Documentation

Hermes Agent

Hermes Agent can load Northsun (formerly Mnemix) as a remote HTTP MCP server from ~/.hermes/config.yaml. Reference MNEMIX_API_KEY in the authorization header, reload the MCP configuration, test the server, and verify one read-only tool. This is protocol interoperability with Hermes Agent, not a Nous Research partnership or a promise of native product support.

Prerequisites

A current Hermes Agent installation with MCP support.
A Northsun API key stored as MNEMIX_API_KEY in Hermes's environment or ~/.hermes/.env.
A controlled caller already present in the target Northsun tenant.

# ~/.hermes/.env
MNEMIX_API_KEY=...

Hermes resolves ${VAR} placeholders in remote MCP URLs and headers when it connects. Keep the real value out of config.yaml.

Configure Northsun

Add this block to ~/.hermes/config.yaml:

mcp_servers:
  mnemix:
    url: "https://mcp.mnemix.ai/mcp"
    headers:
      Authorization: "Bearer ${MNEMIX_API_KEY}"
    enabled: true
    tools:
      include:
        - caller_lookup
        - recall_and_enrich
        - calls_end
      resources: false
      prompts: false

The allowlist starts with the stable caller-memory tools. Remove the include block only after you have inspected the broader contact and governed-context schemas and intentionally want them available.

Reload a running Hermes session with:

/reload-mcp

Verify the connection

Test and list the server from a terminal:

hermes mcp test mnemix
hermes mcp list

Hermes prefixes server-native tools as mcp_<server>_<tool>. For this configuration, verify mcp_mnemix_caller_lookup, then call it with a controlled test number. A successful protocol test plus an authenticated read proves more than tool discovery alone.

Common failures

Symptom	Likely cause	Fix
`${MNEMIX_API_KEY}` resolves empty	Hermes did not load the expected environment or `.env` file	Restart Hermes from the correct environment and test again.
`401 unauthorized`	Missing or invalid bearer key	Check environment loading without printing the secret; rotate the key if exposure is possible.
Test succeeds but expected tools are absent	The `tools.include` list excludes them or the server schema changed	Run `hermes mcp configure mnemix` or update the allowlist after reviewing live discovery.
Tool names look unfamiliar	Hermes prefixes and sanitizes MCP tool names	Use `mcp_mnemix_<tool>` in Hermes while keeping original names in the include list.
Connection times out	Network path or initial handshake is failing	Check remote connectivity, then adjust `connect_timeout` only after confirming the endpoint and auth.

Remove the connection or rotate the key

Remove the server with:

hermes mcp remove mnemix

Delete the corresponding key from ~/.hermes/.env only if no other approved client uses it. If the value was exposed, revoke or rotate it in Northsun first, replace the environment value, and restart Hermes. Local removal alone does not invalidate the credential.

Stable and beta boundaries

The three frozen public REST endpoints remain defined in the API reference. The MCP server also exposes evolving contact and governed-context tools. Re-run discovery before widening the Hermes allowlist. The connection does not imply Beacon, proactive delivery, or cross-session behavior beyond the tools you explicitly observe and call.

This guide is based on Hermes Agent's public MCP configuration contract. It does not claim catalog inclusion, certification, partnership, endorsement, or support from Nous Research.