Skip to main content
Glama
joschi655

claude-code-mcp

by joschi655
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to claude-code-mcp

No user-submitted related servers found.

    Related Servers

    • agent-mux

      JinchengGao-Infty
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that manages interactive CLI agent pools using tmux, enabling creation, control, and communication with agents like Claude and Codex.
      7
      MIT

    • tmux-bridge-mcp

      Beatriceh4206
      A
      license
      Not graded
      quality
      A
      maintenance
      A standalone MCP server that lets AI coding agents running in separate tmux panes read each other's output, send messages and keystrokes, and coordinate multi-agent workflows through standard MCP tool calls. It shells out directly to tmux, so no external dependencies beyond tmux itself are required.
      36 npm
      MIT

    • aiterm-mcp

      kitepon
      A
      license
      A
      quality
      A
      maintenance
      Persistent tmux-backed MCP server that lets Claude Code control Codex CLI's interactive TUI, including slash commands and $imagegen. Run local shells, SSH, Docker, WSL, REPLs, and supported coding agents through durable PTY sessions.
      18
      686 npm
      6
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but session_stop and session_destroy both kill the tmux session, differentiated only by keeping metadata. Also, session_status, session_context, and session_tail all read session state, though they target different aspects. Descriptions clarify the boundaries sufficiently.

    Naming Consistency4/5

    The vast majority follow a consistent session_<verb> pattern (list, start, send, wait, tail, respond, interrupt, status, compact, destroy, stop). The claude_run tool deviates by using a different prefix, but it is still a clear, readable name that fits the server's purpose.

    Tool Count4/5

    At 15 tools, it sits at the upper edge of the ideal range. Each tool covers a distinct aspect of session lifecycle or health, so the count feels justified rather than bloated. It is slightly heavy but not excessive for the domain.

    Completeness5/5

    The tool set covers the full session lifecycle: create, send, wait, tail, respond, interrupt, compact, stop, destroy, plus one-shot execution and health/context checks. There are no obvious missing operations that would leave an agent stuck.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources