Manual publishing gets skipped
When the changelog is outside the release flow, it becomes the thing teams promise to do later.
Changelog API
A changelog API for teams that ship from their workflow.
Create, update, and publish changelog posts from CI, internal tools, release scripts, Claude, Cursor, or your own product operations dashboard.
API access is available on paid plans and active trials.
REST API
MCP server
CI/CD ready
10
MCP tools already map to real changelog workflows
1
API key connects automation to your hosted changelog
No
Manual copy-paste once release scripts mature
API workflow
Create a release post
Your release script sends summary, markdown, categories, and visibility to ChangeCrab.
Decide how it goes live
Publish immediately, keep as draft, or use scheduling controls when your plan supports them.
One update powers every channel
The public page, RSS feed, widget, subscribers, and badges all point back to the same update.
New update ready for customers
Published to public page, widget, RSS, and subscriber channels.
Follow-up context stays attached
Links, categories, and customer impact live with the update instead of drifting across tools.
The problem
Release communication breaks when it is separate from release operations.
Internal tools need a destination
CI, release checklists, and product ops tools need a simple way to create customer updates.
AI agents need tools, not scraping
MCP and API workflows let agents work with structured changelog data instead of brittle browser tasks.
Workflow
Build a release workflow around a real changelog API
Source
Generate release context
Collect commits, tickets, labels, screenshots, and rollout notes.
Shape
Create or update a post
Use the API to publish, draft, or revise the customer update.
Publish
Let ChangeCrab handle distribution
Your public changelog, feeds, subscribers, widget, and badges stay in sync.
Implementation
API examples for release automation
These examples show the core API shape for listing posts, creating release notes, and connecting ChangeCrab to release automation.
curl https://changecrab.com/api/changelogs/your-id/posts \
-H "X-API-Key: $CHANGECRAB_API_KEY" \
-H "Accept: application/json"curl -X POST https://changecrab.com/api/changelogs/your-id/posts \
-H "X-API-Key: $CHANGECRAB_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"summary": "New audit log filters",
"markdown": "Admins can now filter audit logs by actor, action, and date range.",
"public": 1
}'await fetch("https://changecrab.com/api/changelogs/your-id/posts", {
method: "POST",
headers: {
"X-API-Key": process.env.CHANGECRAB_API_KEY,
"Content-Type": "application/json",
"Accept": "application/json"
},
body: JSON.stringify({
summary: "New audit log filters",
markdown: "Admins can now filter audit logs by actor, action, and date range.",
public: 1
})
});What you get
Built around the parts of product communication teams use every week.
API key authentication
List changelogs and posts
Create, update, and delete changelog posts
Category-aware publishing workflows
MCP server support for Claude and Cursor
Public API documentation for implementation handoff
API guardrails
Automation works best when the API creates a reviewed release asset.
This section answers the practical objections developers and product ops teams will have before trial.
General REST API access is available on paid plans and active trials.
Use the API to create or update posts, then review public copy and subscriber alerts before publishing.
The MCP server gives Claude and Cursor a safer path than scraping a browser session.
Buyer questions
Questions teams ask before choosing a changelog workflow.
Is the API for free plans?
API access is available on paid plans and active trials. The free plan is best for manual publishing and basic hosted changelog workflows.
Can this work with CI/CD?
Yes. Use the API from release scripts, internal tools, or deployment workflows when you want changelog publishing to be part of shipping.
How does this relate to MCP?
The ChangeCrab MCP server wraps real changelog workflows as tools for MCP-compatible clients such as Claude Desktop and Cursor.
Make changelog publishing part of release automation.
Start a trial, create an API key, and connect your next release workflow to ChangeCrab.