Connect Hermes to Cockpilot

Hermes, by Nous Research, works on your team's tasks, projects, contacts and KPIs through Cockpilot's 40 MCP tools, with your rights and never more. A personal token, then one block in ~/.hermes/config.yaml.

Start free trial Sign in

What Hermes gets

40 MCP tools. 14 that read and 26 that write, from the day's briefing to the month's KPIs.
Your team's work. Its tasks, projects, contacts and KPIs.
Your rights, never more. Hermes sees and changes what you can, nothing else.

Where the token comes from

In Cockpilot, open Connections. Then the Hermes row: it creates your token, hermes-<you>.
ck_ followed by 43 characters. Copy it right away: it is shown only once.
It goes in COCKPILOT_TOKEN. In ~/.hermes/.env: Hermes resolves ${COCKPILOT_TOKEN} from the profile's .env when it connects.

~/.hermes/.env

COCKPILOT_TOKEN=ck_...

Hermes, step by step

1. Add the block under mcp_servers in ~/.hermes/config.yaml.
2. Put the COCKPILOT_TOKEN line in ~/.hermes/.env.
3. In Hermes, /reload-mcp loads it; hermes mcp test cockpilot shows what Cockpilot answers.

~/.hermes/config.yaml

mcp_servers:
  cockpilot:
    url: "https://your-team.cockpilot.si/mcp"
    headers:
      Authorization: "Bearer ${COCKPILOT_TOKEN}"
    trust: untrusted

Put in your space's address (your-team).

Good to know

trust: untrusted makes every write (a tool without readOnlyHint) ask for approval; Cockpilot marks its reads read-only. tools.include can limit the list. Keys from website/docs/reference/mcp-config-reference.md in the Hermes repository.

The file. ~/.hermes/config.yaml on macOS and Linux.
Checked. On October 28, 2026, against the documentation at hermes-agent.nousresearch.com.

Security

One token per client. Hermes has its own: revoke it from the Security page.
Deletions go to the trash. They can be restored for thirty days, and every change is in the journal.

Other clients

OpenClaw · Claude Code · Codex · Gemini CLI · All integrations · Version française

Start free trial Sign in