agent-context-graph
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_project_overviewB | Return root node, detected tech stack, entry points, and graph counts. |
| init_or_refresh_graphC | Build or refresh the project graph. |
| get_node_contextB | Return a node and its immediate one-hop edges. |
| get_blast_radiusB | Return reachable nodes through calls/imports/inherits up to maxDepth. |
| get_definitive_pathC | Return minimal ordered files/nodes for an intended change. |
| query_best_practicesC | Return bundled best-practice nodes for a domain. |
| declare_task_scopeC | Declare task scope before edits. |
| check_scopeC | Classify proposed changes against a declared scope. |
| record_changeC | Record an actual file mutation immediately after it happens. |
| get_node_historyC | Return compacted change history for a node or path. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Raviraj2024/Agent-Context-Graph'
If you have feedback or need assistance with the MCP directory API, please join our Discord server