Labsco
MCP SERVER

Notion

by seonglae

Browse a whole Notion workspace as Markdown from one root page id — no integration token to create.

Team Wikis & Documentation Platforms
Summary
One variable instead of a Notion integration, and the whole workspace instead of one database.

Most Notion bridges want an integration token and a database id, which limits them to the tables you remembered to share. Here a root page id is the entire configuration, and traversal follows links, so a page reached only by reference still turns up. The prompts go further than reading — refactor and fix suggestions treat your notes as something to improve, not just to quote.

What it is

A TypeScript server that walks Notion from a single root page and converts pages into `text/markdown` notes. Retrieval is by graph distance, following parent-child and reference relationships, rather than a flat keyword index over one database.

What you get
  • Pages exposed as resources under `note://` URIs with UUID slugs, each carrying a title, description and Markdown body
  • `search_notes` takes a query string and returns the Markdown of matching pages
  • Ranking that considers how pages link to each other, not just how they match the words
  • Four prompts over a page URI: `summarize_note`, `suggest_refactor`, `suggest_fix` and `suggest_enhance`
Requirements

One environment variable, `ROOT_PAGE`, set to the root page id of your workspace. Build from source with `pnpm install` and `pnpm build`, then point your client at `build/index.js` with `node`. It is built on `@texonom/nclient` and `@texonom/cli`; an SSE transport is available for shared remote use.