Enterprise DNA
M MCP Servers Developer low

kirvigen/notion-private-api-mcp

by Various

Unofficial Notion MCP server via the private API (tokenv2) — full read/write, no integration token.

K

MCP

kirvigen/notion-private-api-mcp

Added 7 June 2026

#ai #anthropic #automation #claude #claude-code #claude-desktop #cursor #llm

Overview

An unofficial MCP server for Notion that uses the private API (tokenv2) instead of the official integration token. It provides full read and write access to Notion workspaces. Built in JavaScript, it is a community project with limited adoption.

Best for

Best for
Developers who need full Notion access but cannot or prefer not to use the official API

Use cases

  • Automate Notion page creation and updates without an official API token
  • Build custom MCP tools that read and write Notion databases
  • Integrate Notion with other MCP-compatible applications

Notes

An unofficial MCP server for Notion that uses the private API (tokenv2) instead of the official integration token. It provides full read and write access to Notion workspaces. Built in JavaScript, it is a community project with limited adoption.

1 stars on GitHub. Last updated 2026-06-01. Licensed MIT.

Use cases

  • Automate Notion page creation and updates without an official API token
  • Build custom MCP tools that read and write Notion databases
  • Integrate Notion with other MCP-compatible applications

Pros

  • Full read and write access to Notion workspaces
  • No need for an official Notion integration token
  • Works with existing Notion accounts via tokenv2

Cons

  • Relies on the private API which may break without notice
  • Very low community adoption (1 star) suggests limited reliability
  • Using tokenv2 poses security risks and is not officially supported

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • Full read and write access to Notion workspaces
  • No need for an official Notion integration token
  • Works with existing Notion accounts via tokenv2

Cons

  • Relies on the private API which may break without notice
  • Very low community adoption (1 star) suggests limited reliability
  • Using tokenv2 poses security risks and is not officially supported