@mhdd_24/api-versioning-mcp
# @mhdd_24/api-versioning-mcp
Analyze API version compatibility.
Same architecture as [@mhdd_24/sublime-mcp](https://github.com/Mhdd-24/Sublime-MCP).
**Full documentation:** [docs/WIKI.md](./docs/WIKI.md)
---
## How it works (30 seconds)
```
You (chat) → MCP client → api-versioning-mcp → API Versioning APIs / CLIs / local tools
```
---
## Prerequisites
| Requirement | Notes |
|-------------|--------|
| **Node.js 18+** | ESM TypeScript MCP server |
| **Credentials / CLIs** | See environment variables below |
---
## Install
### Option A — npm (after publish)
```bash
npm install -g @mhdd_24/api-versioning-mcp
```
### Option B — npx
```bash
npx @mhdd_24/api-versioning-mcp
```
### Option C — clone and build
```bash
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`:
```json
{
"mcpServers": {
"apiver": {
"command": "npx",
"args": ["-y", "@mhdd_24/api-versioning-mcp"],
"env": {
"PROJECT_ROOT": "..."
}
}
}
}
```
**Local development:**
```json
{
"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
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.