Omi MCP Server
Related Servers
Alternatives to Omi MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides AI agents with persistent memory capabilities through Mem0, allowing them to store, retrieve, and semantically search memories.684MIT
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that integrates AI assistants with Mem0.ai's persistent memory system, allowing models to store, retrieve, search, and manage different types of memories.16MIT
- AlicenseDqualityDmaintenanceA Model Context Protocol server that enables access to Omi memories from a specific user account through a tool interface.1221 npm2MIT
- FlicenseBqualityDmaintenanceA Model Context Protocol server that provides persistent memory capabilities for AI systems, enabling true continuity of consciousness across conversations through episodic, semantic, procedural, and strategic memory types.246-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server implementation that provides a standardized interface for applications to interact with OpenRouter's language models through a unified conversation management system.5 npm2MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that provides knowledge graph-based persistent memory for LLMs, allowing them to store, retrieve, and reason about information across multiple conversations and sessions.9114,646 npm2MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: create vs. read operations for two distinct resources (conversations and memories). The separation between conversations and memories is explicit, and the create/read distinction is unambiguous, leaving no room for confusion or misselection.
All tool names follow a consistent verb_noun pattern with 'create' or 'read' as the verb and 'omi_conversations' or 'omi_memories' as the noun. The naming is perfectly uniform, using snake_case throughout, making the set highly predictable and readable.
With 4 tools, the count is reasonable for a server focused on Omi conversations and memories. It covers create and read operations for both resources, which is well-scoped, though it might feel slightly thin if update or delete operations are expected in the domain, but it's not a significant issue.
The tool set provides create and read operations for both conversations and memories, covering basic CRUD elements. However, there are notable gaps: no update or delete tools for either resource, which could limit agent workflows if modifications or deletions are needed, making the surface incomplete for full lifecycle management.