MCP Notion Upload Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTION_API_TOKEN | No | Your Notion API token (secret_your_notion_token_here) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| upload_file_to_notionA | |
| upload_and_attach_file_to_pageA | |
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 2 tools
The two tools have overlapping purposes that could cause confusion. 'upload_and_attach_file_to_page' includes uploading as part of its workflow, while 'upload_file_to_notion' is a standalone upload tool. An agent might struggle to choose between them when they just need to upload a file without attaching it to a page.
Both tools follow a consistent snake_case naming pattern with clear verb_noun structure. 'upload_and_attach_file_to_page' and 'upload_file_to_notion' are descriptive and follow the same naming convention throughout.
With only 2 tools, this server feels thin for a Notion integration. A typical Notion MCP server would include more operations like creating pages, retrieving content, updating blocks, or searching databases. The limited tool count suggests incomplete coverage of the domain.
The server is severely incomplete for a Notion integration. It only covers file upload operations, missing essential CRUD operations for pages, databases, blocks, and other core Notion resources. There's no way to create, read, update, or delete basic Notion objects beyond file attachments.