Skip to main content
Back to the Notion MCP server

MCP Gateway · Cursor

Notion icon

Connect Notion to Cursor

Cursor can keep the Notion spec next to the code that implements it. Developers fetch the spec while they build, update the documentation page when behavior changes, and look up who to ask about a teamspace. Cursor hooks check each prompt and tool call with Speakeasy before they run and fail closed if the check can't complete.

Category
Productivity
Tools
14
Authentication
OAuth
Cursor
Editor and terminal

Behind the MCP Gateway

Run Notion MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Notion call inspected and logged.

Deploy on MCP Gateway

Set up

Add Notion to Cursor in 4 steps

  1. 01

    Add Notion from the catalog

    An admin finds Notion in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.

    Notion uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.

    Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.

  2. 02

    Choose who can use Notion

    Give teams the mcp:connect scope on the Notion server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Notion to their gateway on the next call, and removing it takes it away.

  3. 03

    Connect Cursor

    Add the gateway to Cursor in one click from the Organization Gateway page.

    On the Organization Gateway page in Speakeasy, choose Cursor under Install.

    Click Add to Cursor to add the gateway to Cursor's MCP settings, then sign in when Cursor prompts you.

  4. 04

    Sign in and use Notion from Cursor

    The first time Cursor connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    Notion needs its own OAuth grant, so each person connects it once. Until they do, Notion calls fail while the rest of the gateway keeps working.

    From then on, Notion's tools appear in Cursor, limited to what the person's access allows, and every call lands in the gateway's tool logs.

For a whole team, a Cursor team admin imports the plugin marketplace under Settings > Plugins > Import and turns on Serve Marketplace From Cursor, so members install without GitHub access.

Use cases

What Cursor users do with Notion

Implement from the spec page

Paste the spec's Notion URL and Cursor fetches the page, so its requirements and examples sit in the editor alongside the code you're writing.

notion-fetch

Update docs when behavior changes

After a change alters how a feature works, Cursor edits the relevant section of the Notion documentation page so the page and the code agree.

notion-update-page

Find who to ask about a teamspace

Cursor lists the workspace's teamspaces and members, so you can find who owns the area a spec belongs to before you raise a question.

notion-get-teamsnotion-get-users

Tools

14 tools

Each Notion tool can be allowed or denied per team and role at the MCP Gateway before Cursor sees it.

notion-fetch

Retrieves details about a Notion entity (page, database, or data source) by URL or ID. Provide URL or ID in id parameter. Make multiple calls to fetch multiple entities. Pages use enhanced Markdown format.

notion-create-pages

Overview Creates one or more Notion pages, with the specified properties and content. Parent All pages created with a single call to this tool will have the same parent. The parent can be a Notion page ("page_id") or data source ("data_source_id").

notion-update-page

Overview Update a Notion page's properties or content. Properties Notion page properties are a JSON map of property names to SQLite values. For pages in a database: - ALWAYS use the "fetch" tool first to get the data source schema and the exact property names.

notion-move-pages

Move one or more Notion pages or databases to a new parent.

notion-duplicate-page

Duplicate a Notion page. The page must be within the current workspace, and you must have permission to access it. The duplication completes asynchronously, so do not rely on the new page identified by the returned ID or URL to be populated immediately.

See all 14 tools

Control

What Speakeasy can see and stop in Cursor

The gateway covers every client the same way. The rest depends on what Cursor exposes to Speakeasy.

Tool logs

Gateway

Every Notion call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the Notion tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to Notion can reject a tool request before it reaches the server, or withhold a result from Cursor. MCP-scoped policies are enabled per organization.

Prompt and tool-call blocking

Cursor

Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it before Cursor runs it, and fail closed.

User attribution

Cursor

Every Cursor hook event carries the user's email.

Budgets

Cursor

Spend limits can block Cursor traffic once a budget is reached. Connect the Cursor Admin API for dollar spend.

Device agent and MDM

Cursor

The device agent installs the marketplace and plugins and reapplies them every minute.

  • Cursor Cloud agents need a checked-in .cursor/hooks.json. Session and MCP-specific hooks don't run there.
  • After a plugin update, members run Developer: Reload Window.

Questions

Frequently asked questions

How does a Cursor team get Notion without GitHub access?
A Cursor team admin imports the plugin marketplace under Settings > Plugins > Import and turns on Serve Marketplace From Cursor, so members install without GitHub access.
What do Cursor Cloud agents need for Speakeasy checks?
Cursor Cloud agents need a checked-in .cursor/hooks.json, and session and MCP-specific hooks don't run there.
How do Cursor users get Notion?
An admin adds Notion from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway to Cursor in one click from the Organization Gateway page. Each person then sees only the Notion tools their access allows.
Are Notion calls from Cursor logged?
Yes. Notion calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Notion in other clients

AI everywhere.

Control here.