agent-bridge
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| delegateA | Delegate a task to another coding agent (Claude Code or Codex) and return its final output. Use this to hand work to the other agent. |
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 1 tool
Only a single tool exists, so there is no possibility of confusion with other tools. The delegate tool's purpose is clearly described as handing tasks to another agent.
With only one tool, naming consistency is trivially maintained. The name 'delegate' is a clear, imperative verb that matches its action.
The server has exactly one tool, which is borderline and feels thin for a 'bridge' concept. While it covers the core delegation operation, a single tool is at the low end of acceptable scoping.
The delegate tool covers the primary task of handing work to another agent, but there are no tools to discover available agents, check statuses, or manage the bridge. This leaves notable gaps for a full agent-bridge lifecycle.