mem0-mcp: Skill for Claude Code

Mem0 MCP Modernization Skill

Purpose

Maintain pinkpixel-dev/mem0-mcp as a reliable MCP interface for Mem0 while supporting its existing Cloud, Supabase, and local/in-memory modes. Prefer a stable, ergonomic MCP layer over exposing every Mem0 REST endpoint blindly.

This skill is specifically about Mem0 Platform API V3 migration and feature design. Treat older V1/V2 assumptions as potentially stale until verified against the current Mem0 docs and installed SDK types.

Non-negotiable rules

1. Do not silently send old V2 request shapes to V3 endpoints.
2. Do not pretend all Cloud capabilities exist in Supabase or local mode. Capability-report and fail clearly instead.
3. Do not expose destructive bulk actions without an explicit confirmation field.
4. Do not make callers manually poll async events by default. Provide a good default polling experience with an opt-out.
5. Do not remove existing convenient MCP inputs without a compatibility path or a major-version migration note.
6. Use the current official docs and installed mem0ai package types as final authority when implementation details disagree.

Current Mem0 Platform API facts

Authentication

All hosted REST calls use token authentication:

Authorization: Token <MEM0_API_KEY>
Accept: application/json
Content-Type: application/json

Keep API keys server-side only. Never expose them in browser code, logs, test fixtures, screenshots, or generated docs.

V3 add-memory behavior is asynchronous and ADD-only

Endpoint:

POST https://api.mem0.ai/v3/memories/add/

Minimal request:

{
  "messages": [
    { "role": "user", "content": "I moved to Manchester last month." }
  ],
  "user_id": "user-123"
}

Important behavior:

• Requires messages.
• Requires at least one entity scope: user_id, agent_id, app_id, or run_id.
• Supports metadata, custom_instructions, and infer.
• infer: false stores messages verbatim instead of invoking memory extraction.
• Returns an async event response, usually PENDING plus event_id.
• V3 extraction is single-pass ADD-only. It does not automatically update or delete old memories. Memories can accumulate and require deliberate maintenance.