Skip to main content
Glama
enesjakozh
Ritesh2351235

Omi Memories MCP Server

by Ritesh2351235
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

오미 메모리 MCP 서버

이는 도구 인터페이스를 통해 특정 사용자에게 Omi 메모리에 대한 액세스를 제공하는 MCP(Model Context Protocol) 서버입니다.

특징

  • OMI 앱에서 지정된 사용자 ID에 대한 모든 메모리를 가져오는 도구

Related MCP server: MCP-Mem0

설정

  1. 종속성 설치:

지엑스피1

  1. 사용자 ID를 구성하세요:

    • src/server.ts 엽니다.

    • Omira 앱의 계정 섹션에서 사용자 ID로 SPECIFIC_USER_ID 상수를 업데이트합니다.

  2. TypeScript 코드를 작성합니다.

npm run build

  1. 서버를 시작합니다:

npm start

사용 가능한 도구

페치 메모리

구성된 사용자 ID에 대한 모든 메모리를 가져옵니다.

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);

구성

서버는 다음을 기대합니다.

  1. Express API는 http://localhost:3000 에서 실행됩니다.

  2. 사용자 ID를 구성해야 합니다. src/server.ts 의 SPECIFIC_USER_ID 상수를 Omira 앱의 계정 섹션에서 얻을 수 있는 사용자 ID로 업데이트합니다.

Claude 데스크톱 통합

Claude Desktop과 통합하려면 Claude Desktop 구성( claude_desktop_config.json )을 업데이트하여 다음을 포함하세요.

{
  "mcpServers": {
    "omi-mcp": {
      "command": "node",
      "args": [
        "/path/to/your/mcp-server/dist/server.js"
      ],
      "env": {
        "NODE_ENV": "development"
      }
    }
  }
}

커서 IDE 통합

Cursor IDE와 통합하려면:

  1. 커서 IDE 설정 열기

  2. "AI 및 Copilot" 설정으로 이동합니다.

  3. "모델 컨텍스트 프로토콜"에서 다음 설정을 사용하여 새 MCP 서버를 추가합니다.

{
  "name": "Omi Memories",
  "command": "node",
  "args": [
    "/path/to/your/mcp-server/dist/server.js"
  ],
  "cwd": "/path/to/your/mcp-server",
  "env": {
    "NODE_ENV": "development"
  }
}

/path/to/your/mcp-server 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
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

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

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches