Skip to main content
Glama
superposed-labs

Fluxion Bus

by superposed-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Fluxion Bus

No user-submitted related servers found.

    Related Servers

    • agent-bus-mcp

      MustaphaSteph
      A
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server that connects AI coding agents (Claude Code, Codex, Cursor, etc.) on the same machine via a shared message bus, enabling them to chat, delegate tasks, and collaborate privately without cloud or internet.
      15 npm
      19
      MIT

    • CacheBash

      rezzedai
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that coordinates AI coding agents with mobile notifications, enabling task queues, inter-agent messaging, session monitoring, and human-in-the-loop approvals.
      MIT

    • Agent Switchboard

      FutureisinPast
      F
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that connects AI coding agents like Claude, Codex, and Gemini, enabling task routing, cross-model debates, and token-efficient context sharing without external APIs.
      15
      -

    • subway-mcp-server

      MauricioPerera
      A
      license
      A
      quality
      B
      maintenance
      Local MCP server that exposes delegation tools for Codex, Claude, and Antigravity CLI, enabling an orchestrator agent to assign tasks to these sub-agents via non-interactive CLI commands.
      3
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, and the lifecycle around run_subagent is well separated. The main risk is get_task_status vs get_task_result (both return run data with overlapping fields) and cancel_subagent_run vs force_cancel_subagent_run, though the latter is explicitly an escalation.

    Naming Consistency5/5

    Tool names consistently follow snake_case verb_noun: list_projects, get_project, run_subagent, get_task_status, cancel_subagent_run. Minor stylistic variants like force_cancel_ and wait_for_ are still in the same pattern and do not create confusion.

    Tool Count5/5

    13 tools is within the ideal range and each tool covers a distinct area of the subagent-run lifecycle, configuration, and maintenance. The count feels appropriate for the orchestration scope without redundant bulk.

    Completeness5/5

    The surface covers the full run lifecycle: submit, poll, retrieve results, cancel, force-cancel, and revert, plus supporting queries for projects, models, server status, authorization waits, and stale-run reconciliation. No obvious dead ends or missing critical operations.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources