@weiseer/api-changelog-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_trackedA | List packages we track with latest version + breaking-change counts. |
| get_packageA | Full record for one tracked package — latest version, recent breaking events, source URLs. |
| get_recent_breakingB | Recent breaking changes across all tracked packages. Filter by days/ecosystem. |
| check_versionB | Given a package + version, return breaking changes since. Saves agents from inspecting changelogs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.