Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AGENT_FLEET_CODEX_ENABLEDNoEnable the Codex worker. Set to 'true' to enable.true
AGENT_FLEET_NOTIFY_COMMANDNoShell command to run when a teammate's run finishes. Receives hook-input JSON on stdin.
AGENT_FLEET_CODEX_ALLOWED_ROOTSNoJSON 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_SECONDSNoMaximum timeout in seconds for Codex runs.3600
AGENT_FLEET_CODEX_ALLOW_WORKSPACE_WRITENoSet to 'true' to allow workspace-write sandbox in Codex.false

Capabilities

Features and capabilities supported by this server

CapabilityDetails
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

NameDescription
create_agentA

Assemble an agent for a task and store it in the pool under agent_key, returning the stored entry — the create/update entry point an orchestrating agent uses to stand up a new pooled agent (or re-assemble an existing one).

get_agentA

Return the pooled entry stored under agent_key, or None when the pool holds no such entry.

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 agent_key isn't at hand.

delete_agentA

Remove the pooled entry stored under agent_key.

This is also the legitimate dismissal path for a teammate: deleting its teammate.* entry discards its standing conversation, and the next run_teammate call re-creates it fresh from its roster template. No guard against the teammate namespace here — unlike create_agent/run_agent, dismissal is intentional deletion, not accidental bypass. Dismissing a teammate with a live run discards that run's record along with the entry, and the still-running background task dies unrecorded when it eventually finishes or fails.

list_runsA

Return every run recorded for agent_key, most-recently-started first.

get_runA

Return one run record by its run_id, or None when the pool holds no such run.

A safe probe, mirroring get_agent: returns None rather than raising when the id is absent, so an orchestrating agent can check existence without handling an error.

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 session_id of every agent — the run's main/supervisor agent and any subagents it dispatched — that participated in a specific run_id (obtained from list_runs, get_run, or a RunOutcome). Each captured session id can then be used to resume that one agent's conversation on its own, independently of the others, later.

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 with_subagents), the run-scoped findings-writer (with_findings_tool), and dynamic capability acquisition (with_acquire_tool). The findings tool needs the run id at wiring time, so the run is started here and its id handed to run_with_capture rather than minted inside it.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

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/Magic-Man-us/claude-sdk-agent-fleet'

If you have feedback or need assistance with the MCP directory API, please join our Discord server