Omi Personal Recollection Access Point (MCP Server)

This implementation serves as a Model Context Protocol (MCP) nexus, granting controlled, programmatic entry to an individual user's aggregated Omi recollections through a standardized tool interface.

Core Capabilities

• Provision of a specific instrument for retrieving the entirety of stored personal narratives associated with a provisioned consumer identifier from the OMI application backend.

Deployment Procedure

1. Dependency establishment: bash npm install

2. Identifier configuration mandate:

3. Modify the script located at src/server.ts.

4. Assign the desired consumer identifier, obtainable from the 'Account' segment of the Omira Application, to the mutable constant SPECIFIC_USER_ID.

5. TypeScript compilation stage: bash npm run build

6. Server initiation sequence: bash npm start

Accessible Interface Functions

fetch-memories

This function retrieves the complete set of recollection entries linked to the statically configured consumer identifier.

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

// Invoking the retrieval mechanism const result = await client.callTool({ name: "fetch-memories", arguments: {} }); console.log(result.content[0].text);

Operational Prerequisites

The operational instance necessitates two primary conditions to be met: 1. The underlying RESTful API infrastructure must be active and accessible at the endpoint http://localhost:3000. 2. The unique consumer identifier must be established: Edit the SPECIFIC_USER_ID variable within the src/server.ts file, sourcing the ID from the user account area of the Omira Application.

Integration with Claude Desktop Environment

To establish connectivity with the Claude Desktop utility, modify your configuration file (claude_desktop_config.json) to incorporate the following declaration:

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

Integration with Cursor IDE

For seamless operation within the Cursor Integrated Development Environment:

1. Access the Cursor IDE preference panel.
2. Navigate to the 'AI & Copilot' parameter group.
3. Within the 'Model Context Protocol' sub-section, introduce a new MCP service configuration utilizing these parameters:

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

Ensure that /path/to/your/mcp-server accurately reflects the complete directory structure of your installed MCP access point.