Omi MCP Server

A custom MCP (Model Context Protocol) server that connects Claude to the full Omi platform - 38 tools covering memories, conversations, action items, goals, transcript editing, speaker management, and more.

Why This Exists

Omi provides an official MCP server using SSE (Server-Sent Events) transport. Two problems:

1. Firewall issues on managed devices. SSE maintains persistent long-lived HTTP connections. On Windows, this triggers "Allow Node.js through Windows Firewall?" prompts. On a work-managed device, that's a non-starter.

2. No Internal API access. The official MCP only uses the Developer API key. It can't edit transcript text, assign speakers to segments, query conversations by status, reprocess conversations, or manage apps/templates - all of which require Firebase authentication.

This server solves both:

• stdio transport - standard outbound HTTPS requests only, no persistent connections, no firewall prompts
• Dual authentication - Developer API key for standard CRUD + Firebase tokens for Internal API access, on a single server

Prerequisites

• Node.js 24+ (uses built-in fetch() - zero npm dependencies)
• Omi account with the Omi mobile app installed
• Claude Code or Claude Desktop (any MCP-compatible client works)

Setup

1. Get Your Credentials

You need three values:

Developer API Key

1. Open the Omi mobile app
2. Go to Settings > Developer
3. Tap "Create Key"
4. Copy the key (shown once, starts with omi_dev_)

Keys are case-sensitive - it's omi_dev_ lowercase, not Omi_dev_.

Firebase Refresh Token

This gives access to Omi's Internal API (transcript editing, speaker assignment, conversation lifecycle). If you only need the Developer API tools, you can skip this.

1. Open omi.me in Chrome and log in
2. Open DevTools (F12)
3. Go to the Application tab
4. In the left sidebar, expand IndexedDB
5. Find firebaseLocalStorageDb
6. Click into the object store
7. Find the entry with your user data
8. Navigate to: value > stsTokenManager > refreshToken
9. Copy the refresh token string

The refresh token doesn't expire unless you change your password or explicitly revoke sessions. You only need to do this once.

Firebase API Key

This identifies Omi's Firebase project. It's not a secret (it's embedded in the web app), but you need the correct one to avoid PROJECT_NUMBER_MISMATCH errors.

Important: Omi has two Firebase projects. The key in the GitHub repo (AIzaSyC1U6S-...) is the dev project. Production users need the production key. Check the Omi web app's network requests or source to find the current production key.

2. Register the Server

Claude Code (CLI)

claude mcp add --scope user omi \
  node /path/to/omi-mcp-server.js \
  -e OMI_DEV_API_KEY=omi_dev_your_key \
  -e OMI_FIREBASE_API_KEY=your_firebase_api_key \
  -e OMI_FIREBASE_REFRESH_TOKEN=your_refresh_token

Replace /path/to/ with the actual path to omi-mcp-server.js.

Claude Desktop

Add to your config file (%APPDATA%\Claude\claude_desktop_config.json on Windows, ~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "omi": {
      "command": "node",
      "args": ["/path/to/omi-mcp-server.js"],
      "env": {
        "OMI_DEV_API_KEY": "omi_dev_your_key",
        "OMI_FIREBASE_API_KEY": "your_firebase_api_key",
        "OMI_FIREBASE_REFRESH_TOKEN": "your_refresh_token"
      }
    }
  }
}

3. Verify

After registration, your MCP client should list all 38 tools. Try a simple read operation:

Get my latest 5 Omi memories

Tool Reference

Developer API Tools (API Key Auth)

These tools use your OMI_DEV_API_KEY for authentication.

Memories (5 tools)

Conversations (6 tools)

Action Items (5 tools)

Goals (6 tools)

Internal API Tools (Firebase Auth)

These tools use Firebase ID tokens. They require OMI_FIREBASE_API_KEY and OMI_FIREBASE_REFRESH_TOKEN.

Conversation Lifecycle (3 tools)

Search & Merge (2 tools)

Transcript Editing (2 tools)

App/Template Management (5 tools)

People/Speaker Profiles (4 tools)

Troubleshooting

"Allow Node.js through Windows Firewall?" prompt

You're using the SSE-based official server, not this one. This stdio server makes standard outbound HTTPS requests only - no firewall prompts.

PROJECT_NUMBER_MISMATCH error

You're using the wrong Firebase API key. Omi has two Firebase projects (dev and production). Make sure your OMI_FIREBASE_API_KEY matches the Firebase project your account is on. If your account is on production omi.me, you need the production key - not the dev key from the GitHub repo.

API key not working / 401 errors

• Dev API keys are case-sensitive: omi_dev_ (lowercase), not Omi_dev_
• Check that the key is correctly set in your environment variables
• Verify the key hasn't been revoked in the Omi mobile app

assign_segments returns 404

The endpoint URL format matters. This server uses the Internal API path (/v1/conversations/{id}/segments/assign), not the Developer API path (/v1/dev/user/conversations/{id}/segments/assign). If you've modified the code, verify the path.

Firebase token refresh fails

Your refresh token may have been revoked (password change, session revocation). Re-extract it from omi.me browser IndexedDB following the setup steps above.

Conversations stuck in "processing" status

Use get_conversations_by_status to find them, then process_in_progress_conversation or reprocess_conversation to push them through. This commonly happens after Bluetooth disconnects or app crashes.

Environment Variables

License

MIT - see LICENSE.