Cursor

Open Knowledge plugs into Cursor through MCP plus an installed skill that teaches the agent how to use the tools.

Install

There are two ways to connect Cursor, depending on how you run Open Knowledge:

• macOS desktop app. The first time you open a project, a consent dialog detects Cursor and configures it for you. To re-trigger the dialog, delete ~/.ok/mcp-status.json and relaunch.
• Web app / terminal (Linux, Intel Mac — see the web app guide). Run ok init in your project: it registers the Open Knowledge MCP server with Cursor and the other editors it detects. Every ok start refreshes the entry.

Approve the server

Cursor prompts you to approve a new MCP server when you next open the project. Approve open-knowledge. Until you do, the agent can't see the tools.

Open with AI

From the editor, Open with AI ▸ Cursor dispatches the current file, folder, or project to Cursor. Three entry points: the editor header's sparkle icon, the sidebar's right-click menu (file / folder / empty space), and the macOS File → Open with AI menu.

Cursor uses a two-step handoff: Open Knowledge spawns cursor <projectDir> to open the workspace first, then fires the cursor:// URL with a short prompt asking Cursor to open the target in Open Knowledge's web preview. The agent then grounds the rest of the conversation through MCP. See Editor → Open with AI for the full UX.

In the web app, Cursor's spawn step runs through a local POST /api/spawn-cursor fallback, so the Open with AI ▸ Cursor row works there too — not just in the desktop app.

Verify

Ask the agent:

“List the first 5 documents you come across in this project.”Copy

The agent should call the Open Knowledge exec tool and respond with some of your documents.

If it still doesn't see the tool after approval, restart Cursor so it picks up the new MCP entry.