MCPModel Context Protocol

Your changelog, readable by your agent.

logg ships an MCP server, so Claude Code, Cursor, and Codex can read your release history and write to it. No copy-pasting between a browser tab and an editor — the log is just another thing your agent can reach.

Connect a client
claude — mcp: logg
what shipped in logg last month?
→ tools/call · list_changelogs { project: "logg" }
← 3 entries · v2.2.0 → v2.4.0
Three releases shipped:
v2.4.0 — scheduled digests, signed webhooks
v2.3.0 — audience tabs on public pages
v2.2.0 — the MCP server itself
draft the v2.5.0 entry from the open milestone
→ tools/call · create_changelog
Draft created — features 4 · fixes 2

01Connect a client

One URL, three editors

Claude

Claude Code

1

Add MCP server

Run this in your terminal — adds logg globally:

claude mcp add --transport http logg https://www.logg.sh/api/mcp
Copy
2

Authenticate

Start Claude Code. A browser window opens for GitHub sign-in automatically on first use.

Alternative: add to ~/.claude/settings.json

settings.json
{
  "mcpServers": {
    "logg": {
      "type": "http",
      "url": "https://www.logg.sh/api/mcp"
    }
  }
}

02Tools

Eleven verbs, no surprises

The full dashboard surface, callable. Reads are safe to run freely; writes go through the same validation as the UI.

ToolDescription
create_projectCreate a project. Omit the GitHub fields for a manual log.
list_projectsEvery project you can reach.
get_projectFull project detail.
list_changelogsEntries for one project, newest first.
get_changelogThe complete body of a single entry.
create_changelogWrite a new entry by hand.
update_changelogRevise an entry in place.
publish_changelogMove a draft onto the public page.
unpublish_changelogPull an entry back to draft.
sync_projectPull new GitHub releases and draft entries for them.
generate_changelogRewrite one entry from its source commits.

03OAuth

2.1 with PKCE, handled for you

Compliant clients complete the handshake on their own. The endpoints below are listed for anyone wiring a client by hand; tokens expire after an hour and clients re-authenticate silently.

DiscoveryGET /.well-known/oauth-authorization-server
ResourceGET /.well-known/oauth-protected-resource
RegisterPOST /api/oauth/register
AuthorizeGET /api/oauth/authorize
TokenPOST /api/oauth/token