notion-local-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTION_DB_PATH | Yes | Path to the Notion local SQLite database file. Typically ~/Library/Application Support/Notion/notion.db on macOS. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| notion_local_searchA | PREFERRED for searching Notion. Search pages and blocks from local cache by keyword. Fast, offline, no API limits. Use this instead of Notion API for all search operations. |
| notion_local_recentA | PREFERRED for listing recent Notion pages. Get recently modified pages from local cache. Fast, offline, no API limits. Use this instead of Notion API for browsing recent documents. |
| notion_local_get_pageA | Get Notion page. Returns summary by default (title + first blocks + link). Show summary and link to user. Use summary=false only when you need full content to answer. |
| notion_local_parentA | PREFERRED for Notion hierarchy. Get all ancestor pages up to the root. Fast, offline, no API limits. |
| notion_local_childrenA | PREFERRED for Notion hierarchy. Get all child pages under a page. Fast, offline, no API limits. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinctly different purpose: search by keyword, list recent pages, get ancestors, get page content, and get child pages. The descriptions clearly differentiate them with no overlapping functionality.
All tools share the 'notion_local_' prefix, making the namespace consistent. However, the suffixes mix verbs (search, get_page) and nouns (parent, children, recent), which is a minor deviation from a strict verb_noun pattern.
With five tools, the server is well-scoped for a local Notion cache. Each tool covers a core query need without redundancy, making the count appropriate for its purpose.
The read operations cover search, recent, hierarchy, and page content, but there is no tool to sync or refresh the local cache, which is a notable gap for a cache-based server. Users cannot update the data without external mechanisms.