Skip to content
DocumentationQuickstartIntegrationsReferenceTroubleshooting
DEEN

Integration

Claude Code

One command in the terminal, one authorisation through /mcp — from then on every Claude Code session reaches your memory, long after the previous context is gone.

Audience
Developers working with Claude Code who want knowledge to survive across sessions. The free knowmind Private plan is enough.

Prerequisites

  • Claude Code installed and current (check: claude --version)
  • An email address for the knowmind account

Steps

  1. 1

    Create your knowmind account

    Enter your email address at knowmind.de. You receive a sign-in link by mail and use it to sign in. There is no password.

    Then create your workspace: name, short name and plan. The Private plan costs 0 € and is enough for this guide; the pricing page lists the others.

    Outcome: The welcome screen is open, offering “start by writing” and “connect my AI tool”. Three starter cards are already in your workspace.

  2. 2

    Add the server

    Run this in the terminal:

    bash
    claude mcp add --transport http knowmind https://knowmind.de/api/mcp/v1

    The command writes the entry itself and needs no access key.

    Outcome: claude mcp list lists knowmind and reports Needs authentication — the correct state before you authorise it.

  3. 3

    Authorise access

    Start Claude Code, run /mcp, pick knowmind and confirm the sign-in. Claude Code opens the browser; you sign in with your sign-in link and confirm the permissions. In the terminal, claude mcp login knowmind does the same.

    Outcome: After the confirmation /mcp lists knowmind with its tools, and the Needs authentication note is gone.

  4. 4

    First recall, first save

    Start a session and ask for something that should be in your memory. In a fresh workspace the three starter cards come back, marked as a starting point rather than a solid hit. So save something first:

    bash
    $ claude
> Save to knowmind: the test environment credentials live in the vault, not in the repo.
> What does knowmind know about the test environment?

    For short notes Claude picks knowmind_store_memory, for longer texts knowmind_upload_document, and knowmind_recall_memories to look things up.

    Outcome: Claude confirms the entry and finds it in the next recall straight away.

Make Claude look things up by itself

Connected does not yet mean the AI uses the memory on its own. This command puts two rules in the project folder: look up before answering, write new things back.

bash
npx -y knowmind init

A second run replaces the rules instead of repeating them. With --dry-run you see every step first. The one-line status display knowmind status --line fits the status bar; details are on the command line page.

Note

No browser: sign in through a header

On a server or in a pipeline there is no browser authorisation. There you pass an access key from the Cockpit (keys) as a header; claude mcp list then reports Connected immediately, without /mcp.

bash
claude mcp add --transport http knowmind https://knowmind.de/api/mcp/v1 \
  --header "Authorization: Bearer kmt_YOUR_KEY"

The key then sits in the Claude Code configuration. Keep that file out of version control and out of cloud backups; if in doubt, revoke the key in the Cockpit.

Verify the result

The integration works when all three hold:

  • claude mcp list reports knowmind as Connected.
  • /mcp lists the knowmind tools.
  • A real question leads to a knowmind_recall_memories call that shows up in the Cockpit timeline.

Troubleshooting

Error messageCauseResolution
Needs authentication does not go awayThe authorisation through /mcp has not happened yet.Run /mcp in Claude Code, pick knowmind and confirm the sign-in in the browser. On a machine without a browser, use the header route.
Failed to connectThe address is incomplete.Check the address exactly: https://knowmind.de/api/mcp/v1. Remove the entry with claude mcp remove knowmind and add it again; claude mcp get knowmind shows what is stored.
Calls run into a timeoutFirst request after a longer pause, or a disturbance on the way.Ask again. If it persists, npx -y knowmind health shows whether the service is reachable.
Claude does not use the memory on its ownThere is no rule for it in the project.Run npx -y knowmind init in the project folder, or ask explicitly: “Search knowmind for …”.
What we tested
Tested on 19 October 2026: the command adds knowmind, without authorisation claude mcp list reports Needs authentication, and with a key in the header it reports Connected immediately. Account, workspace and first recall work as well. We did not verify the authorisation through /mcpitself; on the server side that route was walked in full.

Related