agent-shuttle-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BRIDGE_CODEX_URL | No | URL for Codex agent delegation. | |
| BRIDGE_AGENTS_JSON | No | Routes requests to any agent mapped in this environment variable. | |
| BRIDGE_ANTIGRAVITY_URL | No | URL for Antigravity agent delegation. |
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 |
|---|---|
| ask_agentC | Ask a configured agent profile from BRIDGE_AGENTS_JSON. |
| get_agent_infoB | Read capabilities and quota information for a configured agent profile. |
| ask_antigravityC | Delegate to Antigravity; workspace starts an isolated temporary Bridge. |
| ask_codexC | Delegate to Codex. model and reasoning_effort select its thread settings. |
| get_antigravity_infoB | Read Antigravity's current models, effort options and account quota without an agent turn. |
| get_codex_infoA | Read Codex's current models, supported efforts and account quota without an agent turn. |
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 6 tools
The three ask_* tools target different agents (generic configured profiles, Antigravity, Codex), and the three get_*_info tools mirror that structure. However, the generic ask_agent/get_agent_info could be confused with the specific ask_antigravity/get_antigravity_info or ask_codex/get_codex_info if those agents are also configured, requiring careful reading of descriptions.
All tool names follow a clear ask_<target> or get_<target>_info pattern in consistent snake_case. The generic 'agent' target versus specific agent names is a meaningful distinction rather than a naming inconsistency.
Six tools is well-scoped for a delegation server, covering ask and info operations for both generic and specific agents without redundancy. Each tool earns its place.
The core ask and info operations are present, but there is no list_agents tool to discover which profiles are available in BRIDGE_AGENTS_JSON. This is a notable gap for a server centered on configured agents, as users must already know the agent names.