Skip to content
DocumentationQuickstartIntegrationsReferenceTroubleshooting
DEEN

Integration

Cursor

One command in the terminal, restart Cursor — from then on the editor finds your project knowledge while it answers. The command writes the entry itself; you open no file.

Audience
Anyone working with Cursor. The free knowmind Private plan is enough.

Prerequisites

  • Cursor installed
  • Node.js 20 or newer (check: node --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

    Create an access key

    Create a key in the Cockpit under keys. It starts with kmt_ and is shown only once, so copy it right away. If you picked Cursor on the welcome screen, it is already part of the command there.

    Outcome: A key of the form kmt_… is on your clipboard.

  3. 3

    Write the entry

    Open a terminal, in Cursor if you like, paste the command, replace kmt_YOUR_KEY and press enter:

    bash
    npx -y knowmind install cursor --token kmt_YOUR_KEY

    The command extends ~/.cursor/mcp.json (Windows: %USERPROFILE%\.cursor\mcp.json) and leaves existing entries alone. --print only shows the entry; --project writes it into the project folder instead of your home directory.

    Outcome: The output ends by telling you to restart Cursor.

  4. 4

    Restart Cursor and enable the server

    Quit Cursor completely and open it again — the settings are read at startup. knowmind then sits with the MCP servers in the Cursor settings; switch it on there if new servers need confirming in your setup.

    Outcome: Cursor lists knowmind as a connected server with its tools.

  5. 5

    First recall

    In the Cursor chat, 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: “Save to knowmind: migrations only run through the script, never by hand.”

    Outcome: Cursor calls knowmind_recall_memories, the call is visible in the tools area, and the next question hits straight away.

Verify the result

The integration works when all three hold:

  • Cursor lists knowmind among the MCP servers as connected.
  • The knowmind tools can be selected in the chat.
  • The recall shows up in the Cockpit timeline, and keys shows a last-used time.

Troubleshooting

Error messageCauseResolution
npx: command not foundNode.js is missing on this machine.Install it from nodejs.org, open a new terminal and run the command again.
knowmind does not show up after the commandCursor kept running during setup.Quit Cursor completely and open it again.
Calls return 401The key was copied incompletely or has been revoked.Create a new one under keys and run the command again — it replaces the old entry.
Tools are not visible in every chatTool access is selectable per chat.Open the tools icon in the chat and switch knowmind on.
Manual setup, and what the entry looks like on Windows

If you maintain ~/.cursor/mcp.json yourself:

json
{
  "mcpServers": {
    "knowmind": {
      "command": "npx",
      "args": ["-y", "knowmind", "mcp"],
      "env": {
        "KNOWMIND_TOKEN": "kmt_YOUR_KEY",
        "KNOWMIND_API_URL": "https://knowmind.de"
      }
    }
  }
}

On Windows the command writes a small detour through pythonw.exe into the entry, for a visible reason: npx opens a console window on every start, pythonw.exe does not. Without Python the entry says npx and works just the same — a window simply flashes up at startup.

It also works without a terminal: in the Cursor settings, add a new MCP server and enter the address https://knowmind.de/api/mcp/v1 with the header Authorization: Bearer kmt_….

What we tested
Tested on 19 October 2026: the command runs and writes ~/.cursor/mcp.json with the key in the environment; account, workspace and recall over the same route work as well. We did not verify the Cursor interface itself, and the naming of its settings can differ between versions.

Related