Notion MCP Server — Official Notion Integration

What it is

Notion MCP Server is the official Model Context Protocol integration built by Notion. It exposes Notion's API -- pages, databases, blocks, search -- through the MCP standard so that AI coding assistants like Claude Code or Cursor can interact with your Notion workspace directly.

This is useful for developers and teams who want their AI agents to read project specs from Notion, create meeting notes, update task databases, or search across a workspace without leaving the editor.

How it saves time or tokens

Without this server, you would need to manually copy-paste content between Notion and your AI tool, or write custom API integration code. The MCP server eliminates that friction: the agent calls Notion's API directly, reads the data it needs, and acts on it. For workflows that involve frequent reference to documentation or task boards stored in Notion, this can save significant context-switching time.

How to use

1. Add the MCP server configuration to your AI editor's MCP settings:

{
  "mcpServers": {
    "notion": {
      "command": "npx",
      "args": ["-y", "@notionhq/notion-mcp-server"],
      "env": {
        "OPENAPI_MCP_HEADERS": "{\"Authorization\": \"Bearer ntn_YOUR_TOKEN\", \"Notion-Version\": \"2022-06-28\"}"
      }
    }
  }
}

1. Create a Notion internal integration at https://www.notion.so/my-integrations and copy the token.
2. Share the pages or databases you want the agent to access with your integration.
3. Restart your AI editor. The agent can now search, read, create, and update Notion content.

Example

Once configured, you can ask your AI agent:

'Search my Notion workspace for the Q2 product roadmap and summarize the key milestones.'

The agent will call the Notion MCP server's search endpoint, retrieve the matching page, read its blocks, and return a summary -- all without you opening Notion.

Related on TokRepo

• MCP integrations for Notion -- deep-dive into Notion MCP setup and use cases
• AI tools for automation -- other MCP servers and automation tools for AI agents

Common pitfalls

• You must explicitly share each Notion page or database with your integration. Unshared pages return empty results and this is the most common setup mistake.
• The integration token is scoped to a single workspace. If you work across multiple Notion workspaces, you need separate integrations for each.
• Rate limits apply. Notion's API has a rate limit that the MCP server does not bypass, so bulk operations on large databases may hit throttling.