Skip to main content

Announcing StackOne Defender: leading open-source prompt injection guard for your agent Read More

Notion MCP Server
for AI Agents

Production-ready Notion MCP server with 27 extensible actions — plus built-in authentication, security, and optimized execution.

Notion logo
Notion MCP Server
Built by StackOne StackOne

Coverage

27 Agent Actions

Create, read, update, and delete across Notion — and extend your agent's capabilities with custom actions.

Authentication

Agent Tool Authentication

Per-user OAuth in one call. Your Notion MCP server gets session-scoped tokens with zero credentials stored on your infra.

Agent Auth →

Security

Agent Protection

Every Notion tool response scanned for prompt injection in milliseconds — 88.7% accuracy, all running on CPU.

Prompt Injection Defense →

Performance

Max Agent Context. Min Cost.

Free up to 96% of your agent's context window to enhance reasoning and reduce cost, on every Notion call.

Tools Discovery →

What is the Notion MCP Server?

A Notion MCP server lets AI agents read and write Notion data through the Model Context Protocol — Anthropic's open standard for connecting LLMs to external tools. StackOne's Notion MCP server ships with 27 pre-built actions, fully extensible via the Connector Builder — plus managed authentication, prompt injection defense, and optimized agent context. Connect it from MCP clients like Claude Desktop, Cursor, and VS Code, or from agent frameworks like OpenAI Agents SDK, LangChain, and Vercel AI SDK.

How Your AI Agent Uses the Notion MCP Server

Interactive demo available on desktop.

All Notion MCP Tools and Actions

Every action from Notion's API, ready for your agent. Create, read, update, and delete — scoped to exactly what you need.

Block Children

  • Append Block Children

    Append blocks to a parent block or page

  • Get Block Children

    Retrieve children of a block

Blocks

  • Get Block

    Retrieve a block by ID

  • Update Block

    Update a block's content

  • Delete Block

    Delete a block

Comments

  • Create Comment

    Create a comment on a page, block, or discussion thread

  • Get Comments

    Retrieve comments from a page or block

  • Retrieve Comment

    Retrieve a specific comment by ID

Databases

  • Create Database

    Create a new database with initial data source

  • Get Database

    Retrieve a database by ID

  • Update Database

    Update database-level properties

Data Sources

  • Create Data Source

    Create a new data source in an existing database

  • Retrieve Data Source

    Retrieve a data source by ID

  • Query Data Source

    Query a data source and retrieve pages

  • Update Data Source

    Update a data source's properties and metadata

Data Source Templates

  • List Data Source Templates

    List all page templates for a data source

File Uploads

  • List File Uploads

    List all file uploads for the bot integration

  • Retrieve File Upload

    Get details of a specific file upload by ID

Pages

  • Create Page

    Create a new page in a Notion workspace

  • Get Page

    Retrieve a page by ID

  • Update Page

    Update page properties, icon, cover, or apply template

  • Move Page

    Move a page to a new parent location

Page Propertys

  • Get Page Property

    Retrieve a page property item

Searchs

  • Search

    Search all pages and data sources

Users

  • List Users

    List all users in the workspace

  • Get User

    Retrieve a user by ID

Bot Users

  • Get Bot User

    Retrieve information about the bot user

Set Up Your Notion MCP Server in Minutes

One endpoint. Any framework. Your agent is talking to Notion in under 10 lines of code.

MCP Clients

Agent Frameworks

Claude Desktop
{
  "mcpServers": {
    "stackone": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://api.stackone.com/mcp?x-account-id=<account_id>",
        "--header",
        "Authorization: Basic <YOUR_BASE64_TOKEN>"
      ]
    }
  }
}

More Documents & Knowledge MCP Servers

Confluence

133+ actions

Lokalise

101+ actions

ClickUp

92+ actions

Discourse

67+ actions

Google Drive

47+ actions

JotForm

44+ actions

Figma

39+ actions

Notion MCP Server FAQ

Notion MCP server vs direct API integration — what's the difference?
A Notion MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software — backend code calling Notion. A Notion MCP server is for AI agents — MCP clients like Claude and Cursor, plus framework agents built with OpenAI, LangChain, or Vercel AI — discovering and calling Notion at runtime. StackOne provides both.
How does Notion authentication work for AI agents?
Notion authentication for AI agents works through a StackOne Connect Session. Create one via the dashboard or the SDK — you get an auth link and ready-to-paste config for Claude Desktop, Cursor, and other MCP clients. Your user authenticates their own Notion account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via origin_owner_id.
Are Notion MCP tools vulnerable to prompt injection?
Yes — Notion MCP tools can be vulnerable to indirect prompt injection. Any tool that reads user-written content — documents, messages, tickets, records, or free-text fields — is a potential vector. StackOne Defender scans every tool response before it enters the agent's context — regex patterns in ~1ms, then a MiniLM classifier in ~4ms. 88.7% accuracy, CPU-only.
What is the context bloat of a Notion agent and how do I avoid it?
Context bloat happens when Notion tool schemas and API responses eat your Notion agent's memory, preventing it from reasoning effectively. A single Notion query can return a massive JSON response, and connecting multiple tools compounds the problem. Tools Discovery and Code Mode reduce context bloat — loading only relevant tools per query and keeping raw responses out of the agent's context.
Can I limit which actions my Notion agent can access?
Yes — you can limit which actions your Notion agent can access directly from the StackOne dashboard. Toggle actions on or off, or restrict them to specific accounts, with no code changes to your agent. Session tokens can be scoped to exact actions so if one leaks, exposure stays contained.
Can I create custom agent actions for my Notion MCP server?
Yes — you can create custom agent actions for your Notion MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research Notion's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a Notion MCP server?
Skip a Notion MCP server if your integration is purely software-to-software — direct Notion API integration is simpler when no AI agent is involved. For deterministic, compliance-critical operations (financial transactions, regulatory reporting), direct API gives you predictable behavior without agent-driven decision-making. MCP shines when AI agents need to dynamically discover and call Notion actions at runtime.
What AI frameworks and AI clients does the StackOne Notion MCP server support?
The StackOne Notion MCP server supports both. MCP clients (paste-and-go apps): Claude Desktop, Claude Code, Cursor, VS Code, Goose. Agent frameworks (code SDKs you build with): OpenAI Agents SDK, Anthropic, Vercel AI, Google ADK, CrewAI, Pydantic AI, LangChain, LangGraph, Azure AI Foundry.

Put your AI agents to work

All the tools you need to build and scale AI agent integrations, with best-in-class connectivity, execution, and security.