@mhdd_24/api-dependency-mcp
# @mhdd_24/api-dependency-mcp
Map service-to-service API dependencies.
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-dependency-mcp → API Dependency 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-dependency-mcp
```
### Option B — npx
```bash
npx @mhdd_24/api-dependency-mcp
```
### Option C — clone and build
```bash
git clone https://github.com/Mhdd-24/API-Dependency-MCP.git
cd API-Dependency-MCP
npm install
npm run build
node dist/index.js
```
---
## Configure Cursor
Edit `~/.cursor/mcp.json`:
```json
{
"mcpServers": {
"apidep": {
"command": "npx",
"args": ["-y", "@mhdd_24/api-dependency-mcp"],
"env": {
"PROJECT_ROOT": "..."
}
}
}
}
```
**Local development:**
```json
{
"command": "node",
"args": ["/absolute/path/to/API-Dependency-MCP/dist/index.js"]
}
```
---
## Environment variables
| Variable | Description |
|----------|-------------|
| `PROJECT_ROOT` | Default project/repository root |
---
## Tools
| Tool | Description |
|------|-------------|
| `apidep_status` | Show API dependency scan root. |
| `apidep_scan` | Find hardcoded service URLs/clients. |
| `apidep_map` | Build a dependency map from service:endpoint lines. |
---
## License
ISC
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: status reports the scan root, scan discovers hardcoded URLs/clients, and map builds the dependency graph. There is no meaningful overlap between these operations.
All tools share the consistent 'apidep_' prefix and lowercase snake_case naming. The operation words—status, scan, map—are short and predictable within the server's domain.
With only three tools, the server is tightly scoped to the API dependency scanning workflow. Each tool serves a necessary purpose without redundant or filler operations.
The set covers the core workflow of showing the scan root, scanning for dependencies, and building a map. A minor gap is the lack of an explicit way to configure or update the scan root through the tool surface.