GID MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gid_query_impactA | Analyze what components and features are affected by changing a node |
| gid_query_depsB | Get dependencies or dependents of a node |
| gid_query_common_causeB | Find shared dependencies between two nodes (useful for debugging) |
| gid_query_pathB | Find dependency path between two nodes |
| gid_designB | Generate semantic graph from natural language requirements. Creates Features, Components, layers, and relationships. |
| gid_readB | Read and return the current graph structure or summary |
| gid_initB | Initialize a new GID graph in a project |
| gid_extractB | Extract dependency graph from existing code (TypeScript/JavaScript) with optional enrichment |
| gid_historyB | Manage graph version history (list, diff, restore) |
| gid_get_schemaA | Get the GID graph schema with dynamic relations. If a graph exists, includes custom/discovered relations from that graph. |
| gid_analyzeC | Analyze file, function, or class. Returns structured JSON for AI consumption. |
| gid_adviseB | Validate graph and get improvement suggestions. Returns health score + issues + suggestions. |
| gid_refactorC | Preview or apply graph changes to codebase (rename, move, split, merge nodes) |
| gid_semantifyA | Propose semantic upgrades: map files to components, assign layers, detect features. Use returnContext: true for AI semantic analysis (reads docs + code names). |
| gid_get_file_summaryC | Get structured file analysis ready for AI to generate a summary description |
| gid_edit_graphB | Directly add, update, or delete nodes, edges, and relation types in the graph. Supports dynamic relation schema. |
| gid_completeA | Analyze existing graph and documentation to identify gaps and suggest semantic layer additions. Returns structured context for AI to complete the graph with gid_edit_graph. |
| gid_visualA | Generate static HTML visualization of the dependency graph. Returns self-contained HTML that can be saved and opened in a browser. |
| gid_tasksC | Query tasks across the graph. Shows nodes with pending (or all) tasks. |
| gid_task_updateA | Toggle task completion on a node. Marks [ ] ↔ [x]. If all tasks become done, prompts to update status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Current Graph | The current project dependency graph |
| Health Status | Current health score and issues |
| Feature List | List of all features in the graph |
TDQS
Scored across 20 tools
Each tool has a clear and distinct purpose, with descriptions that differentiate them well. For example, gid_analyze focuses on file/function/class analysis, gid_extract extracts dependency graphs from code, and gid_semantify proposes semantic upgrades. There is no significant overlap.
All tools follow a consistent 'gid_verb_noun' pattern in snake_case. The verbs are imperative and descriptive (e.g., gid_init, gid_query_deps, gid_edit_graph), and there is no mixing of conventions.
With 20 tools, the server covers a broad range of graph management operations. While slightly above the typical 3-15 range, each tool serves a specific function and the count is justified by the comprehensive feature set.
The tool set covers the full lifecycle: initialization, reading, editing, version history, code extraction, analysis, design from requirements, multiple query types (dependencies, impact, path, common cause), task management, and visualization. There are no obvious gaps for the stated domain.