Skip to main content
Glama
Sign In
michael-abdo

tmux-claude MCP Server

by michael-abdo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to tmux-claude MCP Server

No user-submitted related servers found.

    Related Servers

    • session-manager

      horiu
      A
      license
      A
      quality
      A
      maintenance
      Enables Claude Code and Codex to turn an ordinary conversation into an orchestrator that spawns, names, monitors, and revives separate work sessions, aggregates their questions for a single confirmation, and throttles parallelism based on memory and usage limits. Reports results back as a summary table without needing any extra app, daemon, or tmux.
      12
      MIT

    • maestro

      daniel-madrid-07
      A
      license
      A
      quality
      A
      maintenance
      Enables Claude Code to launch and supervise multiple concurrent Claude Code sessions in tmux, sending them briefs, reading their progress, answering their prompts, and managing isolated git worktrees.
      20
      2
      MIT

    • claude-code-mcp

      joschi655
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that gives orchestrator agents fine-grained control over interactive Claude Code sessions running inside tmux, enabling mid-session steering, interruption, and token-efficient result extraction.
      15
      MIT

    • wezterm-agent-mcp

      multiagentcognition
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables orchestration of multiple AI coding agents (Claude Code, Gemini CLI, etc.) in isolated Wezterm panes, allowing one agent to spawn, monitor, and communicate with others across projects.
      8 npm
      1
      -
    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

    B3.2/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct operation: workspace management, instance lifecycle, parallel execution, and git operations. Tools like check_workspace_conflicts and get_workspace_status have clear boundaries, and even similar-sounding ones like distributeWork and executeParallel are differentiated by context (scheduling vs. running).

    Naming Consistency3/5

    The set uses a mix of snake_case (e.g., check_workspace_conflicts, commit_manager_work) and camelCase (e.g., distributeWork, executeParallel), plus short verbs (list, send, read). While each subgroup is internally consistent, the overall pattern is not uniform, which may cause slight confusion.

    Tool Count4/5

    14 tools cover the main aspects of instance management and workspace coordination without being excessive. The scope is well-defined, and each tool serves a necessary role in the multi-instance workflow.

    Completeness4/5

    The tool surface covers the key lifecycle operations (spawn, terminate, restart, send/read), parallel execution, and basic git workflow (commit, sync, merge). Minor gaps exist (e.g., no explicit tool for listing workspace files or pruning instances), but the core functionality is solid.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources