Agent Fleet MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENT_FLEET_CODEX_ENABLED | No | Enable the Codex worker. Set to 'true' to enable. | true |
| AGENT_FLEET_NOTIFY_COMMAND | No | Shell command to run when a teammate's run finishes. Receives hook-input JSON on stdin. | |
| AGENT_FLEET_CODEX_ALLOWED_ROOTS | No | JSON array of absolute directory paths that Codex can operate in. Default is the process working directory (except if root or home); set an explicit allowlist in those cases. | [] |
| AGENT_FLEET_CODEX_MAX_TIMEOUT_SECONDS | No | Maximum timeout in seconds for Codex runs. | 3600 |
| AGENT_FLEET_CODEX_ALLOW_WORKSPACE_WRITE | No | Set to 'true' to allow workspace-write sandbox in Codex. | 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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_agentA | Assemble an agent for a task and store it in the pool under |
| get_agentA | Return the pooled entry stored under A safe probe: returns None rather than raising when the id is absent, so an orchestrating agent can check existence without handling an error. |
| list_agentsB | Return every pooled agent, most-recently-updated first. Returns: Every stored pool entry, newest-updated first. |
| find_agentsA | Rediscover pooled agents by re-describing the problem, ranked most-relevant first —
the fuzzy path for when the exact |
| delete_agentA | Remove the pooled entry stored under This is also the legitimate dismissal path for a teammate: deleting its |
| list_runsA | Return every run recorded for |
| get_runA | Return one run record by its A safe probe, mirroring |
| list_agent_runsA | List every agent that ran within one run and the real, resumable session id each was given. This is how an orchestrating agent discovers the independently-resumable |
| list_findingsA | Return the pooled agent's findings oldest-first — the assembled-document reading order. |
| run_agentA | Run the pooled agent live and record every agent that participates. The entry's first-ever run starts a fresh session; later runs resume it. Requires the claude CLI at runtime. Every run is granted the full capability set — for the main agent and, when named, for each
dispatched subagent: fan-out subagents (resolved from their own pool entries and wired in via
|
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 10 tools
Each tool targets a distinct operation: agent CRUD, run listing, run execution, and findings retrieval. No two tools have overlapping purposes, and descriptions clearly differentiate them.
All tool names follow a consistent verb_noun pattern using snake_case, e.g., create_agent, list_agents, get_run. Verbs are imperative and clear, with no mixed conventions.
10 tools cover the agent fleet management domain without being excessive or insufficient. Each tool serves a clear purpose in the lifecycle of agents and runs.
The tool surface covers core agent and run operations (create, read, delete, search, run, list runs), but lacks explicit run modification or cancellation capabilities, which is a minor gap.