Skip to main content
Glama
@mhdd_24/api-versioning-mcp

@mhdd_24/api-versioning-mcp

by Mhdd-24

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

Related 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-mcp

Option B — npx

npx @mhdd_24/api-versioning-mcp

Option 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.js

Configure 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

PROJECT_ROOT

Default project/repository root


Tools

Tool

Description

apiver_status

Health check for API Versioning MCP.

apiver_compare

Compare two versioned API path lists.

apiver_strategy

Suggest versioning strategy notes.


License

ISC

Available Tools

3 tools
apiver_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

    B3.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    All tools share the consistent apiver_ prefix followed by a single descriptive noun (status, compare, strategy). The pattern is predictable and readable throughout.

    Tool Count4/5

    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.

    Completeness3/5

    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

    ActivitySlowing
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers