Documentation

MCP server

The hosted Northsun (formerly Mnemix) MCP server gives authenticated MCP-compatible agents memory, caller, enrichment, and retrieval tools over Streamable HTTP. Connect to https://mcp.mnemix.ai/mcp with the same tenant-scoped API key used by REST.

Host migration: the canonical platform host is moving to mcp.northsun.ai. During the transition mcp.mnemix.ai continues to serve the full surface unchanged — existing integrations keep working, no action required. When the successor host is generally available, responses from this host will carry a Deprecation header (RFC 9745) and a Link rel="successor-version" header pointing at the corresponding mcp.northsun.ai URL; a retirement date, if one is ever set, will be announced in advance with a Sunset header (RFC 8594). No cutoff is scheduled.

Configure a hosted connection

The exact configuration filename varies by client, but the connection requires three values:

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

Keep the real key in your client's secret/environment facility. Some clients do not expand ${VARIABLE} placeholders inside JSON; verify how your client resolves secrets rather than committing a literal key.

Anonymous discovery is available at https://mcp.mnemix.ai/.well-known/mcp. Tool calls themselves require authentication.

Tool families

The authenticated remote server currently registers the following product tools. MCP evolves independently from the frozen three-endpoint REST surface, so inspect tools/list during integration and pin client expectations.

Frozen caller-memory tools

ToolPurpose
recall_and_enrichRecall a caller and return profile, recent-call memory, and enrichment before a voice interaction.
calls_endPost the completed call transcript and outcome after hangup.
caller_lookupRead a caller profile without creating a caller or triggering enrichment.

Contact workflow tools

ToolPurpose
lookup_contactLook up a contact by phone or email for chat/support workflows.
save_interactionRecord a call, chat, or email interaction.
search_contactsSearch contacts.
get_contact_historyRead prior interactions for a contact.
enrich_contactRequest re-enrichment for an existing contact.
update_contactUpdate supported contact fields.

These tools use authenticated product routes that are not part of the frozen public REST trio. Treat their MCP schemas as the integration contract and re-check tools/list when upgrading.

Governed-context loop

ToolPurpose
observeRecord a voice, chat, or workflow observation for asynchronous memory extraction.
contextRequest a ranked context packet for an entity and query.
feedbackReport which retrieved memories were useful or contradicted.
mnemix.get_memoryRetrieve a full tenant-scoped memory export when a prior notification or workflow supplies an entity ID.

These authenticated MCP tools are the current route for broader voice/chat/workflow context. They do not add public REST endpoints, and their presence does not mean Beacon or proactive delivery is publicly shipped.

Verify the connection

  1. Restart or reload your MCP client.
  2. Inspect the client's tool list and confirm at least caller_lookup, recall_and_enrich, and calls_end appear.
  3. Run caller_lookup with a test number already in your tenant.
  4. Treat 404 as a valid empty-state result; treat 401 as a key/configuration failure.

Hosted versus local

The source repository contains a separate stdio package named @mnemix-ai/mcp-server, but it is not currently published on npm. Public users should use the hosted MCP endpoint. Repository contributors can build the local package from source for development, but should not document an npm install until the package is actually published.

Security boundary

The bearer key establishes the tenant before tools are registered or invoked. Operator-only internal tools are not part of the public product tool list. Never expose your MCP configuration with an embedded key.

Next steps