Skip to main content
Glama
xiaobenyang-com

claude-code-mcp

by xiaobenyang-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

MCP服务器开发工具包

一个用于使用FastMCP构建模型上下文协议(MCP)服务器并部署到Google Cloud Run的综合指南和模板集合。 A comprehensive guide and template collection for building model Context Protocol (MCP) servers using FastMCP and deploying them to Google Cloud Run.## 工具列表 Tool List

本MCP服务封装下列工具，可让模型通过标准化接口调用以下功能。 本MCP服务封装下列工具，可让模型通过标准化接口调用以下功能。

工具 Tool

描述 Description

claude_code

Claude Code Agent: Your versatile multi-modal assistant for code, file, Git, and terminal operations via Claude CLI. Use workFolder for contextual execution. • 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 1. Be concise, explicit & step-by-step for complex tasks. No need for niceties, this is a tool to get things done. 2. For multi-line text, write it to a temporary file in the project root, use that file, then delete it. 3. If you get a timeout, split the task into smaller steps. 4. Seeking a second opinion/analysis: If you're stuck or want advice, you can ask claude_code to analyze a problem and suggest solutions. Clearly state in your prompt that you are looking for analysis only and no actual file modifications should be made. 5. If workFolder is set to the project path, there is no need to repeat that path in the prompt and you can use relative paths for files. 6. Claude Code is really good at complex multi-step file operations and refactorings and faster than your native edit features. 7. Combine file operations, README updates, and Git commands in a sequence. 8. Claude can do much more, just ask it!

检查服务 ## Inspector

工具在线测试： https://mcp.xiaobenyang.com/inspector/1777316659367939

Online Tool test https://mcp.xiaobenyang.com/inspector/1777316659367939

Related MCP server: Boilerplate MCP

服务配置 MCP Server Config

如何获取 XBY-APIKEY ？ How to get XBY-APIKEY ?

访问小笨羊科技网站 https://xiaobenyang.com，注册用户即可获得APIKEY Visit XiaoBenYang website https://xiaobenyang.com, register and get the APIKEY.

SSE

{
  "mcpServers": {
    "MCP服务器开发工具包": {
      "headers": {
        "XBY-APIKEY": "<YOUR_XBY_APIKEY>"
      },
      "type": "sse",
      "url": "https://mcp.xiaobenyang.com/1777316659367939/sse"
    }
  }
}

STREAMABLE HTTP

{
  "mcpServers": {
    "MCP服务器开发工具包": {
      "headers": {
        "XBY-APIKEY": "<YOUR_XBY_APIKEY>"
      },
      "type": "streamable_http",
      "url": "https://mcp.xiaobenyang.com/1777316659367939/mcp"
    }
  }
}

STDIO

{
    "mcpServers": {
        "MCP服务器开发工具包": {
          "command": "npx",
          "args": [
            "-y",
            "xiaobenyang-mcp"
          ],
          "env": {
            "XBY_APIKEY": "<YOUR_XBY_APIKEY>",
            "mcpId": "1777316659367939",
          },
          "transport": "stdio"
        }
      }
}

Available Tools

1 tool
claude_codeclaude_codeB

Claude Code Agent: Your versatile multi-modal assistant for code, file, Git, and terminal operations via Claude CLI. Use workFolder for contextual execution.

• 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

  1. Be concise, explicit & step-by-step for complex tasks. No need for niceties, this is a tool to get things done.

  2. For multi-line text, write it to a temporary file in the project root, use that file, then delete it.

  3. If you get a timeout, split the task into smaller steps.

  4. Seeking a second opinion/analysis: If you're stuck or want advice, you can ask claude_code to analyze a problem and suggest solutions. Clearly state in your prompt that you are looking for analysis only and no actual file modifications should be made.

  5. If workFolder is set to the project path, there is no need to repeat that path in the prompt and you can use relative paths for files.

  6. Claude Code is really good at complex multi-step file operations and refactorings and faster than your native edit features.

  7. Combine file operations, README updates, and Git commands in a sequence.

  8. Claude can do much more, just ask it!

ParametersJSON Schema
NameRequiredDescriptionDefault
promptYes
workFolderNo

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It does reveal some behavioral traits: it mentions timeout handling strategies, the ability to run 'any CLI cmd', and that it's 'faster than your native edit features'. However, it lacks critical information about permissions required, rate limits, whether operations are reversible/destructive, authentication needs, or error handling patterns. The description mentions file deletion capabilities but doesn't explicitly warn about destructive operations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is excessively long (over 500 words) with redundant information and promotional language. While it starts with a clear purpose statement, it then includes extensive bullet lists, examples, and tips that could be more efficiently organized. Sentences like 'Claude can do much more, just ask it!' and 'it might surprise you!' don't add functional value. The structure with multiple bullet levels and emojis is visually cluttered rather than information-dense.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 2 parameters, no annotations, and no output schema, the description provides substantial context about capabilities and usage patterns. However, it's incomplete regarding parameter documentation, error handling, and operational constraints. The extensive examples and tips compensate somewhat, but critical information about what the tool returns, how errors manifest, and security/permission requirements is missing. The description feels more like marketing material than complete technical documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage and 2 parameters (prompt and workFolder), the description provides minimal parameter guidance. It mentions 'Use `workFolder` for contextual execution' and provides one example about relative paths when workFolder is set, but doesn't explain the prompt parameter's expected format, constraints, or structure. Given the low schema coverage, the description should compensate more by explaining both parameters' purposes and usage patterns beyond the single workFolder mention.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states this is a 'versatile multi-modal assistant for code, file, Git, and terminal operations via Claude CLI' with specific examples across multiple domains. It provides a comprehensive overview of capabilities including file operations, code generation/analysis, Git workflows, terminal commands, web search, and GitHub integration. However, since there are no sibling tools mentioned, it doesn't need to differentiate from alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear usage context through the 'Prompt tips' section with 8 specific guidelines, including when to use relative paths, how to handle multi-line text, timeout strategies, and when to seek analysis vs. execution. It explicitly states 'No need for niceties, this is a tool to get things done' and offers guidance for complex multi-step workflows. However, it doesn't explicitly state when NOT to use this tool or compare it to alternatives (though none are mentioned).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedclaude_code
Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.3/5.0

Scored across 1 tool

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness2/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • Xava Labs MCP Template

    null-shot
    A
    license
    Not graded
    quality
    C
    maintenance
    A template repository for building Model Context Protocol (MCP) servers that enables developers to create interactive AI agents with real-time bidirectional communication capabilities through WebSocket and SSE endpoints.
    MIT

  • Skeleton MCP Server

    nickweedon
    A
    license
    A
    quality
    D
    maintenance
    A template project for building Model Context Protocol servers with FastMCP framework, Docker support, and example CRUD API implementation to help developers quickly bootstrap their own MCP servers.
    6
    MIT

  • Simple Remote MCP Server

    ParthSharma1197
    F
    license
    B
    quality
    D
    maintenance
    A template and demonstration project for building, testing, and deploying remote MCP servers using FastMCP and uv. It provides a foundational structure for creating MCP-compliant tools that can be hosted publicly and integrated with LLM agents.
    2
    -