search_notesLABSCO 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_notestakes 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_fixandsuggest_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.
Setup effort
Build from source
USE CASES
01
Finding a note across the whole workspace
Search once instead of remembering which database the page lives in.
02
Summarising a long page
Point the summarise prompt at the page URI and get the short version back.
03
Tidying a page that has grown messy
Ask for structural improvements or fixes to the note's content rather than rewriting it yourself.
04
Sharing one server across a team
Run it over SSE rather than starting a separate stdio process per person.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/seonglae/mcp-notion
cd mcp-notion
pnpm install
pnpm buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"notion-texonom": {
"command": "node",
"args": [
"<YOUR_PATH_TO_MCP>/build/index.js"
],
"env": {
"ROOT_PAGE": "$SOME_UUID"
}
}
}
}
