@mhdd_24/api-dependency-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROJECT_ROOT | No | Default project/repository root |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| apidep_statusC | Show API dependency scan root. |
| apidep_scanC | Find hardcoded service URLs/clients. |
| apidep_mapC | Build a dependency map from service:endpoint lines. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.