Skip to main content
Glama
KunihiroS

claude-code-mcp

by KunihiroS

Related Servers

Alternatives to claude-code-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A Node.js/TypeScript MCP server template with sample tools (ping and system_info) that demonstrates how to build custom tools for Claude Desktop using stdio transport.
      3 npm
      ISC
    • F
      license
      Not graded
      quality
      D
      maintenance
      A demonstration project showing how to set up and use a custom MCP server with Claude Desktop, providing example tools and resources.
      -
    • A
      license
      Not graded
      quality
      F
      maintenance
      A fully working MCP server built from scratch in plain Node.js, implementing tools, resources, prompts, notifications, and sampling according to the MCP specification, designed to connect to Claude Desktop or any MCP client.
      32
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Local MCP server that wraps the headless Claude Code CLI as MCP tools, providing stateless access to Claude's coding capabilities through prompt-based interactions. It enables users to execute Claude Code commands with various prompt formats and structured outputs directly from MCP clients.
      3
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      An MCP server that implements Claude Code-like functionality, allowing the AI to analyze codebases, modify files, execute commands, and manage projects through direct file system interactions.
      15
      304
      MIT

    TDQS

    C2.7/5.0

    Scored across 7 tools

    Disambiguation3/5

    There is significant overlap between edit_code, fix_code, and review_code, as all involve modifying or analyzing code for improvements, which could confuse an agent about which to use for specific tasks. However, explain_code, simulate_command, test_code, and your_own_query have more distinct purposes, providing some clarity.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (e.g., edit_code, explain_code, fix_code), which is predictable and readable. The only deviation is your_own_query, which uses a different style but doesn't severely disrupt the overall consistency.

    Tool Count5/5

    With 7 tools, the count is well-scoped for a code-focused server, falling within the typical 3-15 range. Each tool appears to serve a specific purpose in code development and analysis, making the set appropriately sized for the domain.

    Completeness4/5

    The tool set covers key aspects of code interaction such as editing, explaining, fixing, reviewing, simulating, testing, and custom queries, which aligns well with a code assistant domain. Minor gaps might include operations like code generation or version control integration, but core workflows are adequately supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues