DOCUMENTATION / MCP PROTOCOL SPECIFICATION V1

Model Context Protocol (MCP)

MemoraMobi is a hosted AI memory layer that provides a unified, persistent memory store for all your AI assistants. By exposing a standard Model Context Protocol (MCP) interface, MemoraMobi allows tools like Claude, ChatGPT, Cursor, VS Code, Gemini, and custom agents to remember facts about your preferences, projects, and history—stored securely on MemoraMobi's own servers with local vector embedding.

1. The MCP Endpoint

Connect any MCP-compatible client to our Streamable HTTP transport endpoint.

POST https://memoramobi.com/mcp

Canonical endpoint: https://memoramobi.com/mcp (also served on https://app.memoramobi.com/mcp).

2. Authentication

MemoraMobi supports three flexible authentication methods depending on your client software capabilities:

Bearer Token Header

Authorization: Bearer mm_live_...

Standard HTTP header for clients supporting custom headers (e.g. Claude Code, Cursor, Windsurf).

Path-Key URL (Header-less)

POST https://memoramobi.com/mcp/k/mm_live_...

For clients that only accept a single URL string without header configuration support.

OAuth 2.1 + DCR

PKCE / Dynamic Client Registration

For browser-based custom connectors (e.g. Claude.ai, ChatGPT) with standard "Sign in with MemoraMobi" flow.

3. Quickstart Request (Curl Example)

Test your connection using a standard MCP initialize JSON-RPC 2.0 payload:

curl -X POST https://memoramobi.com/mcp \
  -H "Authorization: Bearer mm_live_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2024-11-05",
      "capabilities": {},
      "clientInfo": {
        "name": "curl-test",
        "version": "1.0.0"
      }
    }
  }'

4. Available MCP Tools

MemoraMobi registers 6 core MCP tools during initialization. Tool descriptions below are pulled verbatim from the live server definitions:

Tool Name	Verbatim Description
remember	Store a durable fact about the user. Check `similar` in the response: if an existing memory covers the same fact, call `supersede` on it instead of storing a near-duplicate. Returns {status:"created"\|"duplicate", id, similar:[{id,content,score}]}. Use tier "profile" for stable facts about who the user is, "log" for dated events, "note" (default) for everything else.
recall	Call this at the start of any conversation and whenever the user references their preferences, history, projects, or people. Returns the user's stored memories ranked by relevance. Hybrid semantic + keyword search; results are {id, content, tier, tags, category, score, created_at}.
forget	Soft-delete one memory. Pass `id` (from recall/list) to delete it, or `query` to find it: with a query, the memory is deleted only when one confident match exists; otherwise {candidates:[...]} is returned and you must call again with the chosen id. Never deletes on a guess.
list	Browse memories newest first with keyset pagination (no search). Returns {items, next_cursor}; pass next_cursor back to get the next page.
supersede	Replace an existing memory with an updated fact, keeping history. Use this instead of remember when a fact changed (new address, new preference, corrected detail). Returns {id: new, supersedes: old}.
stats	Counts of stored memories by tier, pending embeddings, and the embedding model in use. Returns {total, by_tier, pending_embeddings, embedding_model}.

Ready to set up your AI assistants?

Use our interactive setup assistant for one-click installs and step-by-step guides for 34+ AI tools.

Go to Connect Setup →