MCP.so
Sign In

Browse your entire Notion workspace, not just one database

@seonglae

Repository

About Browse your entire Notion workspace, not just one database

Global Notion workspace-accessible MCP server for all Notion pages within the workspace

#mcp#notion#notion-api#prompt-engineering#anthropic#model-context-protocol#context-protocol#ai-protocol

Basic information

Category

Memory & Knowledge

Runtime

node

Transports

stdio

Publisher

seonglae

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp-notion": {
      "command": "npx",
      "args": [
        "-y",
        "supergateway",
        "--port",
        "8000",
        "--stdio",
        "npx -y @modelcontextprotocol/server-filesystem /some/folder"
      ]
    }
  }
}

Tools

2

Query text to filter relevant pages.

Markdown content of matching notes.

Overview

What is notion-texonom?

notion-texonom is a TypeScript-based MCP server that lets you browse and interact with your entire Notion workspace using a single ROOT_PAGE variable, converting pages into text/markdown notes. It is designed for developers and Claude Desktop users who need to search, retrieve, and summarize Notion pages based on graph distance (parent-child and reference relationships) without requiring an API token.

How to use notion-texonom?

Install dependencies with pnpm install, build with pnpm build, and set the ROOT_PAGE environment variable to your root page ID. Configure the server in Claude Desktop's claude_desktop_config.json under the notion-texonom MCP server entry, or run remotely via SSEServerTransport using npx supergateway.

Key features of notion-texonom

  • List and retrieve Notion pages as note:// URIs with UUID slugs
  • Search notes using the search_notes tool with query text input
  • Summarize individual pages with the summarize_note prompt
  • Suggest structural improvements, fixes, and enhancements
  • Content delivered in text/markdown format

Use cases of notion-texonom

  • Browse your entire Notion workspace without per-database tokens
  • Search and retrieve relevant pages by query and graph distance
  • Automatically generate summaries for note-taking and review
  • Propose refactors, fixes, or enhancements to existing notes

FAQ from notion-texonom

How is notion-texonom different from other Notion MCP servers?

It requires only a single ROOT_PAGE variable and no API token, and it browses the entire workspace, not just one database.

What dependencies does notion-texonom require?

It uses TypeScript, pnpm, and the @texonom/nclient, @texonom/cli, and @modelcontextprotocol/sdk packages.

Where does my data live?

All data remains in your Notion workspace; the server accesses pages via the ROOT_PAGE ID and does not store content externally.

What transport and auth are available?

The server supports stdio transport by default and can be deployed remotely with SSEServerTransport. Authentication is handled solely by the ROOT_PAGE UUID environment variable.

Comments

More Memory & Knowledge MCP servers

🧠 Ultimate MCP Server

Dicklesworthstone

Comprehensive MCP server exposing dozens of capabilities to AI agents: multi-provider LLM delegation, browser automation, document processing, vector ops, and cognitive memory systems

154

RAG Documentation MCP Server

hannesrudolph

An MCP server implementation that provides tools for retrieving and processing documentation through vector search, enabling AI assistants to augment their responses with relevant documentation context.

267

Basic Memory

basicmachines-co

AI conversations that actually remember. Never re-explain your project to your AI again. Join our Discord: https://discord.gg/tyvKNccgqN

3.4K

Ultimate Google Docs & Drive MCP Server

a-bonus

The Ultimate Google Docs, Sheets, Drive, Gmail, & Google Calendar MCP Server. This MCP (primarily for use in Claude Desktop) gains full access to your google suite and lets claude do its thing.

605

Mcp Knowledge Graph

shaneholloman

MCP server enabling persistent memory for Claude through a local knowledge graph - fork focused on local development

871