@omnidim-ai/mcp-server
Related Servers
Alternatives to @omnidim-ai/mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides a stdio MCP server for single-user local operation of the otaman platform, enabling agent orchestration, slash commands, and skill management within Claude Code without a remote bridge daemon.2AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceProvides a production-ready Model Context Protocol server with dual STDIO and Streamable HTTP transports, enabling file operations, memory, database queries, RAG, web search, GitHub integration, background tasks, and prompt-based workflows.MIT
- AlicenseAqualityCmaintenanceProvides a Model Context Protocol server with tools for knowledge base search, retrieval, and addition, plus system time, resources, and prompts. Supports stdio and Streamable HTTP transports for local and shared deployments.4MIT
- FlicenseAqualityDmaintenanceMCP server that wraps MiniMax platform APIs (speech, video, image, music, and file management) as tools over stdio, enabling natural language interaction with MiniMax's AI services.161-
- AlicenseBqualityDmaintenanceA minimal local MCP server that wraps any Claude Messages API-compatible upstream into a unified ask_model tool. It enables MCP clients to interact with these models through a standard tool interface using stdio transport.17MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that supports STDIO, SSE and Streamable HTTP protocols for AI model interactions.9 npm1MIT
TDQS
Scored across 79 tools
Most tools target a clearly distinct resource+action, and the descriptions actively disambiguate overlapping cases (e.g. updateAgent vs. updatePostCallAction vs. addPostCallAction, and testWorkflow vs. getWorkflowExecution). Some overlap remains among the provider tools (listLLMProviders/listSTTProviders/listTTSProviders/listAllProviders/getVoice/listVoices) and the multiple agent-version tools, but the boundaries are generally spelled out.
The set is almost entirely camelCase verb_noun (createAgent, listCallLogs, deleteWorkflow, publishWorkflow), which is very predictable. The one clear deviation is bulkCallActions, a noun phrase with no leading verb, breaking the otherwise uniform verb_noun pattern.
At 79 tools this is far beyond the 25+ 'heavy' threshold, even for a broad voice-AI platform. The surface legitimately spans many subdomains (agents, calls, bulk calls, workflows, numbers, voices, KB, billing), and the tags group them well, but the count is still excessive and several endpoint families could be consolidated.
Coverage is broad and lifecycle-complete across most domains: full CRUD for agents, versions (diff/restore/rename), workflows (create/edit/validate/publish/activate), bulk calls (create/start/retry/contacts/numbers/status), phone numbers, voice cloning, knowledge base, and billing. Only minor gaps exist, such as per-resource lookup helpers or session lifecycle management beyond creation.