Skip to content
DocblockOpen workspace

Cursor integration

Put project knowledge beside your editor.

Keep reference material and decisions in a readable knowledge base, then make them available to Cursor through MCP. The editor and the notes can each keep the context they are best suited to hold.

Start with a note Read the guide
01

Ask for the relevant context

Cursor can use the connected tools to search and read accessible notes. Use a project brief as the starting point for a focused request.

02

Choose project or user configuration

The guide covers Cursor’s MCP settings and its project or user configuration files. Use the scope that matches how you want the connection available.

03

Control the contribution back

Choose read-only access for reference work or propose-only access for supported note changes. Direct write access is available when the workflow calls for it.

FROM IDEA TO USEFUL CONTEXT

Put it into practice.

  1. Add an MCP server

    Open Cursor’s MCP settings or use the configuration example in the agent guide.

  2. Connect the workspace

    Sign in with OAuth or provide a scoped Docblock token in the authorization header.

  3. Run a read-only test

    Ask Cursor to list accessible workspaces and read a known note before relying on the integration.

A FEW USEFUL DETAILS

Questions, answered.

Can I use OAuth instead of copying a token?

Yes. The documented Cursor setup uses OAuth when no authorization headers are supplied. Use the Needs login control to sign in.

Can access be limited to a project folder?

A Docblock grant can include an optional folder limit. The connection then reads and writes only within its granted workspace and folder access.

KEEP EXPLORING

Connect the next piece.

A PLACE TO BUILD ON

Give your next thought a home.

Start with a note. Add structure, connect an agent, and keep the useful context together.

Open Docblock