Skip to main content
Glama
Mhdd-24

@mhdd_24/api-deprecation-mcp

by Mhdd-24
README.md
# @mhdd_24/api-deprecation-mcp

Track deprecated endpoints and features.

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-deprecation-mcp → API Deprecation 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-deprecation-mcp
```

### Option B — npx

```bash
npx @mhdd_24/api-deprecation-mcp
```

### Option C — clone and build

```bash
git clone https://github.com/Mhdd-24/API-Deprecation-MCP.git
cd API-Deprecation-MCP
npm install
npm run build
node dist/index.js
```

---

## Configure Cursor

Edit `~/.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "apidepr": {
      "command": "npx",
      "args": ["-y", "@mhdd_24/api-deprecation-mcp"],
      "env": {
        "PROJECT_ROOT": "..."
      }
    }
  }
}
```

**Local development:**

```json
{
  "command": "node",
  "args": ["/absolute/path/to/API-Deprecation-MCP/dist/index.js"]
}
```

---

## Environment variables

| Variable | Description |
|----------|-------------|
| `PROJECT_ROOT` | Default project/repository root |

---

## Tools

| Tool | Description |
|------|-------------|
| `apidepr_status` | Show scan root for deprecations. |
| `apidepr_scan` | Scan for deprecated annotations/comments. |
| `apidepr_catalog` | Build a deprecation catalog from notes. |

---

## License

ISC

TDQS

B3/5.0

Scored across 3 tools

Disambiguation4/5

The three tools have clearly distinct purposes: status shows the scan root, scan performs the actual deprecation search, and catalog builds a structured result. Minor overlap exists between status and scan since status may imply scanning state, but descriptions are sufficient to differentiate them.

Naming Consistency4/5

All tools share the consistent 'apidepr_' prefix, which creates a clear namespace. However, the suffix pattern is mixed: 'status' and 'catalog' are nouns while 'scan' is a verb, so it is not a strict verb_noun convention.

Tool Count4/5

Three tools is a reasonable, focused count for a narrow deprecation-scanning server. The scope is small enough that each tool earns its place without feeling thin or excessive.

Completeness3/5

The core scan workflow is covered: view the scan root, run the scan, and build a catalog. However, there is no obvious tool for configuring the scan root, viewing raw scan results, or performing follow-up actions on detected deprecations, which leaves minor gaps.

Maintenance

ActivityMaintained
ResponsivenessNo issues