Skip to main content
Glama

Related Servers

Alternatives to omnara

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Start, observe, and interact with Claude Managed Agents from any MCP client — launch an agent, watch its events, reply, approve the tools it wants to run, and stop it. Runs over stdio, HTTP, or AWS Lambda with pluggable auth.
      17
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      The infrastructure for AI teams: a self-hosted server that gives a fleet of agents shared semantic memory, tasks, direct messages, and session handoff. Any agent that speaks HTTP participates: Claude Code, AutoGen, raw API scripts, anything.
      47
      9
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      agent-mq is a message queue that enables AI coding agents to communicate with each other across sessions and machines. Agents can send messages, delegate tasks, and coordinate work — all through MCP tools. Supports Claude Code, Cursor, Codex, OpenClaw, and any MCP-compatible tool. UUID-based authentication with per-user data isolation. Self-hostable with Docker.
      7
      2
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables deployment of autonomous AI agents with memory and tool execution capabilities through a WebSocket-based MCP protocol. Provides production-ready infrastructure with REST API access, persistent state management, and extensible function registry for building self-hosted AI systems.
      -
    • A
      license
      A
      quality
      D
      maintenance
      Multi-agent orchestration server that enables parallel task delegation, sequential pipelines, cron scheduling, and cross-model peer review via CLI providers like Codex, Antigravity, OpenCode, and Claude Code.
      42
      7 npm
      6
      MIT

    TDQS

    C2.4/5.0

    Scored across 75 tools

    Disambiguation3/5

    The set contains many parallel tool pairs such as models_delete vs grant_models_delete, pools_delete vs grant_pools_delete, and secrets_create vs grant_secrets_add, which could cause misselection without careful reading. Descriptions clarify boundaries, but the sheer number of tools with grant/non-grant and resource/action variations creates moderate ambiguity.

    Naming Consistency4/5

    Nearly all tool names use snake_case with a resource-first pattern (e.g., agents_get, models_create, grant_pools_add), which is predictable and readable. Minor deviations exist: grants use add/edit while base resources use create/update, and a few tools like whoami or profiles_rename break the verb pattern.

    Tool Count1/5

    75 tools is an extreme mismatch for a single MCP server. While the domain is broad, this count far exceeds typical well-scoped ranges (3–15) and is likely to overwhelm an agent's selection process.

    Completeness3/5

    Core resources like secrets, machines, pools, crons, and grants have near-complete CRUD coverage. However, notable gaps exist: no configs_list/update/delete, no projects_get/update/delete, no skills_create, and no models_get, which will limit several agent workflows.