Skip to main content
Glama
@weiseer/api-changelog-mcp

@weiseer/api-changelog-mcp

by weiseer

@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 count

  • get_package — full record with recent breaking events + GitHub release URL

  • get_recent_breaking — breaking changes across all packages, filterable

  • check_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-mcp

Use 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 tools
check_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

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers