Notion MCP Server Cursor IDE Setup 2026: Query Your Workspace from Composer

Notion is where specs, RFCs, meeting notes, and project context live for most engineering teams. Connecting it to Cursor via MCP means your AI assistant can read your actual docs — not hallucinate them. Here's the complete setup.

What This Integration Enables

With Notion MCP running in Cursor, you can:

Prerequisites

Step 1: Create a Notion Integration

1. Go to notion.so/my-integrations.
2. Click + New integration.
3. Name it "Cursor MCP", select your workspace, and enable: Read content, Update content, Insert content.
4. Click Save and copy the Internal Integration Secret (starts with secret_).

Step 2: Connect Pages to Your Integration

Notion integrations only see pages you explicitly share with them:

1. Open any Notion page you want accessible from Cursor.
2. Click ··· (three dots, top right) → Add connections.
3. Select your "Cursor MCP" integration.
4. Repeat for parent pages, databases, or workspaces — child pages are accessible automatically.

For maximum utility, connect your top-level workspace pages (e.g., Engineering Hub, Product Docs, Meeting Notes) so everything underneath is automatically accessible.

Step 3: Install the Notion MCP Server

Notion has an official package:

npm install -g @notionhq/mcp

Or run it without a global install:

npx @notionhq/mcp --version

Step 4: Configure Cursor

Edit ~/.cursor/mcp.json (macOS/Linux) or %APPDATA%\Cursor\mcp.json (Windows):

{
  "mcpServers": {
    "notion": {
      "command": "npx",
      "args": ["-y", "@notionhq/mcp"],
      "env": {
        "NOTION_API_TOKEN": "secret_your_token_here"
      }
    }
  }
}

Some versions require the API version header. If tools don't appear after setup, add:

"NOTION_VERSION": "2022-06-28"

Step 5: Restart and Verify

Quit Cursor fully and reopen. Check Settings → Features → MCP for the "notion" server.

Test in Composer:

Search Notion for "authentication architecture"

Getting results confirms the integration is working.

Real-World Use Cases

Retrieving a Spec While Coding

You're implementing a feature and need to check the original requirements:

Find the Notion page titled "User Authentication v2 Spec" 
and show me the API contract section

Creating Docs from Code

After implementing a module, generate documentation directly into Notion:

Create a new Notion page in the "Engineering Docs" database 
titled "Rate Limiting Implementation" and write a technical summary 
of how this middleware works: [paste code]

Querying a Database

List all items in the Notion "Q2 Roadmap" database 
where Status is "In Progress" and Team is "Backend"

Pulling Meeting Notes for Context

Find the most recent Notion page with "backend architecture" in the title 
from the last 2 weeks and summarize the key decisions

Appending to an Existing Page

Add a new section to the Notion page "Deployment Runbook" 
with the header "Emergency Rollback Procedure" and the following steps: 
[list your steps]

Troubleshooting

Token not working (401 error)

"Object not found" for specific pages

Search returns no results

Tools don't appear in Cursor after setup

Read-Only vs. Read-Write Setup

If you only want Cursor to read Notion (safer for shared workspaces), create the integration with only Read content permissions enabled. This prevents Cursor from accidentally creating or modifying pages.

For full read-write, enable all three content capabilities. You'll gain the ability to create pages and databases directly from Composer.

Combining Notion with Other MCP Servers

Notion works best as a context layer alongside action-oriented tools:

Notion isn't the only knowledge base worth connecting, either — if your team (or you personally) keeps notes in Obsidian instead of or alongside Notion, the Obsidian MCP server covers the equivalent setup for a local, Markdown-file-based vault rather than a hosted workspace. If your docs live in Coda instead — pages with embedded live tables rather than Notion's block-and-database model — the Coda MCP server covers both Coda's own hosted server and the community npm alternative.

Notion itself isn't a fit for every kind of structured content, though — it's built around pages and databases for internal docs and specs, not a public-facing content model with a defined schema and API-level publishing controls. If what you actually need is structured content for a website or app (blog posts, product data, marketing copy that ships to production), the Sanity MCP server is built for that instead — a real schema, a dataset separate from your frontend code, and an MCP connection meant for content that leaves the building, not internal team docs.

Example multi-server workflow:

1. Read the Notion page "Feature: Billing Overhaul Spec"
2. Create a Linear issue "Implement billing overhaul" with the spec summary
3. Create a GitHub branch "feature/billing-overhaul" in the payments repo

All from a single Composer prompt.

Security

Notion's "share each page with the integration" model is a decent example of least privilege in practice, which is one of the patterns the MCP security checklist argues for more generally. If you're deciding how much write access to grant, the breakdown of tools versus resources is useful context: read-only servers expose resources, while anything that can change your workspace is a tool the model can invoke on its own.

More MCP Integrations

See the full MCP server directory to connect Slack, Linear, GitHub, Jira, and more to your Cursor workflow, or browse the documentation and knowledge-base servers if Notion is one of several places your team keeps written material. First time configuring Cursor for MCP at all? Start with the Cursor MCP setup guide.

For teams that track the actual task list in Asana rather than a Notion database, the Asana MCP server covers that workflow directly — a common pairing is Notion for specs and docs, Asana for the task tracking that executes against them.