omnara
OfficialRelated Servers
Alternatives to omnara
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceStart, 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.171MIT
- AlicenseAqualityAmaintenanceThe 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.479MIT
- AlicenseBqualityDmaintenanceagent-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.72MIT
- AlicenseNot gradedqualityAmaintenanceOpen-source AI teammates for your company. The self-hosted agent layer: build, run and govern AI agents on your own servers, models and rules. RAG, skills, a real browser, 4,700+ MCP servers and an API, with budgets, approvals and an audit trail. Apache-2.0, built on Pydantic AI.172Apache 2.0
- AlicenseNot gradedqualityAmaintenanceConnects your own Claude subscription to applications via an OpenAI-compatible API, adding durable job queues, workflows, subagents, and a local management console.Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables 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.-
TDQS
Scored across 75 tools
Tools are generally scoped to a distinct resource and action, and descriptions clarify subtle distinctions such as grants vs. direct resource updates. A few pairs remain easy to confuse, especially grant_pools_edit vs. pools_update and grant_models_edit vs. models_update, but the overall surface is well differentiated.
Most names follow a predictable snake_case resource_action pattern, e.g. agents_list, crons_create, secrets_update, and grant_pools_add. Minor deviations such as whoami, tools_catalog, model_providers_catalog, and the use of edit for grant updates instead of update keep it from being fully consistent.
At 75 tools, the server is far beyond a practical MCP tool surface and will create significant selection and context overhead for agents. The broad platform scope explains some of the size, but many domains could be consolidated or split into narrower servers.
Core agent, cron, machine, pool, model, secret, and grant workflows are well covered, with strong lifecycle support in several areas. However, notable gaps remain, such as no skills_create/update, limited org/project lifecycle operations beyond create/list, and some resources lacking full get/update coverage.