Skip to main content
Glama
Ritesh2351235

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

  1. Instalar dependencias:

npm install
  1. Configura tu ID de usuario:

    • Abrir src/server.ts

    • Actualice la constante SPECIFIC_USER_ID con su ID de usuario desde la sección Cuenta de la aplicación Omira

  2. Construya el código TypeScript:

npm run build
  1. Iniciar el servidor:

npm start

Herramientas 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:

  1. La API Express se ejecutará en http://localhost:3000

  2. El ID de usuario debe configurarse: actualice la constante SPECIFIC_USER_ID en src/server.ts con 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:

  1. Abrir la configuración de Cursor IDE

  2. Vaya a la configuración de "IA y copiloto".

  3. 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 tool
fetch-memoriesD
ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

D1/5.0
Behavior1/5

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.

Conciseness1/5

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.

Completeness1/5

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.

Parameters1/5

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.

Purpose1/5

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.

Usage Guidelines1/5

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. 1 tool updatev1.0.0
    • Changedfetch-memories1 field changed
      • removedInput schema / additionalProperties
        Removed value: -false
  2. 1 tool update
    • First observedfetch-memories

TDQS

D1.8/5.0

Scored across 1 tool

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness2/5

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

ActivityInactive
ResponsivenessNo issues

Related MCP Connectors

Related MCP Servers