context-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | HTTP bind host (default: localhost) | localhost |
| PORT | No | HTTP server port (default: 3100) | 3100 |
| DATA_DIR | No | Path to the data directory (default: ~/.context-mcp) | ~/.context-mcp |
| ACCESS_GIT | No | Enable git tools for HTTP clients (default: false) | false |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| codegraph_buildA | Scan a project directory and build the knowledge graph from code files. Uses tree-sitter AST (with regex fallback) for all code files. Fast, local, no API key needed. Run once per project; rebuild whenever code changes. |
| codegraph_queryA | Ask a structural question about the codebase OR look up a specific node by name — or both in one call. Pass |
| codegraph_reportC | Return CODEGRAPH_REPORT.md — god nodes, clusters, surprising connections, suggested questions. |
| codegraph_nodesB | List all nodes of a given type in the graph. |
| codegraph_pathC | Find the shortest relationship path between two concepts in the graph. |
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 5 tools
Each tool has a clearly distinct purpose: building the graph, listing nodes, finding paths, querying, and generating reports. No overlap in functionality.
All tools follow a consistent 'codegraph_<verb>' pattern (build, nodes, path, query, report), making it easy to predict tool names.
Five tools is an ideal count for a focused code knowledge graph server, covering all essential operations without bloat or deficiency.
The tool surface covers building, querying (by node, path, natural language), listing nodes, and generating a summary report. No obvious gaps for code exploration.