Skip to content

All developer docs

The Changeloop MCP server

An MCP server that lets an agent work on your changelog from the editor: read pending, scheduled and published entries, edit them, publish them now or at a set time, or discard them. Below: how to connect Claude Code, the ten tools, and what an agent cannot do.

The MCP server

POST https://api.changeloop.dev/mcp

If you work in Claude Code, ChatGPT or another agent that speaks the Model Context Protocol, you can connect it to your changelog directly. The agent can then see what is waiting for review, edit the wording, and publish, without you leaving the editor. It is the same review gate as the web app: nothing goes public until something approves it.

Connecting Claude Code

Create an API key first (Settings, API keys), then add the server with your key in the header:

claude mcp add --transport http changeloop \
  https://api.changeloop.dev/mcp \
  --header "Authorization: Bearer clapi_YOUR_KEY"

For a client that reads a JSON config instead, the same thing looks like this:

{
  "mcpServers": {
    "changeloop": {
      "type": "http",
      "url": "https://api.changeloop.dev/mcp",
      "headers": { "Authorization": "Bearer clapi_YOUR_KEY" }
    }
  }
}

There is no OAuth flow yet. Authentication is the API key in the header, which is what the two commands above are doing. Revoking that key in Settings disconnects the agent on its next request.

What the agent can do

Ten tools, and the list is deliberately short. Anything else this product can do is reachable over the REST API with the same key; every tool exposed to an agent is one more thing it can be talked into calling.

  • list_pending_entries, list_published_entries, get_entry - read your entries. Pending ones are not public.
  • update_entry - change the title or the markdown body of an entry. The HTML the feed serves is re-rendered from your markdown by our sanitiser; an agent cannot supply HTML.
  • approve_entry - publish. This is public and immediate, and it notifies any linked feedback on GitHub. Only a pending entry can be approved, or a scheduled one when you pass publish_now: true, which sends it out now instead of at its time.
  • discard_entry - keep an entry out of the changelog. Reversible from the web app.
  • get_changelog_info - your feed id and the addresses your changelog is served from.
  • list_scheduled_entries, schedule_entry, unschedule_entry - see what is scheduled, soonest first; schedule a pending entry to go out at a set time, given with its time zone, from a minute to 90 days ahead, or move it to a new time; or cancel a schedule, which puts the entry back in pending. A roundup cannot be scheduled.

What it cannot do

Every tool is scoped to the team the key belongs to, and none of them takes a team as an argument, so there is nothing to point at another team even if something tried. The server does not accept a browser session, only a key: a request has to attach the credential deliberately. And a key cannot manage keys or download your data export, so an agent connected this way cannot mint itself a second credential or pull your data out in one call.

API keys

Everything above is anonymous and needs no credential. The authenticated API -- your settings, your review inbox -- is a different surface, and it accepts either a signed-in browser session or an API key. Keys are for scripts and agents: anything that has to reach your changelog without a person at a keyboard.

Create one in the app under Settings, on the API keys tab. The key is shown once, at the moment you create it, and never again: we store only a hash of it, so there is no screen anywhere that can show it to you a second time. If you lose it, revoke it and make another.

Review your changelog from the editor

Changeloop drafts each entry from a merged pull request and holds it for review, in the web app or through this MCP server. Free for one repository, no card.

Start free

Read the developer docs