@mhdd_24/api-dependency-mcp
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.
@mhdd_24/api-dependency-mcp
Map service-to-service API dependencies.
Same architecture as @mhdd_24/sublime-mcp.
Full documentation: docs/WIKI.md
How it works (30 seconds)
You (chat) → MCP client → api-dependency-mcp → API Dependency APIs / CLIs / local toolsRelated MCP server: code-smell-detection-mcp
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-dependency-mcpOption B — npx
npx @mhdd_24/api-dependency-mcpOption C — clone and build
git clone https://github.com/Mhdd-24/API-Dependency-MCP.git
cd API-Dependency-MCP
npm install
npm run build
node dist/index.jsConfigure Cursor
Edit ~/.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"]
}Environment variables
Variable | Description |
| Default project/repository root |
Tools
Tool | Description |
| Show API dependency scan root. |
| Find hardcoded service URLs/clients. |
| Build a dependency map from service:endpoint lines. |
License
ISC
Available Tools
3 toolsapidep_mapC
Build a dependency map from service:endpoint lines.
Inputs: entries (required).
apidep_scanC
Find hardcoded service URLs/clients.
Inputs: root, limit.
apidep_statusC
Show API dependency scan root.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
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.
GitHub security scanning, code audit, and workflow automation for repositories.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI agents to map cross-repository dependencies, detect breaking changes in API contracts, and assess impact across services.10MIT
- AlicenseBqualityDmaintenanceEnables static analysis and code smell detection by connecting to an external analysis API.131MIT
- AlicenseNot gradedqualityDmaintenanceEnables cross-repository architecture discovery and dependency routing across multi-service codebases, with automated scanning and batch AST indexing for AI agents to trace request lifecycles and navigate service boundaries.15 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to track cross-repo dependencies, surface affected consumers before changing shared artifacts, and monitor pinned versions for vulnerabilities.30 PyPI4MIT