knowmindknowmind
DokumentationQuickstartAnbindungReferenzFehlerbehebung
DEEN
knowmindknowmind
DocumentationQuickstartIntegrationsReferenceTroubleshooting
DEEN

Integration

Cursor

This guide registers knowmind as an MCP server in the Cursor IDE. Cursor uses the same MCP format as Claude Desktop — configuration takes a couple of minutes.

Audience
Developers using Cursor as their IDE who need a persistent Memory Store across projects and sessions.

Prerequisites

  • Cursor installed (cursor.com)
  • knowmind account on any plan
  • For the CLI option: knowmind CLI installed and signed in
  • For the HTTP option: an API token from the knowmind dashboard

Steps

  1. 1

    Open Cursor's configuration

    In Cursor under Settings → MCP or directly editing the configuration file:

    text
    macOS / Linux:  ~/.cursor/mcp.json
Windows:        %USERPROFILE%\.cursor\mcp.json

    Outcome: The configuration file is open, or the MCP area in settings is visible.

  2. 2

    Option A: register the knowmind CLI (recommended)

    Prerequisite: the CLI is installed and signed in with knowmind login:

    json
    {
  "mcpServers": {
    "knowmind": {
      "command": "knowmind",
      "args": ["mcp"]
    }
  }
}

    Outcome: Cursor launches the CLI on demand in stdio MCP mode. The token stays in the CLI configuration file.

  3. 3

    Option B: HTTP transport with a bearer token

    json
    {
  "mcpServers": {
    "knowmind": {
      "type": "http",
      "url": "https://knowmind.de/api/mcp/v1",
      "headers": {
        "Authorization": "Bearer kmt_…"
      }
    }
  }
}
  4. 4

    Restart Cursor

    Cursor reads the MCP configuration only at startup. After the restart, the knowmind tools appear in the MCP overview.

    Outcome: Under Settings → MCP, knowmind is shown as Connected. In every new chat in Cursor the ten tools are available.

  5. 5

    Smoke test

    In a Cursor chat ask a question that targets content in your Memory Store. Cursor usually recognises the tool need automatically and calls knowmind.recall.

    Outcome: Cursor's response contains content from your knowmind corpus, visible in the tool-call area.

Verify the result

The integration is healthy when all three conditions hold:

  • Under Settings → MCP, knowmind is Connected.
  • The knowmind tools are visible in new chats.
  • A test question returns answers from the knowmind corpus, traceable in the tool-call area.

Troubleshooting

Error messageCauseResolution
MCP area not visible in CursorOutdated Cursor version without MCP support.Update Cursor to the current version (at least 0.42).
knowmind shows as FailedJSON syntax error or knowmind CLI not on PATH.Open the file in an editor with JSON linting. Verify the CLI path with which knowmind or where knowmind.
Tools not offered in every chatTool permissions are configurable per chat.Click the tool icon at the top right of the Cursor chat and enable knowmind.

Related