ReleasePad adds MCP server for AI-written release notes

ReleasePad launched a Model Context Protocol server on Sept. 14, 2026, letting Claude, Codex, Cursor and other compatible assistants draft, organize and publish product release notes with human approval. The company says the goal is to close the gap between shipping features and telling customers about them.

Why it matters: - Product teams often ship features faster than they announce them, leaving customers unaware of updates and support teams answering questions a short release note could have prevented. - ReleasePad is trying to make release notes part of the same workflow as coding, which could help teams keep changelogs current without adding a separate manual step. - The launch also pushes release notes into the growing AI toolchain, so the same assistants that help build products can now help explain them.

What happened: - ReleasePad launched an MCP server on Sept. 14, 2026. - The server is live at pro.releasepad.io/mcp and works with any assistant that supports the Model Context Protocol. - Compatible assistants include Claude, Codex and Cursor. - The server lets an AI assistant draft release notes, file them under a category and schedule them for publication.

The details: - The Model Context Protocol is an open standard that allows AI assistants to use external tools. - ReleasePad's MCP server exposes the changelog as a set of tools the assistant can use directly. - Users can ask an assistant to review what shipped, draft a customer-ready note and leave it as a draft. - The server can create posts as drafts, edit or reference earlier posts, list product categories, attach images and report post performance after publication. - ReleasePad says connection uses OAuth, so teams do not need to generate, paste or rotate API keys. - Access can be revoked from the account like any other connected app. - Teams can set tone, language, detail level and emoji style in AI settings. - Teams can also add free-text instructions, such as always mentioning which plans a change applies to. - Every draft still requires human approval before publication. - ReleasePad publishes approved updates in three places: an in-app widget, a changelog page on the customer's own domain and an LLM-ready Markdown feed. - The in-app widget is a 4.3-kilobyte script that shows a “What’s new” panel inside the product. - The public changelog page can live on a customer subdomain such as updates.yourdomain.com, with HTTPS handled automatically. - The public page is built to be indexed by search engines. - The Markdown feed is designed to be readable by ChatGPT, Claude, Perplexity and other assistants. - ReleasePad says the feed lets AI answers about a product come from the team's own release notes instead of a guess.

Between the lines: - The launch goes beyond faster writing. It links feature shipping, customer communication and AI search into one workflow. - ReleasePad is targeting a common failure point for small teams: the product update exists, but the announcement never gets finished. - By keeping a human approval step, ReleasePad is positioning the MCP server as an assistant for publishing, not an autopilot for messaging. - The analytics hooks suggest ReleasePad wants the changelog to be a feedback loop, not just a broadcast channel.

What's next: - Teams can start using the MCP server immediately through supported AI assistants. - ReleasePad's analytics access should let teams ask which posts were read and which updates drew the most views. - The company is betting that faster feature shipping will create more demand for same-session release-note creation.

The bottom line: - ReleasePad is turning release notes into an AI-assisted workflow, with human approval at the center and automatic publishing to multiple surfaces after sign-off.