# Notion

> Read, write, and search across Notion pages, databases, and blocks.

[Canonical HTML page](https://top-mcps.com/mcp/notion) · [server.json](https://top-mcps.com/mcp/notion.json) · [methodology](https://top-mcps.com/about/methodology)

## Install

### Claude Desktop — `claude_desktop_config.json`

Paste under mcpServers. Fully quit and reopen Claude after editing.

```json
{
  "mcpServers": {
    "notion": {
      "command": "npx",
      "args": [
        "-y",
        "@notionhq/notion-mcp-server"
      ],
      "env": {
        "NOTION_API_KEY": "${NOTION_API_KEY}"
      }
    }
  }
}
```

### Claude Code — `CLI or .mcp.json`

Run from your repo. Commit .mcp.json to share with your team.

```shell
# export NOTION_API_KEY=secret_your_integration_token
claude mcp add notion -- npx -y @notionhq/notion-mcp-server
```

### Cursor — `.cursor/mcp.json`

Global path: ~/.cursor/mcp.json. Reload window after editing.

```json
{
  "mcpServers": {
    "notion": {
      "command": "npx",
      "args": [
        "-y",
        "@notionhq/notion-mcp-server"
      ],
      "env": {
        "NOTION_API_KEY": "${NOTION_API_KEY}"
      }
    }
  }
}
```

### VS Code — `.vscode/mcp.json`

VS Code uses the "servers" key (not "mcpServers").

```jsonc
{
  "servers": {
    "notion": {
      "command": "npx",
      "args": [
        "-y",
        "@notionhq/notion-mcp-server"
      ],
      "env": {
        "NOTION_API_KEY": "${NOTION_API_KEY}"
      }
    }
  }
}
```

### Windsurf — `~/.codeium/windsurf/mcp_config.json`

Open via Cascade → hammer icon → Configure.

```json
{
  "mcpServers": {
    "notion": {
      "command": "npx",
      "args": [
        "-y",
        "@notionhq/notion-mcp-server"
      ],
      "env": {
        "NOTION_API_KEY": "${NOTION_API_KEY}"
      }
    }
  }
}
```

### Cline — `cline_mcp_settings.json`

Open via the Cline sidebar → MCP Servers → Edit.

```json
{
  "mcpServers": {
    "notion": {
      "command": "npx",
      "args": [
        "-y",
        "@notionhq/notion-mcp-server"
      ],
      "env": {
        "NOTION_API_KEY": "${NOTION_API_KEY}"
      }
    }
  }
}
```

### Continue — `~/.continue/config.json`

Continue uses modelContextProtocolServers with a transport block.

```json
{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "@notionhq/notion-mcp-server"
          ],
          "env": {
            "NOTION_API_KEY": "${NOTION_API_KEY}"
          }
        }
      }
    ]
  }
}
```

### Codex CLI — `~/.codex/config.toml`

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

```shell
# ~/.codex/config.toml
[mcp_servers.notion]
command = "npx"
args = [
  "-y",
  "@notionhq/notion-mcp-server",
]
env = { NOTION_API_KEY = "${NOTION_API_KEY}" }
```

### Zed — `~/.config/zed/settings.json`

Zed calls them "context_servers". Settings live-reload on save.

```jsonc
{
  "context_servers": {
    "notion": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "@notionhq/notion-mcp-server"
        ]
      },
      "env": {
        "NOTION_API_KEY": "${NOTION_API_KEY}"
      }
    }
  }
}
```

### ChatGPT — `ChatGPT → Settings → Connectors → Developer mode`

Enable Developer mode (paid plans) and enter these values in the UI.

```json
{
  "name": "Notion",
  "transport": "stdio",
  "command": "npx",
  "args": [
    "-y",
    "@notionhq/notion-mcp-server"
  ],
  "env": {
    "NOTION_API_KEY": "${NOTION_API_KEY}"
  }
}
```

## At a glance

- **Maintainer:** Notion
- **Transport:** stdio
- **Auth model:** API key
- **Required secrets:** NOTION_API_KEY
- **Supported clients:** Claude, Cursor, Any MCP-compatible client, Notion workspaces
- **License:** MIT
- **Language:** TypeScript
- **Latest version:** latest
- **Last verified:** 2026-04-19
- **GitHub stars:** 4,239 (fetched 2026-04-19T20:32:55.621Z)
- **Score:** 85/100 (rubric 2026-04 — see https://top-mcps.com/about/methodology)
- **Source:** https://github.com/makenotion/notion-mcp-server

## Security & scope

- **Access scope:** read-write
- **Sandbox:** Authenticates via a Notion integration token with exactly the permissions granted to the integration at installation time.
- **Gotchas:**
  - The integration only sees pages explicitly shared with it — on un-shared pages the MCP returns 404.
  - Integration tokens cannot be restricted to a single workspace — they have workspace-level access once granted.

## Quick answer

**What it does.** Surfaces Notion's page, database, and block APIs as MCP tools — search, read, create, update, and query with filter expressions.

**Best for:**
- Agent-generated meeting notes
- Project database queries
- Living knowledge-base updates
- Auto-generated status pages
- Internal doc lookups

**Not for:**
- Bulk content migration
- Real-time collaborative editing
- Binary asset storage

## Recipes

### Summarise a known workspace page

```
Find the page titled "Weekly Planning" in my Notion workspace and summarise its current state in 5 bullets. Highlight any item blocked on someone else.
```

_Tested with: Claude Desktop, Cursor_

## Description

The official Notion MCP gives AI agents structured access to your Notion workspace. Query databases by filter, create pages, append blocks, fetch page contents, and keep a living knowledge base in sync with what your agents produce.

## Why it matters

Notion is where a lot of teams keep their operating knowledge. An agent that can read and append there closes the loop between AI work and the team's source of truth.

## Key features

- Pages + blocks + databases CRUD
- Rich database filter expressions
- Official Notion maintenance
- Integration token scoping per workspace
- Structured block-tree output

## FAQ

### How do I grant the MCP access to my pages?

Create a Notion integration at notion.so/profile/integrations, copy the secret, and share each page or database with the integration from Notion's share panel. The integration only sees what you explicitly share.

### Can it query a database by filter?

Yes — the server exposes Notion's full filter syntax, including compound `and`/`or` groups, date ranges, relations, and rollup conditions. Large result sets paginate automatically.

### What happens with formatted blocks — does it preserve headings and lists?

Yes. The server returns block trees with types preserved (heading_1, bulleted_list_item, toggle, etc.) so the model can reason about structure, not just flat text. Writes round-trip the same shape back.

### Is there a rate limit I should worry about?

Notion enforces ~3 requests/second per integration. Tight agent loops that fan out queries can hit that ceiling; use the MCP's pagination helpers and cache read-heavy results to stay under it.

## Changelog

- **2026-04-19** — Refreshed install snippets and fact sheet; verified for 2026.
- **2025-03-15** — Initial directory listing.