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-dependency-mcp scan the current repo for hardcoded service URLs"
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.
Map service-to-service API dependencies.
Same architecture as @mhdd_24/sublime-mcp.
Full documentation: docs/WIKI.md
You (chat) → MCP client → api-dependency-mcp → API Dependency APIs / CLIs / local toolsRelated MCP server: Merovingian MCP Server
Requirement | Notes |
Node.js 18+ | ESM TypeScript MCP server |
Credentials / CLIs | See environment variables below |
npm install -g @mhdd_24/api-dependency-mcpnpx @mhdd_24/api-dependency-mcpgit clone https://github.com/Mhdd-24/API-Dependency-MCP.git
cd API-Dependency-MCP
npm install
npm run build
node dist/index.jsEdit ~/.cursor/mcp.json:
{
"mcpServers": {
"apidep": {
"command": "npx",
"args": ["-y", "@mhdd_24/api-dependency-mcp"],
"env": {
"PROJECT_ROOT": "..."
}
}
}
}Local development:
{
"command": "node",
"args": ["/absolute/path/to/API-Dependency-MCP/dist/index.js"]
}Variable | Description |
| Default project/repository root |
Tool | Description |
| Show API dependency scan root. |
| Find hardcoded service URLs/clients. |
| Build a dependency map from service:endpoint lines. |
ISC
Screens public GitHub repos and PRs to generate risk maps, findings, and merge-readiness signals.
Detects database migration table locks, terraform cost leaks, and OWASP API flaws.
Generate SBOMs, scan vulnerabilities, and analyze dependencies from local projects or Git repos.
Software component catalog: search your org's services, docs, APIs, dependencies, and ownership.
