v1.8.0 - Added query plan inspection tool
Claude can now inspect query plans before running expensive PostgreSQL operations.
ChangeCrab MCP Server
Install the ChangeCrab MCP server and publish tool additions, schema changes, auth fixes, compatibility notes, and releases from Claude Desktop, Cursor, API, or the web.
Tool updates, compatibility notices, schema changes, and release notes for users running this server with Claude.
Claude can now inspect query plans before running expensive PostgreSQL operations.
Resolved a redirect mismatch affecting local Claude Desktop setups.
Tool calls now require explicit database role and timeout parameters.
The problem
Commits, Discord messages, and README edits are useful for maintainers. They are a rough place for users to track compatibility.
A small tool input change can break saved agent workflows.
Users need release meaning, not every internal refactor.
Claude Desktop and client-specific fixes get buried quickly.
A public update history tells users the server is alive.
Docs, issues, chats, and release pages drift out of sync.
Installable today
Run the ChangeCrab MCP server locally with your API key. Version 2 saves drafts first and requires an explicit subscriber alert choice when publishing. Hosted ChatGPT and Claude connections are planned for a later release.
Build version 2 from source, create an API key, and use your local path below. The npm package currently provides 1.0.0; version 2 will be available after publication. See the setup guide for build steps.
Use static info tools for product help, then API-backed tools to publish and maintain your changelog.
list_changelogsFind the right changelog from chat.
get_changelogFetch details for one changelog.
list_categoriesChoose labels before publishing.
list_postsReview recent releases.
create_postSave Markdown drafts; publish explicitly.
update_postEdit supplied fields and preserve the rest.
delete_postDelete an explicitly selected entry.
info toolsAnswer setup and limits questions.
Example gallery
Show users the exact changes they care about: tools, schemas, auth, client compatibility, and releases.
How it works
Install the ChangeCrab MCP server, use the API, import from GitHub or RSS, or publish from the dashboard.
Post releases, breaking changes, tool additions, compatibility fixes, and auth or schema notices.
Give users one URL to follow your MCP server through public pages, feeds, emails, widgets, and badges.
Distribution layer
ChangeCrab turns release communication into a durable surface for docs, README files, Claude setup guides, Discord communities, and users evaluating whether your server is maintained.
Start a ChangeCrab trial, install the MCP server, and give users a visible release history before the next breaking schema change lands.