Skip to main content
Glama
Sign In
agent-discussion-mcp

agent-discussion-mcp

by ewanni
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to agent-discussion-mcp

No user-submitted related servers found.

    Related Servers

    • api_agent_mcp

      ewanni
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to define and run reusable role-based agent profiles that complete tasks alone or in bounded multi-agent discussions with independent proposals, parallel critiques, an independent judge verdict, and optional revision rounds, persisting all session events to a local SQLite log. It works over MCP stdio with any OpenAI-compatible chat completions endpoint and exposes profiles as resources.
      MIT

    • OmniFix MCP Server

      Soumo04
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to execute and validate autonomous multi-agent workflows with tools for workflow execution, output validation, and execution logging, plus resources and prompts for task decomposition and error recovery.
      MIT
    • SimArch MCP Server

      SimArch MCP Serverofficial

      isiraglobal
      A
      license
      B
      quality
      B
      maintenance
      Enables AI tools and agents to form contract-bound organizations, execute persistent task DAGs with independent audits, score decisions with counterfactual trees, run time-compressed world simulations, and control an on-demand localhost dashboard via stdio tools.
      6
      1
      Apache 2.0
    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

    B3.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct action on a clearly identified resource: profile CRUD (create/update/list) versus execution (run_solo for one agent, run_discussion for multi-agent with a judge). The descriptions clearly delineate the two execution modes, so there is little risk of misselection.

    Naming Consistency4/5

    Names follow a mostly consistent verb_noun pattern (create_agent, update_agent, run_solo, run_discussion). The only minor deviation is plural 'list_agents' versus singular elsewhere, but the convention remains predictable and readable.

    Tool Count4/5

    Five tools is slightly lean for a profile-management plus execution server, but each tool earns its place covering profile lifecycle and both single- and multi-agent runs. Nothing appears redundant or padded.

    Completeness3/5

    The profile lifecycle lacks delete and get/read-single operations, so an agent can create, update, and list profiles but cannot remove or fetch one specifically. Execution paths are covered, but the CRUD surface has a notable gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources