Skip to main content
Glama
Sign In
seaweedsoup98

agentmux

by seaweedsoup98
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to agentmux

No user-submitted related servers found.

    Related Servers

    • CLI Subagents MCP Server

      lunati228
      A
      license
      B
      quality
      B
      maintenance
      Enables a host coding agent to launch and coordinate real subagent sessions in other agent CLIs and accounts, sharing existing MCP servers, skills, plugins, and instructions. Supports two-way messaging, automatic account failover, and mixed-CLI delegation while leaving credentials with the vendor CLIs.
      8
      11
      Apache 2.0

    • subturn

      eshatalov
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables any MCP client to launch and manage subagent sessions in installed coding agents like Codex, Claude Code, Grok, and OpenCode, using your existing logins and chosen models.
      10 npm
      MIT

    • agent-fleet-mcp

      s0wingseason
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables a lead AI agent to spawn and coordinate manager agents, which can in turn run child agents across Codex/ChatGPT, Google Antigravity, Claude Code, and local OpenAI-compatible models. Provides messaging, waiting, transcripts, file exchange, and saved-conversation adoption so multi-agent workflows can be orchestrated from MCP hosts.
      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

    B3.1/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools target distinct resources and actions: sessions, jobs, teams, messages, and provider metadata are clearly separated. The main ambiguity is between send and message_send, but their descriptions clarify session continuation versus persisted messaging.

    Naming Consistency3/5

    Naming is readable but mixes conventions: verb_noun (team_create, team_status), noun_verb (message_send, message_ack), bare verbs (send, wait, list, kill), and nouns (inbox, status, providers). The send/message_send pair is especially inconsistent.

    Tool Count3/5

    With 17 tools, the server is at the borderline of feeling heavy for an orchestration/mux utility. Each tool covers a distinct concern, but the count is above the typical well-scoped range.

    Completeness3/5

    The surface covers core session, job, team, and messaging workflows, but there are notable gaps: no way to list all jobs, no team deletion or update, and no session transcript/history retrieval. These gaps can force workarounds but basic orchestration is functional.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources