claude-mcp-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLAUDE_CLI_PATH | No | Path to CLI binary. | claude |
| ANTHROPIC_API_KEY | No | Anthropic API key. Required when using API key authentication (set CLAUDE_BRIDGE_USE_API_KEY=1). | |
| CLAUDE_QUERY_MODEL | No | Default model for query tool. | sonnet |
| CLAUDE_QUERY_EFFORT | No | Default effort for query tool. | |
| CLAUDE_SEARCH_MODEL | No | Default model for search tool. | sonnet |
| CLAUDE_DEFAULT_MODEL | No | Shared default model for all tools. If not set, each tool uses its own default. | |
| CLAUDE_SEARCH_EFFORT | No | Default effort for search tool. | medium |
| CLAUDE_FALLBACK_MODEL | No | Fallback model on quota exhaustion. Set to 'none' to disable. | haiku |
| CLAUDE_MAX_BUDGET_USD | No | Global cost cap in USD per call. | |
| CLAUDE_MAX_CONCURRENT | No | Max concurrent subprocess spawns. | 3 |
| CLAUDE_STRUCTURED_MODEL | No | Default model for structured tool. | sonnet |
| CLAUDE_BRIDGE_USE_API_KEY | No | Set to '1' to forward ANTHROPIC_API_KEY to the subprocess. Default uses subscription auth. |
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 |
|---|---|
| queryA | Execute a prompt via Claude Code CLI with optional file context and session resume. Claude is an AI coding agent that can generate, analyze, refactor, and explain code. Capabilities: code generation and refactoring, code analysis and explanation, file understanding (text and images), multi-turn conversations via sessionId. Cost: Default model is Sonnet (~$0.01-0.10/call). Use effort="low" for simple tasks, effort="high" + model="opus" for complex analysis. Set maxBudgetUsd to cap per-call cost (recommended for effort="max" or model="opus"). Tips:
|
| structuredA | Generate JSON conforming to a provided JSON Schema. Uses Claude CLI's native --json-schema flag for validated output (not client-side validation). Use for: data extraction from text/files, classification, entity parsing, or any task needing machine-parseable output. Cost: Similar to query (~$0.01-0.10/call). Schema complexity doesn't significantly affect cost. Tips:
|
| searchA | Web search via Claude Code CLI using WebSearch and WebFetch tools. Searches the web and synthesizes a comprehensive answer with source URLs. Use for: current information, documentation lookups, API references, comparing libraries, and research questions. Cost: Typically ~$0.02-0.05/search with Sonnet. Tips:
|
| listSessionsA | List active Claude CLI sessions tracked by this server. Returns session metadata (IDs, models, timing, turn counts, cumulative cost) for orchestration. Use to check available sessions before resuming with sessionId. No cost (local lookup only). |
| pingA | Health check: verifies Claude CLI is installed and authenticated, reports versions, capabilities, and configuration. No cost (local check only). |
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 5 tools
Each tool serves a clearly distinct purpose: listing sessions, health checking, executing prompts, web searching, and structured JSON generation. No overlap or ambiguity.
Tool names follow no consistent pattern: 'listSessions' uses camelCase verb_noun, 'ping' and 'query' are single-word verbs, 'search' is a verb, 'structured' is an adjective. Mixing conventions makes the naming unpredictable.
With 5 tools covering session management, health check, code query, web search, and structured output, the count is well-scoped for the server's purpose of bridging to Claude CLI.
The tool set covers the core intended actions (query, search, structured output) and adds session listing and health check. Minor gaps exist (no tool to create or manage sessions beyond listing), but agents can work around them.