Omi Memories MCP Server
Servidor MCP de Omi Memories
Este es un servidor de Protocolo de Contexto de Modelo (MCP) que proporciona acceso a las memorias Omi para un usuario específico a través de una interfaz de herramientas.
Características
Herramienta para obtener todas las memorias para el ID de usuario especificado desde la aplicación OMI
Related MCP server: MCP-Mem0
Configuración
Instalar dependencias:
npm installConfigura tu ID de usuario:
Abrir
src/server.tsActualice la constante
SPECIFIC_USER_IDcon su ID de usuario desde la sección Cuenta de la aplicación Omira
Construya el código TypeScript:
npm run buildIniciar el servidor:
npm startHerramientas disponibles
buscar recuerdos
Obtiene todas las memorias para el ID de usuario configurado.
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StdioClientTransport } from "@modelcontextprotocol/sdk/client/stdio.js";
const transport = new StdioClientTransport({
command: "node",
args: ["dist/server.js"]
});
const client = new Client(
{
name: "example-client",
version: "1.0.0"
},
{
capabilities: {
tools: {}
}
}
);
await client.connect(transport);
// Fetch memories using the tool
const result = await client.callTool({
name: "fetch-memories",
arguments: {}
});
console.log(result.content[0].text);Configuración
El servidor espera:
La API Express se ejecutará en
http://localhost:3000El ID de usuario debe configurarse: actualice la constante
SPECIFIC_USER_IDensrc/server.tscon su ID de usuario que puede obtener de la sección Cuenta de la aplicación Omira.
Integración de escritorio de Claude
Para integrarse con Claude Desktop, actualice su configuración de Claude Desktop ( claude_desktop_config.json ) para incluir:
{
"mcpServers": {
"omi-mcp": {
"command": "node",
"args": [
"/path/to/your/mcp-server/dist/server.js"
],
"env": {
"NODE_ENV": "development"
}
}
}
} Integración de Cursor IDE
Para integrar con Cursor IDE:
Abrir la configuración de Cursor IDE
Vaya a la configuración de "IA y copiloto".
En "Protocolo de contexto de modelo", agregue un nuevo servidor MCP con estas configuraciones:
{
"name": "Omi Memories",
"command": "node",
"args": [
"/path/to/your/mcp-server/dist/server.js"
],
"cwd": "/path/to/your/mcp-server",
"env": {
"NODE_ENV": "development"
}
}Reemplace /path/to/your/mcp-server con la ruta real al directorio de instalación del servidor MCP.
Available Tools
1 toolfetch-memoriesD
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v1.0.0- Changed
fetch-memories1 field changed- removed
Input schema / additionalPropertiesRemoved value: -false
1 tool update
- First observed
fetch-memories
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'fetch-memories' stands alone with a distinct purpose, making disambiguation trivial.
The single tool name 'fetch-memories' follows a clear verb_noun pattern. Since there is only one tool, consistency is inherently perfect with no deviations or mixed conventions to evaluate.
A single tool is too few for a server named 'Omi Memories MCP Server', which suggests a domain involving memory storage or retrieval. This minimal set likely leaves significant functionality uncovered, making it inappropriate for the implied scope.
Inferred from the server name and tool name, the domain involves memories, but with only a fetch operation, there are obvious gaps such as creating, updating, deleting, or searching memories. This severely incomplete surface will cause agent failures in handling memory lifecycles.
Maintenance
Related MCP Connectors
Model Context Protocol server for Studex tools, notifications, and profile integrations
Cross-tool persistent memory and context for AI assistants over MCP.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
An MCP memory server. One memory your agents share — across models, devices and apps.
Related MCP Servers
- FlicenseBqualityDmaintenanceA Model Context Protocol server that enables AI assistants to interact with the Omi API for retrieving and creating conversations and memories for users.44-
- 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 gradedqualityDmaintenanceA server that implements the Model Context Protocol, providing a standardized way to connect AI models to different data sources and tools.8 npm11MIT
- 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.9162,542 npm2MIT