MCP-Claude Code Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | Yes | Your Anthropic API key |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| claude_code_taskC | Execute a coding task using Claude Code CLI |
| create_projectC | Create a new project directory |
| list_filesC | List files in a project directory |
| read_fileC | Read contents of a file |
| run_commandC | Run a shell command in the project directory |
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
Most tools have distinct purposes: claude_code_task for coding execution, create_project for project setup, list_files and read_file for file inspection, and run_command for shell operations. However, claude_code_task and run_command could potentially overlap if coding tasks involve shell commands, but their descriptions help differentiate them.
The naming is mixed: claude_code_task uses a descriptive compound name, while the others follow a verb_noun pattern (create_project, list_files, read_file, run_command). This inconsistency is noticeable but still readable, as most tools use clear verbs and nouns.
With 5 tools, the count is reasonable for a code bridge server, covering project creation, file operations, and command execution. It feels slightly thin for broader coding workflows, but each tool serves a clear purpose without obvious bloat.
The toolset covers basic project and file operations, but there are notable gaps for a code-focused domain: no tools for writing/modifying files, deleting files, or managing dependencies. This could limit agent workflows, though core inspection and execution are present.