cc-changelogs
coredirective/ccchangelogsFifteen tools over a Claude Code changelog that reads the actual release diffs instead of copying out Anthropic's notes. Ask what changed between two versions, search entries by area or tier, pull one entry in full, read the stock system prompts version by version, diff Anthropic's docs day by day, or look up an env var or a hook API and get back the release that introduced it. Every answer carries the public URL it came from, so you can hand a link to a person instead of a paragraph. Anthropic ships Claude Code fast and says little about what is in it. Features land with no announcement, no changelog entry, sometimes no documentation at all, and the official notes are one line per release when they exist. The site behind this server unpacks every build and writes up what actually moved, down to the flags and internal APIs nobody mentioned. This is how a model reads it without you pasting anything in.
Score: 100/100
Handshake verified by our own probe.
Tools · 15
The full changelog for one Claude Code release, from changelogs.core-directive.com: what changed, why it matters, and what is present but switched off. Omit `version` (or pass `latest`) for the newest…
Search every Claude Code release the site has read, by entry: hit an entry's own heading and prose rather than a whole release. Every term has to appear in the same entry. Narrow with `version`, `tier…
Which Claude Code releases the site has published, newest first, with each one's date, entry count and one-line summary. This is how to answer what the newest version is, what shipped since a date (`s…
What changed between two versions, in one call. Reach for this whenever somebody names two versions, says they upgraded, or asks what is new since the build they are on: it answers every entry publish…
Every entry in one release, in the order the release puts them, as headings with a one-line summary each. Where `changelog` hands back the release's prose a window at a time, this pages through its en…
One changelog entry in full: the whole prose the release carries for it, as markdown, rather than the one-line summary `search` and `entries` answer. Takes the `anchor` either of those tools gave, plu…
What a Claude Code environment variable, CLI flag, settings key, slash command, tool, hook event or model id actually is, from the site's mined inventory of every name in the shipped build. This is th…
Anthropic's own Claude Code, API and SDK documentation, as this site captured it, with the text as published rather than as summarised. Pass `q` to search every captured page and get the passage aroun…
What Anthropic changed in their own documentation, dated and diffed. Reach for this whenever somebody asks whether the docs moved, what was quietly updated this week, when a page last changed, or what…
The site owner's own writing about Claude Code, which is the one thing here that is neither a changelog entry nor somebody else's documentation: the argument about why a change matters, and what this …
What one Claude Code build actually told the model its tools do: the stock injected tool descriptions, captured release by release, byte for byte as they were sent. Not a description of the Read tool,…
The Claude Code plugin runtime's own API, mined out of the newest shipped build: every noun and verb on `$` (`$.session.usage`, `$.model.complete`), every event a hook can be registered for (`session.…
How to actually write a Claude Code hooks module, as ten pages of hand-written guide: what a mod is and which builds load one, the files one needs, the five tiers and what `next()` can do, the engine …
Features followed across every release that touched them, as the site's owner grouped them by hand: how output styles, or hooks, or the plugin runtime actually arrived, in order, one release at a time…
What has happened to already-published entries since their release shipped: a flag reading moved on Anthropic's server, a gate was removed from the code, their documentation finally arrived, their off…
How to use
Claude Desktop or claude.ai: add a custom connector (Customize → Connectors; on Team and Enterprise plans an owner adds it under Organization settings → Connectors) with this server URL: https://changelogs.core-directive.com/mcp
Cursor or Cline: add to your MCP config:
{
"mcpServers": {
"cc-changelogs": {
"url": "https://changelogs.core-directive.com/mcp",
"transport": "http"
}
}
}