Cursor

Give Cursor Agent access to product briefs, architecture decisions and debugging notes alongside your code. Your editor reads the same knowledge saved by your other agents, with no separate copy of the vault to maintain.

Let Cursor Agent prepare setup

Paste this into Cursor Agent with its configuration-editing tools enabled. It can prepare the connection; you complete browser sign-in and any host approval.

Paste into your agent

Configure manually

Open Cursor's Customize → MCP controls, or merge the following entry into your user MCP configuration at ~/.cursor/mcp.json. For a connection limited to one project, use .cursor/mcp.json in that project.

json
{
  "mcpServers": {
    "mindwiki": {
      "url": "https://api.mindwiki.io/mcp"
    }
  }
}

Refresh the server list and use the server's sign-in control to complete OAuth. Enable MindWiki for the Agent session. If you are using Cursor cloud agents, configure the MCP connection through that environment's settings as well.

Complete the MindWiki connection

On MindWiki's authorization page, review the account and requested permissions. New users choose a MindWiki email name, save the generated access key and continue. Existing users select Use an existing MindWiki account and sign in to the account that owns their vault. Access Keys explains both paths.

Return to your agent after approving. Your sign-in key belongs on MindWiki's pages, not in chat or an MCP configuration file. The client handles its own OAuth credentials.

Check that it works

Ask your agent:

text
Use MindWiki to read my account status, then search for a note about one of my projects. Read a matching page and cite its title and path. Tell me if the vault is empty rather than making up a result.

Inspect the tool result and compare it with a page in MindWiki Cloud. For a new vault, the agent can read the operating guide and initialize the starter pages when account status permits it.

To check saving after granting write or capture access, ask “Save a new MindWiki capture titled Connection check with today's date, then read it back and give me its path.” The same file is available in your MindWiki apps.

Useful editor workflows

  • “Read the feature specification in MindWiki and compare it with this implementation before editing.”
  • “Search for our earlier migration decisions and use them to explain the tradeoffs in this change.”
  • “Save the bug's root cause and fix as a note the next agent can find.”

Use a project handoff page to move work between Cursor and Codex or Claude Code. Ask each agent to read the latest page before updating it.

Troubleshooting

If the server appears but its tools do not, check that it is enabled in Agent and finish authentication. A change to local configuration may require refreshing the MCP server or a new session. A project configuration applies only to that project; user configuration is the right place for a personal vault used across projects.

Permissions and disconnecting

The tools available depend on the scopes you approved and your vault's agent permissions. A read-only connection can search and read; writing requires the appropriate access. MindWiki currently includes the same features on Free, Pro and Power. The agent provider's plan and workspace rules are separate.

To disconnect just this client, revoke its grant in MindWiki Connections. Other agents keep their own connections. Never send access keys or OAuth tokens to support.

More help

MCP tools · Agent permissions · All AI agents

Setup reference: Cursor MCP documentation, checked October 20, 2026.