codex-claude-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLAUDE_BRIDGE_HOME | No | Isolated config/state directory; default `~/.claude-reviews` | ~/.claude-reviews |
| CLAUDE_BRIDGE_CLAUDE_PATH | No | Explicit Claude executable or supported npm shim/JS entrypoint | |
| CLAUDE_BRIDGE_MCP_EXCLUDE | No | Comma-separated source MCP server names to omit | |
| CLAUDE_BRIDGE_SOURCE_HOME | No | Source Claude directory; otherwise inherited `CLAUDE_CONFIG_DIR` or `~/.claude` |
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 |
|---|---|
| claude_askA | Start an independent Claude Code session in a project. Claude can inspect the project and perform the requested task. Returns session_id for follow-ups. There is no enforced read-only sandbox. |
| claude_followupA | Continue a session returned by claude_ask, preserving its original directory and permission mode. Concurrent follow-ups on one session are serialized across bridge processes. |
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 2 tools
The two tools are cleanly separated by lifecycle stage: claude_ask starts a new session and claude_followup continues an existing one. There is no plausible confusion about which to call for a given intent.
Both names share the identical 'claude_' prefix in snake_case and use parallel action suffixes (ask/followup). The convention is applied uniformly across the entire surface.
Two tools is thin even for a narrow delegation server; only the start/continue pair exists. A focused purpose partly justifies it, but it sits at the borderline of minimalism.
The core start-and-continue workflow is covered, but there is no way to list, inspect, or terminate sessions, and no status/result-retrieval operation. These are notable lifecycle gaps for session management.