Agent Context 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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_taskC | Creates a new working context task and returns the task ID. |
| log_progressB | |
| log_decisionC | Logs a technical decision with its reason to the context. |
| add_questionC | Adds an unresolved open question to the context. |
| resolve_questionB | Marks an open question as resolved. |
| resumeA | |
| list_tasksB | Lists tasks, optionally filtered by status (active, done, blocked, abandoned). |
| graph.indexC | Parses a given file path and saves the extracted symbols to the symbols table. |
| graph.get_symbolC | Retrieves a symbol's info, file, and line numbers from the database. |
| graph.trace_callsB | Returns the inbound or outbound call chain for a given symbol. direction: 'inbound' or 'outbound' |
| graph.get_architectureB | Returns a basic high-level overview of the parsed codebase, including files, symbol counts, and entry points. |
| project.exportA | Creates a compressed zip backup of the entire .agentctx/ directory. |
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 12 tools
Tools are clearly separated into graph analysis (graph.*) and context management (add_question, log_decision, etc.), each with distinct purposes. No overlap between tools.
Uses a mix of plain snake_case (add_question, list_tasks) and dotted hierarchical names (graph.get_architecture, project.export). Consistent within subgroups but inconsistent across the whole set.
12 tools cover the main functionalities of code graph analysis and task/context management without being excessive. Well-scoped for the server's domain.
Core operations are present but missing lifecycle actions: no update/delete for tasks, decisions, or questions. Graph tools lack search or listing capabilities.