This Notion MCP Server provides a standardized interface for AI clients to access, query, and modify content in Notion workspaces. It enables you to connect an MCP client to Notion, perform data retrieval and updates, and automate workspace workflows with ease.

How to use

You connect an MCP client to this server to perform data operations against your Notion workspace. Use it to list databases, inspect database schemas, fetch page contents, and apply updates or creations from natural language or scripted prompts. You can combine Notion data with other sources in your MCP client to build richer assistant workflows.

Start by launching the local Notion MCP Server and then configure your MCP client to point to the local process. In your MCP client, reference the server as a stdio-based MCP endpoint that runs a Node.js process and executes the built server script. Provide your Notion API key so the server can authenticate with Notion. Once connected, you can issue queries like listing databases, retrieving page content, or updating pages through your MCP client’s prompts and tools.

Key capabilities you can leverage include: listing databases, retrieving and inspecting database schemas, accessing page content, and applying changes or creates within your Notion workspace. When you issue tasks via your MCP client, the server translates them into Notion API calls, returning structured results you can present or use in subsequent prompts.

How to install

Prerequisites: ensure you have Node.js 16 or higher and a Notion API Key from your Notion integration.

Step 1: Clone the project and enter the directory.

# Required
NOTION_API_KEY=your_notion_api_key_here

Install dependencies, build, and run locally (these commands are shown in sequence)

npm install
npm run build
npm start

Configuration and running notes

Create a configuration file to supply your API key to the server at startup. The server expects an environment variable NOTION_API_KEY containing your Notion API key. You can run the server locally with a ready environment or define it in a startup script.

If you are using Claude for Desktop or another MCP client that supports a local stdio server, you can configure the client to launch the MCP server directly. A typical configuration passes the runtime command and the script path to the built server, along with the API key.

{
  "mcpServers": {
    "notion": {
      "command": "node",
      "args": ["/path/to/notion-mcp-server/build/index.js"],
      "env": {
        "NOTION_API_KEY": "your_notion_api_key_here"
      }
    }
  }
}

Backups and polling

The server supports configurable polling and backups. Adjust settings such as UPDATE_POLLING_INTERVAL and BACKUP_RETENTION_DAYS to suit your workspace needs. Backups are stored in the designated backup directory and are retained according to your retention policy.

Prompts and tool usage

Use the pre-configured prompts to query deadlines, project status, and daily tasks. You can ask the server to summarize upcoming deadlines, check progress on projects, or retrieve today’s tasks. You can also request operations like creating or updating Notion pages via natural language prompts.

Troubleshooting tips

If you encounter connection issues, verify that NOTION_API_KEY is correctly set in your environment and that the Notion integration has the required workspace permissions. Check that the server process is running and that the MCP client is configured to invoke the local stdio server with the correct path to the built script.

Examples of connected workflows

• Retrieve all databases and inspect their schemas to decide which tables to query.

• Fetch content from a specific page, then summarize changes or extract key data for reporting.

Available tools

upcoming-deadlines

Get a list of upcoming deadlines from your Notion workspace.

project-status

Summarize the status of a project by aggregating Notion data.

daily-tasks

Get a list of tasks for today from Notion databases.