npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

notion-export-mcp-server

v0.0.3

Published

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

Readme

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

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:

...
    "lightdash": {
      "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