Skip to main content
Glama
trevoraspencer

claudecode-mcp

by trevoraspencer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to claudecode-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-agents

      thomaswitt
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that wraps AI CLI tools — Claude Code, Antigravity CLI, and Codex CLI — so any MCP client can call them as tools.
      299 npm
      18
      MIT

    • claude-bridge-mcp

      0motionguy
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that exposes your local Claude Code CLI over HTTP+SSE, enabling any MCP-compatible client to use your Claude Code MAX/PRO subscription remotely.
      7 npm
      2
      MIT

    • Claude Code MCP

      auchenberg
      A
      license
      B
      quality
      D
      maintenance
      An implementation of Claude Code as a Model Context Protocol server that enables using Claude's software engineering capabilities (code generation, editing, reviewing, and file operations) through the standardized MCP interface.
      8
      14 npm
      188
      MIT

    • code-bridge

      ITSWProj
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that bridges Claude Desktop with Claude Code, allowing users to delegate tasks to Claude Code directly from Claude Desktop conversations, supporting both synchronous and background execution with session reuse.
      2 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools have clearly distinct purposes: one returns plain text, one returns structured JSON, and one accepts additional context/files. However, the core functionality of running a one-shot prompt is identical across all three, which could cause minor confusion about when to use each variant.

    Naming Consistency5/5

    All tool names follow a perfect 'claude_prompt_' prefix pattern with descriptive suffixes (_structured, _with_context). The naming is completely consistent and predictable, making it easy to understand the tool hierarchy at a glance.

    Tool Count4/5

    Three tools is reasonable for a Claude Code CLI interface, covering the main variations needed (text, structured, contextual). However, this feels slightly minimal - additional tools for session management or configuration might be expected but aren't strictly necessary for the stated headless, stateless approach.

    Completeness3/5

    The tools cover the basic prompt execution variations well, but there are notable gaps for a complete Claude Code CLI surface. Missing operations include session management (contradicting the stateless approach), model selection, parameter tuning, streaming responses, and error handling tools that would be expected for production use.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources