Connect Notion to Cursor
Give Cursor governed access to Notion’s 48 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Notion to Cursor in four steps
Admins approve the server once. Everyone in Cursor then gets it through the same governed connection.
- 1
Approve Notion in Runlayer
Add Notion from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Cursor to Runlayer
Runlayer’s CLI installs the Runlayer Plugin natively in Cursor, and admins can roll it out org-wide with Auto Sync plus a Cursor team rule. With direct tool listing turned on for your deployment, Notion’s 48 tools show up in Cursor’s own tool list.
Cursor setup guide - 3
Sign in to Notion
Sign in the way Notion requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Notion from Cursor
Notion’s approved tools appear in Cursor. Every call is checked against policy and recorded.
Tools
48 Notion tools in Cursor
Runlayer policy decides which of these Cursor users can call. 5 read data only and 1 can change or delete data.
AI search
Notion ai search.
Check MCP next steps
Finish all Notion tool calls needed for the current request, then call at most once with no arguments.
Convert page to skill
Mark an existing Notion page as a skill without changing its content.
Create attachment
Create an attachment and upload it to Notion.
Create comment
Add a comment to a page or specific content.
Create database
Creates a new Notion database using SQL DDL syntax, or a canonical typed database for tasks, projects, or skills.
Create file upload
Create a short-lived URL for uploading one local file directly to Notion.
Create folder
Creates an empty Notion Folder.
Control
What Runlayer can see and stop in Cursor
Some controls apply to every client at the gateway. Others depend on what Cursor exposes to Runlayer.
Gateway policy (available)
Every Notion call from Cursor passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Cursor as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call before Cursor runs it, including calls to MCP servers.
Block output after it runs (available)
Runlayer can block a tool’s output before Cursor’s model sees it.
Redact output in place (not available)
Cursor cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.
In Cursor
- Runlayer cannot tell Agents Window sessions apart from regular IDE sessions.
- The Cursor CLI sends fewer session events than the IDE, but Runlayer’s allow and deny decisions still apply.
Frequently asked questions
Connect more