meinKontextDocs
Navigation & search

Getting started

Connect your app

Client-specific setup with steps and commands.

Client setup

Choose your app and follow its setup steps. The guide explains the available sign-in options and any limitations.

Optional org API key profile. For personal access on a headless host, use the device-login guide.

  1. Mint an org API key with the create_api_key tool from a connected user session (Claude Code, Desktop) — the Hermes host never sees your personal login.
  2. In Fleet, open the instance's MCP integration and set three fields: a server name (letters, digits, _, - only), the endpoint https://meinkontext.de/mcp, and the api-key as the bearer token.
  3. Save. Fleet writes the server into ~/.hermes/config.yaml, puts the token into ~/.hermes/.env (never into the YAML) and restarts the gateway — the agent picks up the tools on the next session.
  • Org-scoped service principal — read-only for objects (the server hides authoring tools such as write_article; direct calls answer an explanatory error), and the same for memory: it reads (recall, search) but cannot write; remember and forget need an OAuth connection.
  • Fleet only manages an entry that carries url, enabled and headers and nothing else. Adding another key — or a command: for a local stdio server — makes that entry unmanaged by the reviewed Fleet adapter; maintain that custom configuration yourself.
  • The endpoint must be HTTPS unless it is a loopback address on the VPS itself — Fleet rejects plain HTTP to a remote host.
  • Field names come from Fleet's Hermes adapter, not from a screenshot of its UI — the on-screen labels may read differently.
  • After a tool-surface change on the server, restart the gateway: instructions and the tool list are read at connect, so a running session keeps the old ones.
Without Fleet: the two files by hand
  • Same shape Fleet writes, so an entry created this way stays Fleet-manageable as long as it keeps exactly these keys. Restart the gateway afterwards.
yaml
# ~/.hermes/config.yaml
mcp_servers:
  meinkontext:
    url: https://meinkontext.de/mcp
    enabled: true
    headers:
      Authorization: "Bearer ${MEINKONTEXT_TOKEN}"

# ~/.hermes/.env  — chmod 600; the token NEVER belongs in the YAML
# MEINKONTEXT_TOKEN=<org API key>
  • ${MEINKONTEXT_TOKEN} stays literal in the YAML; Hermes resolves it from its environment. The .env file still contains the key: protect it and any backups that include it.