MCP with API key

For programmatic or server-side access where OAuth is not practical, use a Bearer API key.

Server URL

https://api.hypermemory.io/mcp

The same MCP endpoint is used for both OAuth and API key authentication. The middleware detects the hm_ prefix on the key and resolves your tenant from the api_keys system table.

1. Create a key

Go to app.hypermemory.io and click API Keys in the main navigation. Create a new key, select which graph it should access (if your plan supports multiple graphs), and choose a scope.

Keys use the format hm_ followed by 64 hexadecimal characters. Each key is bound to a specific graph at creation time.

Copy the key immediately — it is shown only once. Keys are stored server-side as a SHA-256 hash.

2. Configure your client

Claude Desktop

In Claude Desktop’s MCP settings, add HyperMemory with the server URL and your API key in the Authorization header.

Claude Code

claude mcp add hypermemory \
  --transport http \
  --header "Authorization: Bearer hm_YOUR_KEY_HERE" \
  https://api.hypermemory.io/mcp

Environment variable

Many clients read HYPERMEMORY_API_KEY from the environment:

export HYPERMEMORY_API_KEY=hm_YOUR_KEY_HERE

Raw HTTP

curl -X POST https://api.hypermemory.io/mcp \
  -H "Authorization: Bearer hm_YOUR_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "hm_get_overview",
      "arguments": {}
    }
  }'

Key scopes

Scope	Access	Default for
owner	Read + write	Personal keys
member	Read-only	Organization keys

Key management

• Revoke keys at API Keys in the main navigation
• Rotate by creating a new key and revoking the old one
• The same plan limits and rate limits apply as with OAuth

See API keys for details on format, scopes, and rotation.