Skip to main content
Glama
Sign In
moa-mcp

moa-mcp

by cvanes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to moa-mcp

No user-submitted related servers found.

    Related Servers

    • AgentTasker MCP Server

      S3bRR
      A
      license
      B
      quality
      C
      maintenance
      A lightweight stdio-only MCP server that allows AI agents to run multiple tasks (e.g., Python code, HTTP requests, shell commands) in parallel or with dependencies, returning structured results in a single call.
      2
      36 PyPI
      MIT

    • mcp-second-opinion

      aleksbuss
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that queries a panel of LLMs from different providers via OpenRouter and returns their answers side by side, optionally synthesizing them to highlight disagreements.
      4 npm
      1
      MIT

    • Roundtable AI

      dQureshi71
      F
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets a primary AI assistant delegate parts of a prompt to specialized sub-agent CLIs (Gemini, Claude, Codex, Cursor), which run in parallel against a shared context bundle. It then aggregates their findings into a single synthesized response, using existing CLI tools and subscriptions with no extra cost.
      -

    • Roundtable AI MCP Server

      kevinlacroix80
      F
      license
      Not graded
      quality
      A
      maintenance
      This local MCP server lets a primary AI assistant delegate tasks in parallel to specialized sub-agent CLIs (Gemini, Claude, Codex, Cursor) that share the same project context, then aggregates and synthesizes their findings into one response. It uses existing CLI tools and API subscriptions with no markup, supporting 26+ MCP-compatible IDEs.
      -
    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.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes: one lists available models, the other executes prompts. There is no overlap or ambiguity in their functionality.

    Naming Consistency5/5

    Both tool names follow a consistent verb_noun pattern: 'list_models' and 'execute_prompt'. The naming style is uniform and predictable.

    Tool Count3/5

    With only 2 tools, the server feels thin for a typical MCP server, but the two tools cover a minimal end-to-end workflow (discover models, execute prompts). This is borderline acceptable but not a rich toolkit.

    Completeness5/5

    For the stated purpose of executing single-turn prompts against models, the surface is complete: list_models provides the necessary metadata to call execute_prompt, and execute_prompt handles the execution. No obvious gaps exist within this narrow scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources