Skip to main content
Glama
notion-export-mcp-server

notion-export-mcp-server

by syucream

notion-export-mcp-server

npm version

A MCP(Model Context Protocol) server that accesses to Notion unofficial API to export pages.

This server provides MCP-compatible access to Notion's unofficial API, allowing AI assistants to interact with your Notion exported page data through a standardized interface.

Features

Available tools:

  • notion_export_get_result - Get notion export result markdown text

Related MCP server: notion-mcp-server

Quick Start

Installation

Manual Installation

npm install notion-export-mcp-server

Configuration

  • NOTION_TOKEN_V2: Your Notion token

  • NOTION_FILE_TOKEN: Your Notion file token

Usage

Start the MCP server

Directly:

npx notion-export-mcp-server

Or, run the installed module with node.

Edit MCP configuration json for your client:

...
    "notion-export": {
      "command": "npx",
      "args": [
        "-y",
        "notion-export-mcp-server"
      ],
      "env": {
        "NOTION_TOKEN_V2": "<your token>",
        "NOTION_FILE_TOKEN": "<your token>"
      }
    },
...

Secrets?

How to get

To export anything from Notion, one needs to authenticate oneself with some Cookies (like a browser would). These cookies are called token_v2 and file_token. They are set on all requests of a logged in user when using the Notion web-app.

  1. Go to notion.so.

  2. Log in with your account.

  3. Open the developer tools of your browser, open Application > Storage > Cookies (Chrome); Storage tab (Firefox).

  4. Copy the value of the Cookies called token_v2 and file_token and paste them somewhere safe.

    • ⚠️ If you don't find file_token, you need to have at least had exported a file manually once.

  5. Those cookies have a 1 year validity, so you don't need to do this often.

Note on Stability

This tool completely relies on the export/download feature of the official but internal Notion.so API. The advantage is, that we do not generate any markup ourselves, just download and extract some ZIPs. While the download feature seems to be pretty stable, keep in mind that it still is an internal API, so it may break anytime.

Development

Available Scripts

  • npm run dev - Start the server in development mode with hot reloading

  • npm run build - Build the project for production

  • npm run start - Start the production server

  • npm run lint - Run linting checks (ESLint and Prettier)

  • npm run fix - Automatically fix linting issues

  • npm run examples - Run the example scripts

Contributing

  1. Fork the repository

  2. Create your feature branch

  3. Run tests and linting: npm run lint

  4. Commit your changes

  5. Push to the branch

  6. Create a Pull Request

Available Tools

1 tool
notion_export_get_resultC

Get notion export result

Inputs: id (required), recursive.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.7/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of overlap or confusion. The tool's purpose is clearly stated as retrieving a Notion export result.

    Naming Consistency5/5

    The single tool name follows a clear verb_noun pattern (get_result) with a domain prefix (notion_export). No inconsistencies exist in the set.

    Tool Count2/5

    One tool is too few for a server dedicated to Notion exports. Typical export workflows require initiating an export, listing exports, and retrieving results, so the current count is insufficient for the apparent scope.

    Completeness1/5

    The server only supports retrieving an export result, missing essential operations like creating an export or checking export status. This severely limits the tool's usability and leaves the workflow incomplete.

    Related MCP Connectors

    Related MCP Servers