Ship an MCP server over the programmatic API

[tabkram]

Why

MCP is how coding agents reach tools. The closest feature rival, @entro314labs/ai-changelog-generator, already ships an MCP server and a desktop extension — that is currently its clearest advantage.

src/index.ts already exports generate, promote, and PromptSession as a clean programmatic API. The server is a thin adapter over it, not new functionality.

Scope

Expose as MCP tools:

Tool	Maps to	Notes
generate_release_notes	generate()	range, environment, language, format
promote_release_notes	promote()	returns files without writing by default
ask_release_notes	PromptSession	read-only questions over existing notes
list_releases	output-path discovery	what already exists on disk

Design constraints:

• Read-only by default. Writing to disk is opt-in per call. An agent should be able to explore without side effects.
• Zod schemas for every tool input — zod is already a dependency.
• Surface token usage in the response so the caller can see spend.
• Ship as a bin entry so it runs under npx with no install.

Acceptance criteria

• Server starts over stdio and advertises the four tools
• Works in Claude Code and one other MCP client
• Every tool input is schema-validated with useful error messages
• Write operations require an explicit flag in the call
• Documented in a new docs/mcp.md with a copy-pasteable config block

Files

New src/bin/mcp.ts, src/index.ts, package.json (bin), new docs/mcp.md