Skip to main content

​
Common Issues

  • Verify your API key starts with omi_mcp_
  • Check that the Authorization header uses Bearer prefix: Bearer omi_mcp_...
  • Generate a new key in the Omi app: Settings → Developer → MCP
  • Ensure the key hasn’t been revoked
  • Send an initialize request first — tools are only available after initialization
  • Check that your client supports the Streamable HTTP transport (2025-03-26 spec)
  • Try the /v1/mcp/sse/info endpoint to verify the server is reachable: 
    curl https://api.omi.me/v1/mcp/sse/info
  • Semantic search requires conversations/memories to be indexed in the vector database
  • New data may take a few minutes to be indexed after creation
  • Try broader queries — very specific queries may not match if phrased differently than the original
  • Use get_memories or get_conversations with filters as a fallback
  • The MCP server has per-user rate limits to prevent abuse
  • Wait a moment and retry
  • Reduce the frequency of tool calls in automated workflows
  • Some memories and conversations are behind the paid plan
  • Upgrade your plan to access all content
  • Locked memories still appear in list/search results with truncated content

​
Debugging Tools

Use the MCP inspector to test tools interactively:
npx @modelcontextprotocol/inspector uvx mcp-server-omi
For local development:
cd path/to/servers/src/omi
npx @modelcontextprotocol/inspector uv run mcp-server-omi

​
Need Help?

Discord Community

Get help from the community and team

GitHub Issues

Report bugs or request features