home / mcp / notion mcp server

Notion MCP Server

**Notion MCP Server** is a Model Context Protocol (MCP) server implementation that enables AI assistants to interact with Notion's API. This production-ready server provides a complete set of tools.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "awkoy-notion-mcp-server": {
      "command": "env NOTION_TOKEN=YOUR_KEY NOTION_PAGE_ID=YOUR_PAGE_ID npx",
      "args": [
        "-y",
        "notion-mcp-server"
      ],
      "env": {
        "NOTION_TOKEN": "YOUR_KEY",
        "NOTION_PAGE_ID": "YOUR_PAGE_ID"
      }
    }
  }
}

You can empowering your AI assistants to work with Notion by running a dedicated MCP server. This server exposes a complete set of tools to read, create, and modify Notion content through natural language interactions, making Notion data accessible to your MCP clients with reliable, production-ready endpoints.

How to use

You connect the Notion MCP Server to your MCP client (such as Cursor or Claude Desktop) and start it with your Notion API credentials. Once the server is running, you can ask your AI assistant to create pages, update content, manage databases, handle blocks, search pages, and handle comments and users within Notion. Use natural language prompts like: - Create a new page with today\'s tasks - Update meeting notes in Notion - Add bullet points to a notes page - Create a new database for tracking projects - Add entries to a task database - Get information about workspace users and permissions The server exposes a cohesive set of tools to perform these actions in a single MCP workflow.

How to install

Before you start, ensure you have Node.js and npm installed on your system. Then you can run the MCP server directly with a local command or configure a client to launch it as part of your MCP workflow.

Option A: Run via a direct MCP command (recommended for quick setup) in your shell or your MCP client configuration.

Option B: Use a local configuration file to auto-start the server from your MCP client. The following examples show how to reference the server using standard MCP tooling.

Configuration and setup details

You will configure a local MCP server instance that uses Notion authentication tokens and a target Notion page. The server is started through a command that runs the server package and passes environment variables for access.

Environment variables you will need: - NOTION_TOKEN: Your Notion API integration token - NOTION_PAGE_ID: The Notion page you want the server to operate on

Examples of integration configurations

Cursor integration uses a project file to define the MCP server and exposes the server via a standard command to launch the server with the proper environment and arguments.

{
  "mcpServers": {
    "notion-mcp-server": {
      "command": "env NOTION_TOKEN=YOUR_KEY NOTION_PAGE_ID=YOUR_PAGE_ID npx",
      "args": ["-y", "notion-mcp-server"]
    }
  }
}

Claude Desktop integration uses a similar pattern

Claude Desktop can also start the MCP server with environment variables for Notion access.

{
  "mcpServers": {
    "notion-mcp-server": {
      "command": "npx",
      "args": ["-y", "notion-mcp-server"],
      "env": {
        "NOTION_TOKEN": "YOUR_KEY",
        "NOTION_PAGE_ID": "YOUR_PAGE_ID"
      }
    }
  }
}

Available tools

notion_pages

Interact with Notion pages: create pages, update properties, archive/restore, and search by title.

notion_blocks

Manage blocks: retrieve, append, update, delete blocks, and perform batch operations.

notion_database

Operate on databases: create, query with filters/sorting, and update structure.

notion_comments

Handle comments on pages and discussions: get, add, and reply to comments.

notion_users

Access workspace user information: list users and get user details.