@mhdd_24/api-versioning-mcp
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., "@@mhdd_24/api-versioning-mcp Compare my v1 and v2 API paths and suggest a versioning strategy."
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.
@mhdd_24/api-versioning-mcp
Analyze API version compatibility.
Same architecture as @mhdd_24/sublime-mcp.
Full documentation: docs/WIKI.md
How it works (30 seconds)
You (chat) → MCP client → api-versioning-mcp → API Versioning APIs / CLIs / local toolsRelated MCP server: mcp-semver
Prerequisites
Requirement | Notes |
Node.js 18+ | ESM TypeScript MCP server |
Credentials / CLIs | See environment variables below |
Install
Option A — npm (after publish)
npm install -g @mhdd_24/api-versioning-mcpOption B — npx
npx @mhdd_24/api-versioning-mcpOption C — clone and build
git clone https://github.com/Mhdd-24/API-Versioning-MCP.git
cd API-Versioning-MCP
npm install
npm run build
node dist/index.jsConfigure Cursor
Edit ~/.cursor/mcp.json:
{
"mcpServers": {
"apiver": {
"command": "npx",
"args": ["-y", "@mhdd_24/api-versioning-mcp"],
"env": {
"PROJECT_ROOT": "..."
}
}
}
}Local development:
{
"command": "node",
"args": ["/absolute/path/to/API-Versioning-MCP/dist/index.js"]
}Environment variables
Variable | Description |
| Default project/repository root |
Tools
Tool | Description |
| Health check for API Versioning MCP. |
| Compare two versioned API path lists. |
| Suggest versioning strategy notes. |
License
ISC
Available Tools
3 toolsapiver_compareC
Compare two versioned API path lists.
Inputs: v1 (required), v2 (required).
apiver_statusB
Health check for API Versioning MCP.
Inputs: no named parameters.
apiver_strategyC
Suggest versioning strategy notes.
Inputs: style.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Detect breaking changes, generate changelogs, diff, and validate OpenAPI specs.
Schema-aware API monitoring: diff OpenAPI specs for breaking changes, manage endpoints.
Scores how well AI agents will use your API, 0-100, from its OpenAPI spec. Free and read-only.
Check exact npm/PyPI upgrades for evidence-backed breaking changes; query APIs and components.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to browse, read, compare, and validate OpenAPI contracts for providers and consumers.1MIT
- AlicenseNot gradedqualityCmaintenanceProvides semantic versioning tools to parse, compare, and check range satisfaction for version strings, enabling version management through natural language queries.292 npmMIT
- AlicenseAqualityDmaintenanceEnables AI clients to validate OpenAPI specs, compare versions, detect breaking changes, and generate changelogs.4MIT
- FlicenseNot gradedqualityDmaintenanceProvides a streamable HTTP endpoint for compatibility analysis, with published contracts and schemas for integration.-