ChangeCrab MCP Server

Public changelogs for Claude MCP servers.

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.

Start Trial and Install MCP View Example MCP Changelog

MCP and API access included on trial Node.js 18+ stdio server Works with Claude Desktop and Cursor

claude_desktop_config.json -> changecrab-mcp-server

Claude / Cursor MCP connected

Prompt

Create a public changelog post for v1.8.0 of our PostgreSQL MCP server. Mention query plan inspection, Claude Desktop auth fixes, and the changed input schema.

Tool calls

list_changelogs({}) list_categories({ changelog_id: "pgMCP8" }) create_post({ changelog_id: "pgMCP8", summary: "v1.8.0 - Query plan inspection and auth fixes", public: 1, draft: 0 })

Result

Published a user-facing update with New tool, Compatibility, and Breaking categories. Subscribers, RSS readers, and the public page now have the same source of truth.

Public changelog Live page

PostgreSQL MCP Server

Tool updates, compatibility notices, schema changes, and release notes for users running this server with Claude.

Public page RSS Email README badge

v1.8.0 - Added query plan inspection tool

Today

New tool Compatibility

Claude can now inspect query plans before running expensive PostgreSQL operations.

v1.7.4 - Fixed Claude Desktop OAuth callback issue

3d ago

Fix Auth

Resolved a redirect mismatch affecting local Claude Desktop setups.

v1.6.2 - Breaking: updated query input_schema

9d ago

Breaking Schema

Tool calls now require explicit database role and timeout parameters.

The problem

MCP servers evolve fast. Most users never know what changed.

Commits, Discord messages, and README edits are useful for maintainers. They are a rough place for users to track compatibility.

Breaking

Schema changes go unnoticed

A small tool input change can break saved agent workflows.

Noise

GitHub commits are too dense

Users need release meaning, not every internal refactor.

Support

Compatibility fixes disappear

Claude Desktop and client-specific fixes get buried quickly.

Trust

Adoption needs visible activity

A public update history tells users the server is alive.

Spread

Announcements fragment

Docs, issues, chats, and release pages drift out of sync.

Installable today

Manage ChangeCrab from Claude or Cursor.

The ChangeCrab MCP server exposes your changelog workflow as tools your AI assistant can call with your API key.

Claude Desktop / Cursor config

Start a trial, create an API key, add the server, then restart your MCP client.

{ "mcpServers": { "changecrab": { "command": "npx", "args": ["-y", "changecrab-mcp-server"], "env": { "CHANGECRAB_API_KEY": "your-api-key-here" } } } }

Start Trial for MCP Access Read MCP Docs

10 MCP tools, mapped to real ChangeCrab workflows

Use static info tools for product help, then API-backed tools to publish and maintain your changelog.

list_changelogs

Find the right changelog from chat.

get_changelog

Fetch details for one changelog.

list_categories

Choose labels before publishing.

list_posts

Review recent releases.

create_post

Publish markdown updates.

update_post

Edit an existing release note.

delete_post

Remove mistaken entries.

info tools

Answer setup and limits questions.

Example gallery

Changelogs that feel native to the MCP ecosystem.

Show users the exact changes they care about: tools, schemas, auth, client compatibility, and releases.

Browser Automation MCP

v2.4.0 - Added screenshot diff toolNew tool · Playwright compatibility

v2.3.1 - Fixed headless launch flagsFix · Claude Desktop

v2.2.0 - Added file upload actionsNew tool · Docs

Claude Memory MCP

v1.5.0 - Added scoped memory storesFeature · Privacy

v1.4.2 - Improved local index rebuildsFix · Performance

v1.4.0 - Breaking storage path changeBreaking · Migration

Vector Search MCP

v3.1.0 - Added hybrid search rankingNew tool · Relevance

v3.0.5 - Fixed embedding batch retriesFix · Reliability

v3.0.0 - Updated collection schemaBreaking · Schema

GitHub Issues MCP

v0.9.0 - Added triage label toolNew tool · GitHub

v0.8.3 - Fixed token refresh handlingFix · Auth

v0.8.0 - Added comment searchFeature · API

How it works

From shipped MCP change to public update.

Connect

Connect your workflow

Install the ChangeCrab MCP server, use the API, import from GitHub or RSS, or publish from the dashboard.

Ship

Ship MCP updates

Post releases, breaking changes, tool additions, compatibility fixes, and auth or schema notices.

Share publicly

Give users one URL to follow your MCP server through public pages, feeds, emails, widgets, and badges.

Distribution layer

Every MCP changelog gets a public page users can bookmark.

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.

Public pageShare a clean hosted changelog or custom domain.

RSS / AtomFeed readers, docs sites, automation, and bots.

EmailLet users subscribe to compatibility changes.

WidgetSurface updates inside docs or product pages.

BadgeShow update frequency in README and docs.

API / MCPPublish without leaving your coding agent.

Your MCP server ships fast. Your changelog should too.

Start a ChangeCrab trial, install the MCP server, and give users a visible release history before the next breaking schema change lands.

Start Trial Install MCP Server