@mhdd_24/api-versioning-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROJECT_ROOT | No | Default project/repository root |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| apiver_statusB | Health check for API Versioning MCP. |
| apiver_compareC | Compare two versioned API path lists. |
| apiver_strategyC | Suggest versioning strategy notes. |
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 3 tools
The three tools have clearly distinct purposes: status is a health check, compare diffs two path lists, and strategy produces advisory notes. No overlap or ambiguity exists between them.
All tools share the consistent apiver_ prefix followed by a single descriptive noun (status, compare, strategy). The pattern is predictable and readable throughout.
Three tools is a small but reasonable set for a narrow, focused domain like API versioning diagnostics. It is slightly thin but each tool earns its place without redundancy.
The surface covers health, comparison, and strategy advice, but lacks core versioning operations such as detecting breaking changes, transforming/rewriting paths, or applying a versioning scheme. Notable gaps remain for real versioning workflows.