Skip to main content
Glama
enesjakozh
Ritesh2351235

Omi Memories MCP Server

by Ritesh2351235
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Omi Memories MCP サーバー

これは、ツール インターフェイスを通じて特定のユーザーに Omi メモリへのアクセスを提供するモデル コンテキスト プロトコル (MCP) サーバーです。

特徴

  • OMIアプリから指定されたユーザーIDのすべての思い出を取得するツール

Related MCP server: MCP-Mem0

設定

  1. 依存関係をインストールします:

npm install

  1. ユーザー ID を設定します。

    • src/server.tsを開く

    • Omiraアプリのアカウントセクションから、 SPECIFIC_USER_ID定数をユーザー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 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