notion-export-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTION_TOKEN_V2 | Yes | Your Notion token v2 cookie value | |
| NOTION_FILE_TOKEN | Yes | Your Notion file token cookie value |
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_export_get_resultC | Get notion export result |
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 1 tool
With only one tool, there is no possibility of overlap or confusion. The tool's purpose is clearly stated as retrieving a Notion export result.
The single tool name follows a clear verb_noun pattern (get_result) with a domain prefix (notion_export). No inconsistencies exist in the set.
One tool is too few for a server dedicated to Notion exports. Typical export workflows require initiating an export, listing exports, and retrieving results, so the current count is insufficient for the apparent scope.
The server only supports retrieving an export result, missing essential operations like creating an export or checking export status. This severely limits the tool's usability and leaves the workflow incomplete.