knowmindknowmind
DokumentationQuickstartAnbindungReferenzFehlerbehebung
DEEN
knowmindknowmind
DocumentationQuickstartIntegrationsReferenceTroubleshooting
DEEN

Integration

Claude Code

This guide registers knowmind as an MCP server in the Claude Code command line tool. From then on, every Claude Code chat has access to the ten knowmind tools — recall, store, link, unlink, stats and six more.

Audience
Developers working with Claude Code who need a persistent Memory Store across sessions. Suitable for solo development and for team setups with a shared workspace.

Prerequisites

  • Claude Code installed and ready (check: claude --version)
  • knowmind account on Business API or higher (for your own API token), or on Private / Pro / Business with the knowmind CLI installed
  • For the CLI option: Node.js 20 or newer

Steps

  1. 1

    Option A: via the installed knowmind CLI

    This option is the fastest — assuming you have the knowmind CLI installed and signed in. If not, run through the command line guide first.

    bash
    claude mcp add knowmind knowmind mcp

    Claude Code launches the knowmind CLI on demand in stdio MCP mode. The token stays in ~/.knowmind/config.json and is not stored in the Claude Code configuration.

    Outcome: claude mcp list shows an entry knowmind: knowmind mcp — Connected.

  2. 2

    Option B: HTTP transport with your own API token

    This option uses the official HTTP transport protocol with a bearer token. Requires the Business API plan or higher, which unlocks personal API tokens.

    In the dashboard under API Tokens create a token with scopes read and write. Copy the clear text once — afterwards only the prefix is visible.

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

    Smoke-test from chat

    Start a Claude Code session and ask a question that points at content in your Memory Store. Claude usually recognises the need for a recall on its own. If needed you can ask explicitly: "Look up … in knowmind".

    bash
    $ claude
> What open items are on the Müller contract?

    Outcome: Claude calls knowmind.recall (visible in the tool output) and answers based on the hits from your Memory Store.

  4. 4

    Save a memory from the chat

    In the same chat you can ask Claude to write something into knowmind. Claude picks knowmind.store_memory (for short notes) or knowmind.upload_document (for longer texts that need chunking).

    bash
    > Store as a new memory: "QM training confirmation Maria, 12 March"

    Outcome: Claude confirms the new memory and returns its memory ID. The entry appears immediately in the knowmind dashboard.

Verify the result

The integration is healthy when all four conditions hold:

  • claude mcp list shows knowmind as Connected.
  • In the chat, a domain question triggers a knowmind.recall call.
  • The knowmind dashboard "Recent activity" lists the actions you took.
  • Running knowmind stats in a second terminal shows the updated memory count.

Troubleshooting

Error messageCauseResolution
claude mcp list shows knowmind as Failedknowmind CLI not on PATH (Option A) or bad header value (Option B).Option A: run which knowmind / where knowmind — if empty, reinstall the CLI. Option B: check the token in the dashboard and re-register.
Tool calls time outFirst request in a cold-start situation or network latency.Retry the request. If it persists, run knowmind health to verify service reachability.
Memory type unknownClaude passed an invalid memory_type value.Valid values: semantic, episodic, procedural, reference. Be explicit with Claude on the next save.

Related