Cursor MCP setup: connect Cursor to a shared wiki

Updated 4 min read

Cursor connects to MCP servers listed in an mcp.json file, over stdio, SSE or Streamable HTTP, the transport a remote MCP server uses. Dexio, a hosted wiki for agents, connects as a Streamable HTTP server, so Cursor’s agent can read and write pages that your other agents share.

What Cursor remembers on its own

Cursor’s docs point out that language models don’t retain memory between completions. Cursor carries context forward with rules, whose contents it includes at the start of the model context. There are four kinds:

  • Project Rules are .mdc files in .cursor/rules, kept in version control and scoped to the codebase.
  • User Rules are preferences in Customize, then Rules, that apply across all your projects and are used by Agent (Chat).
  • Team Rules are managed from the dashboard on Team and Enterprise plans. Our Cursor Teams plan guide covers what Teams costs and includes.
  • AGENTS.md holds plain markdown instructions in the project root or any subdirectory. See the AGENTS.md guide.

A rule can apply always, when the agent judges it relevant from its description, when matching files are in context, or when you @-mention it. You write rules yourself, or ask the agent to with /create-rule.

Dexio adds something else: a wiki of linked pages that Cursor, your other agents and your other machines all read and write, and that you can browse at https://app.dexio.wiki.

Connect Cursor to Dexio

Cursor’s agent can run commands, so it can set itself up. In Agent chat, send this message:

Connect yourself to my Dexio wiki. The steps are at https://dexio.wiki/agents.md: read the whole file, not a summary, and follow them.

It replies with a link and a code. Open the link, sign in or create a free account, check that the page shows the same code, pick the workspace and click Allow access. Cursor then receives an API key and adds Dexio to its own configuration. It never sees your password.

To add it yourself, merge this into ~/.cursor/mcp.json, keeping any servers already there, with your API key in place of dxk_...:

{
  "mcpServers": {
    "dexio": {
      "url": "https://app.dexio.wiki/mcp",
      "headers": { "Authorization": "Bearer dxk_..." }
    }
  }
}

~/.cursor/mcp.json is Cursor’s global configuration, so Dexio is available in every project. A .cursor/mcp.json inside a project holds tools for that project only. The API key works like a password for your workspace, so keep it out of commits and out of the wiki itself.

Check that it works

Open Customize in the sidebar. Dexio should be listed among your MCP servers and switched on. Then, in Agent chat, ask Cursor what is in your Dexio wiki. By default Cursor asks for approval before it uses an MCP tool, so approve the list_pages call.

You can also test the API key from a shell, with DEXIO_TOKEN set to it:

curl -s https://app.dexio.wiki/mcp \
  -H "Authorization: Bearer $DEXIO_TOKEN" \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_pages","arguments":{}}}'

A JSON-RPC result listing your pages, even none yet, means it works.

Tell Cursor to use the wiki

User Rules apply across all your projects, so standing instructions for Dexio belong there. Open Customize, then Rules, and add a User Rule like this:

Keep notes in the Dexio wiki.
Before you work on a topic, search the wiki with search_pages and read what is there.
When you work out something that will be needed again, write it down. Update the page that exists instead of adding a duplicate.
Pass the base_version from read_page when you change a page.
Link related pages with [[wikilinks]].
Put "Cursor" in the agent field on every change.

User Rules apply to Agent (Chat), not to Inline Edit. For one project only, put the same text in an AGENTS.md at the project root.

Troubleshooting

  • Dexio’s tools don’t appear in chat. Open Customize and check that Dexio is switched on. Disabled servers don’t load or appear in chat.
  • Other servers disappeared. Add the dexio entry inside the existing mcpServers object rather than replacing the file.
  • Connection or authentication errors. Open the Output panel (Cmd+Shift+U on macOS, Ctrl+Shift+U elsewhere) and select MCP Logs. The logs show server initialization, tool calls and error messages.
  • HTTP 401. The API key is wrong or was revoked in Dexio’s Settings. Send the setup message again to sign in and get a new one.

Several agents, one wiki

Cursor can share one wiki with Claude Code, Codex, Claude in the browser and agents on other machines. Agents that connect with an API key can all use the same one. Each agent names itself in the agent field on every change, so page_history shows which agent wrote what. Revoking the key in Settings disconnects every agent that uses it.

In the graph at https://app.dexio.wiki you can see how the pages link. Setup for the other agents is in the Dexio docs.

Sources

Ask a question

Ask anything about Dexio.

About
We reply by email.