agloop-mcp
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 |
|---|---|
| agloop_get_stateA | Read the full AgLoop state including phase, tasks, iteration, and compaction context. Returns null if no active loop. |
| agloop_get_taskA | Get details for a single task by ID. Returns task status, dependencies, acceptance criteria, and result log. |
| agloop_list_tasksB | List all tasks with optional status filter. Returns array of task objects. |
| agloop_get_logsA | Read execution log entries. Supports filtering by agent, task, and limiting results. |
| agloop_get_planA | Read the current plan (plan.yaml or plan.md). Returns raw file contents. |
| agloop_get_compaction_contextA | Get compaction recovery context: compaction count, pending decision, last delegation, recovery hint. Critical after VS Code context compaction. |
| agloop_search_logsB | Full-text search through execution logs. Case-insensitive search across agent, action, task_id, phase, input/output summaries. |
| agloop_get_agent_infoA | Read the definition file (.agent.md) for a specific agent. Returns the full agent prompt including frontmatter. |
| agloop_get_next_taskA | Compute the next task using topological sort. Returns the recommended next task and reasoning. |
| agloop_list_agentsA | List all available agent names in .github/agents/. |
| agloop_update_taskA | Update a task's status and/or result log. Auto-sets timestamps. COORDINATOR ONLY. |
| agloop_append_logB | Append a structured entry to the execution log. COORDINATOR ONLY. |
| agloop_create_checkpointC | Create a checkpoint of the current state for recovery. COORDINATOR ONLY. |
| agloop_set_phaseD | Transition to a new phase. COORDINATOR ONLY. |
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 14 tools
Each tool targets a distinct aspect of the AgLoop workflow: logging, state management, agent info, task operations, and phase transitions. There is no overlap or ambiguity between tools.
All tools follow a consistent 'agloop_verb_noun' pattern with appropriate verbs (append, create, get, list, search, set, update) and clear nouns, making the naming predictable.
With 14 tools, the server covers the needed operations for a workflow management system without being excessive. The count is well-scoped for its purpose.
The tool set covers core workflow operations such as reading state, managing tasks and agents, logging, and phases. A minor gap is the lack of task creation or deletion tools, but tasks appear to be defined externally, so the surface is largely complete.