claude-code-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XBY_APIKEY | Yes | 你的实际apikey (Your actual 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| claude_codeB | Claude Code Agent: Your versatile multi-modal assistant for code, file, Git, and terminal operations via Claude CLI. Use • File ops: Create, read, (fuzzy) edit, move, copy, delete, list files, analyze/ocr images, file content analysis └─ e.g., "Create /tmp/log.txt with 'system boot'", "Edit main.py to replace 'debug_mode = True' with 'debug_mode = False'", "List files in /src", "Move a specific section somewhere else" • Code: Generate / analyse / refactor / fix └─ e.g. "Generate Python to parse CSV→JSON", "Find bugs in my_script.py" • Git: Stage ▸ commit ▸ push ▸ tag (any workflow) └─ "Commit '/workspace/src/main.java' with 'feat: user auth' to develop." • Terminal: Run any CLI cmd or open URLs └─ "npm run build", "Open https://developer.mozilla.org" • Web search + summarise content on-the-fly • Multi-step workflows (Version bumps, changelog updates, release tagging, etc.) • GitHub integration Create PRs, check CI status • Confused or stuck on an issue? Ask Claude Code for a second opinion, it might surprise you! Prompt tips
|
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
With only one tool, there is no possibility of confusion between tools. The single tool 'claude_code' has a clearly defined purpose as a multi-modal assistant for code, file, Git, and terminal operations, so agents cannot misselect between non-existent alternatives.
A single tool inherently has perfect naming consistency since there are no other tools to compare against. The name 'claude_code' follows a clear pattern and stands alone without conflicting conventions.
One tool is too few for the broad scope described, which includes file operations, code analysis, Git workflows, terminal commands, web search, GitHub integration, and multi-step workflows. A single tool forces all these diverse functionalities into one interface, making it less scoped and potentially confusing for agents to navigate specific operations.
The tool surface is severely incomplete as a set, with only one tool covering an extensive domain. While the single tool may offer many capabilities internally, the lack of specialized tools for distinct operations (e.g., separate tools for file ops, Git, terminal) creates gaps in the MCP interface, likely causing agent failures due to unclear boundaries and missing targeted endpoints.