agents-bridge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BRIDGE_DEBUG | No | Enable debug logging to stderr | |
| BRIDGE_DEPTH | No | Current recursion depth (set automatically) | 0 |
| BRIDGE_TIMEOUT_MS | No | Subprocess timeout in milliseconds | 600000 |
| AGENTS_BRIDGE_HOME | No | Override job storage location (default is ~/.agents-bridge) | |
| BRIDGE_MAX_RETRIES | No | Auto-retries on transient errors (rate limits, 5xx, network) | 2 |
| AGENTS_BRIDGE_CODEX_BIN | No | Point at an alternative Codex executable | |
| AGENTS_BRIDGE_CLAUDE_BIN | No | Point at an alternative Claude executable |
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 |
|---|---|
| codex_queryB | Ask OpenAI Codex a question or give it a task. Use for getting a second opinion, exploring unfamiliar code, or tasks that benefit from a different model's perspective. |
| codex_review_codeB | Ask Codex to review code. Provide a git diff range, file paths, or a code snippet. Returns specific, actionable feedback. |
| codex_review_planA | Ask Codex to critique an implementation plan. Identifies gaps, risks, missing edge cases, and suggests improvements. |
| codex_explain_codeB | Ask Codex to deeply explain code, logic, or architecture. Useful for understanding unfamiliar code, onboarding, or documenting complex systems. |
| codex_plan_perfB | Ask Codex to analyze performance and create an improvement plan. Identifies bottlenecks, proposes ranked optimizations with expected impact. |
| codex_implementA | Ask Codex to implement a feature, fix a bug, or make code changes. WARNING: This modifies your codebase. Returns a summary of what was changed. |
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
Each tool has a distinct primary purpose, but codex_query is a generic catch-all that could overlap with the specialized tools. codex_review_plan and codex_plan_perf also have some conceptual overlap around planning, though their descriptions differentiate them.
All names use a consistent codex_ prefix and snake_case, following a clear verb or verb_noun pattern. Minor deviation: codex_query and codex_implement are single verbs, while others are compound.
Six tools is well-scoped for a Codex bridge, covering query, review, explanation, performance planning, implementation, and code review. Each tool appears to earn its place without excessive fragmentation.
The surface covers core Codex use cases: asking questions, reviewing plans/code, explaining code, performance analysis, and implementing changes. Minor gaps exist for specialized tasks like test generation or refactoring, but these can be handled via codex_query or codex_implement.