@weiseer/api-changelog-mcp
Provides real-time monitoring of breaking changes and version updates for the Google GenAI SDK.
Provides real-time monitoring of breaking changes and version updates for the LangChain SDK.
Provides real-time monitoring of breaking changes and version updates for the Next.js SDK.
Provides real-time monitoring of breaking changes and version updates for the Ollama SDK.
Provides real-time monitoring of breaking changes and version updates for the OpenAI SDK.
Provides real-time monitoring of breaking changes and version updates for the React SDK.
Provides real-time monitoring of breaking changes and version updates for the Replicate SDK.
Provides real-time monitoring of breaking changes and version updates for the Vercel AI SDK.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@weiseer/api-changelog-mcp List all tracked packages with latest versions and breaking changes."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@weiseer/api-changelog-mcp
SDK breaking-change tracker as a stdio MCP server.
Probe P-004 by weiseer.
What it does
Tracks latest version + breaking changes for SDKs AI agents depend on (Anthropic, OpenAI, Google GenAI, MCP SDK, LangChain, LlamaIndex, Mistral, Cohere, Vercel AI, Next.js, React, HuggingFace, Replicate, Ollama).
Your agent can:
list_tracked— packages we track + latest version + 30d breaking-change countget_package— full record with recent breaking events + GitHub release URLget_recent_breaking— breaking changes across all packages, filterablecheck_version— "I'm on v X — am I behind, and what breaks if I upgrade?"
Related MCP server: Doc Monitor MCP
Why use this instead of your agent scraping GitHub releases
Agent DIY | api-changelog | |
Releases to fetch | 18 GitHub repo release feeds | 1 MCP call |
Token cost | $0.06-0.20 | $0 free / $0.00005 paid |
Latency | 5-15 seconds | <100ms |
Breaking-change classification | LLM-classified per call | Pre-classified once |
Install
npm install -g @weiseer/api-changelog-mcpUse with Claude Desktop / Cursor / Cline / Continue / Windsurf
{
"mcpServers": {
"api-changelog": {
"command": "npx",
"args": ["-y", "@weiseer/api-changelog-mcp"]
}
}
}License
Apache-2.0
Available Tools
4 toolscheck_versionB
Given a package + version, return breaking changes since. Saves agents from inspecting changelogs.
Inputs: package_id (required), current_version (required).
get_packageA
Full record for one tracked package — latest version, recent breaking events, source URLs.
Inputs: package_id (required).
get_recent_breakingB
Recent breaking changes across all tracked packages. Filter by days/ecosystem.
Inputs: ecosystem, since_days.
list_trackedA
List packages we track with latest version + breaking-change counts.
Inputs: ecosystem.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: listing tracked packages, fetching a full record, querying recent breaking changes across packages, and checking breaking changes for a specific version. No ambiguity between them.
All tool names follow a consistent verb_noun snake_case pattern: list_tracked, get_package, get_recent_breaking, check_version. Naming is predictable and clear.
With 4 tools, the server is well-scoped for its purpose of tracking API changelogs. It covers the essential operations (list, detail, recent, version check) without being too few or too many.
The tool set covers the main use cases: listing packages, getting full details, recent breaking changes, and version-specific impact. A minor gap is the lack of a tool to view actual changelog entries, but check_version essentially provides that for breaking changes.
Maintenance
Related MCP Connectors
Release notes and changelogs from across the web, indexed for agents. Also via CLI and REST API.
npm & PyPI freshness for AI agents: latest version, deprecations, dated breaking-change diffs.
Verified latest versions, changes and exact-error fixes for agent dev tools. Read-only.
Change intelligence for coding agents: sourced breaking changes for npm, PyPI, and Rust packages.
Related MCP Servers
- AlicenseAqualityCmaintenanceChecks npm and PyPI packages for outdated versions, deprecation status, and breaking changes with cited sources, enabling AI agents to verify dependency freshness.1ISC
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to monitor web documentation for changes, perform semantic search with RAG, and analyze breaking changes in APIs.9-
- AlicenseAqualityDmaintenanceProvides accurate, source-grounded breaking-change briefings for npm packages by reading real GitHub release notes and CHANGELOGs, helping coding agents avoid hallucinated dependency migrations.34 npmMIT
- FlicenseNot gradedqualityDmaintenanceProvides structured migration briefs for LLM coding agents covering breaking changes, codemod coverage, and hallucination warnings for major version bumps of packages like tailwindcss, next, and react.-