Notion MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Node environment (development/production). | development |
| NOTION_TOKEN | Yes | The secret token for your Notion integration. | |
| SUPABASE_URL | No | Optional Supabase URL for audit logging. | |
| AUDIT_LOG_FILE | No | Path to audit log file if Supabase is not configured. | .audit/tool-calls.jsonl |
| OPENAI_API_KEY | No | Optional OpenAI API key. | |
| MCP_GATEWAY_API_KEY | No | Optional API key for MCP gateway. | |
| NOTION_ROOT_PAGE_ID | Yes | The ID of the root Notion page that this server can access. | |
| SUPABASE_SERVICE_ROLE_KEY | No | Optional Supabase service role key for audit logging. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| notion_searchB | Search the connected Notion workspace for pages matching a query. Risk: read. |
| notion_get_pageB | Retrieve a Notion page and its block content. Risk: read. |
| notion_create_pageA | Create a new Notion page under the configured root page or provided parent page. Risk: safe_write. |
| notion_append_to_pageA | Append content to an existing Notion page without replacing or deleting content. Risk: safe_write. |
| project_list_appsA | Return app/project names configured for this workspace. Risk: read. |
| project_get_contextC | Retrieve configured project context. Risk: read. |
| mission_log_decisionA | Log an architecture, product, business, security, or implementation decision to Notion. Risk: safe_write. |
| codex_generate_promptC | Generate a Codex-ready implementation prompt from configured project context and a current goal. Risk: read. |
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 8 tools
Each tool has a clearly distinct purpose: codex prompt generation, decision logging, Notion page operations (append, create, get, search), and project context retrieval. No overlaps.
Names follow snake_case and use a <domain>_<action> pattern, but prefixes vary (codex_, mission_log_, notion_, project_). Within each domain, naming is consistent; overall pattern is readable but not fully uniform.
8 tools is well-scoped for a Notion integration covering core operations (create, get, search, append) plus additional project context and decision logging. No redundancy.
Covers create, read, search, and append for Notion pages, but missing update and delete operations. Project context and decision logging are included, but the Notion surface is incomplete for full CRUD.