Skip to main content
Glama
@mhdd_24/api-dependency-mcp

@mhdd_24/api-dependency-mcp

by Mhdd-24

@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 tools

Related 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-mcp

Option B — npx

npx @mhdd_24/api-dependency-mcp

Option 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.js

Configure 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

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

Available Tools

3 tools
apidep_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

    A3.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers