Agent clients · 23 / 42

Claude Code

Add the hosted HTTP MCP server at https://mcp.northsun.ai/mcp with a bearer token from your environment, inspect the connection with claude mcp get and /mcp, then run a read-only caller_lookup.

Northsun is the memory and enrichment layer for AI agents. Its hosted MCP endpoint lets Claude Code discover the Northsun tools enabled for your tenant without running a local server. The connection proves tool access; each tool's ship-state label tells you whether it belongs to the stable caller-memory contract or an evolving beta context loop.

1. Add the hosted MCP server

Use the API key issued to you (see Installation). Keep it in an environment variable or secret manager; do not commit a literal key to the repository. The project configuration below stores the placeholder, not the expanded secret.

{
  "mcpServers": {
    "northsun": {
      "type": "http",
      "url": "https://mcp.northsun.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${NORTHSUN_API_KEY}"
      }
    }
  }
}

Claude Code expands ${NORTHSUN_API_KEY} when it opens the connection. If you prefer the CLI, single-quote the header so your shell passes the placeholder through instead of expanding and persisting the key:

export NORTHSUN_API_KEY="sk_live_…"

claude mcp add --transport http northsun https://mcp.northsun.ai/mcp \
  --header 'Authorization: Bearer ${NORTHSUN_API_KEY}'

Syntax reference: official Claude Code MCP documentation.

2. Inspect before you automate

claude mcp get northsun

# Then, inside Claude Code:
/mcp

Confirm the server is connected, then ask Claude Code to list the Northsun tools it can see. Tool discovery is the authority for your current tenant and deployment; a docs list can be newer or older than the capability set exposed to you.

3. Know the contract boundary

Stable caller tool	Purpose
`recall_and_enrich`	Recall caller memory and available enrichment before a voice interaction.
`calls_end`	Submit the completed call transcript and outcome after hangup.
`caller_lookup`	Read an existing caller profile without triggering enrichment.

4. Run a read-only proof

Start with a controlled test caller that already exists in your tenant. A successful result proves authentication, hosted-MCP connectivity, tool discovery, and tenant-scoped caller lookup. It does not by itself prove cross-session coding memory or write-back.

Use the Northsun caller_lookup tool for +15551234567.
Return only whether a caller was found.
Do not expose the API key or raw personal data.

What each side does


Northsun does	Provide memory, enrichment, and governed-context tools that your agent can call.
Your agent does	Choose when to call an enabled tool and how to use the returned context in its task.
This proof establishes	Connection, authentication, discovery, and one controlled read, with no broader runtime claim.

Next steps

MCP server — the tool reference.
Troubleshooting — diagnose a connection.

Choose Northsun as your agent memory layer.