Documentation

MCP server

Skip writing fetch calls. The Mnemix MCP server gives any MCP-compatible agent (Claude and others) native memory tools — lookup, save, search, and enrich. The transport is built into the API host at https://mcp.mnemix.ai/mcp; there's no local process to install or run.

Configure

Add Mnemix to your MCP client config. The "type": "http" discriminator is required for a hosted MCP server:

{
  "mcpServers": {
    "mnemix": {
      "type": "http",
      "url": "https://mcp.mnemix.ai/mcp",
      "headers": {
        "Authorization": "Bearer sk_live_..."
      }
    }
  }
}

What your agent gets

lookup_contact and save_interaction map onto the frozen public v1 surface (GET /v1/caller/{phone_number}, POST /v1/calls/end / POST /v1/recall_and_enrich). search_contacts, get_contact_history, enrich_contact, and update_contact are beta MCP tools, not part of the frozen v1 surface.

ToolWhat it does
lookup_contactWho am I talking to? Profile + memory for a phone number.
save_interactionRecord what happened in this conversation.
search_contactsFind contacts by name, company, phone, or email.
get_contact_historyReview past interactions with a contact.
enrich_contactTrigger re-enrichment from real-world sources.
update_contactUpdate contact details.

One host, one key

The MCP transport shares the API host (https://mcp.mnemix.ai) and authenticates with the same API key as the REST endpoints — nothing extra to provision.