MCP — the agent surface
Your agent keeps the record
The same record your customers read, exposed as twelve tools over streamable HTTP with OAuth 2.1 — a consent screen, short tokens, rotating refresh. An agent can read what shipped, draft the next entry from evidence, and publish it, all as you.
> connect logg
logg: authorized as @you · 12 tools
> what shipped last week?
logg: 2 releases — 2.4.0 exports, 2.3.9 fixes
> draft 2.5.0 from the merged PRs
logg: drafted · 6 items · 1 flagged guess
> publish it
logg: live — page, feeds, api, #releases ▌
01—Connect a client
claude code
claude mcp add --transport http logg https://logg.sh/api/mcp
any mcp client
endpoint: https://logg.sh/api/mcp transport: streamable http auth: oauth 2.1 (discovered automatically)
02—The tools
| Tool | Takes | Does |
|---|---|---|
| get_upgrade_guide | project, from, to | Public breaking changes and declared migration steps (Pro) |
| list_projects | — | Every project the account can touch |
| get_project | project | One project's configuration and counts |
| create_project | name, slug, github? | Start a record, manual or GitHub-tracked |
| list_changelogs | project | The entries, newest first |
| get_changelog | project, version, edition? | One entry through an edition |
| create_changelog | project, version, content | Write an entry by hand |
| update_changelog | project, changelogId, … | Edit title, summary, items |
| publish_changelog | project, changelogId | Put an entry live everywhere |
| unpublish_changelog | project, changelogId | Take it off the record |
| sync_project | project | Import the repo's shipping history |
| generate_changelog | project, changelogId | Redo an entry from evidence, and save it |
03—OAuth, if you are wiring it by hand
/.well-known/oauth-authorization-serverRFC 8414 discovery/.well-known/oauth-protected-resourceRFC 9728 resource metadata/api/oauth/registerdynamic client registration/api/oauth/authorizecode flow, S256 PKCE, human consent/api/oauth/tokencodes and rotating refresh tokens