MCP Notion Upload Server
Related Servers
Alternatives to MCP Notion Upload Server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceEnables uploading images and files to Notion pages from Cursor chat, supporting multiple attachment types like image blocks, file blocks, cover images, and icons.2-
- AlicenseNot gradedqualityAmaintenanceGives MCP clients such as Claude, Cursor, VS Code and Codex token-authenticated read/write access to a Notion workspace, so agents can search, create and edit pages, query databases, manage blocks and comments, and upload files in plain language. It is built for unattended automation with batched, idempotent writes, markdown round-tripping, retry on rate limits, and a low context footprint.4,610 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP-compatible clients to read and write Notion content—creating pages, querying databases, appending blocks, applying templates, commenting, and uploading files—using a token-based, headless setup. It exposes a compact three-tool interface that keeps context usage low while supporting batched, idempotent operations.4,610 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients such as Claude, Cursor and ChatGPT to read and write in Notion using a single token, covering search, page creation and editing, database queries, comments and file uploads through natural language. It also supports headless use in automation and CI, with batched, idempotent writes and compact context cost.4,610 npmMIT
- AlicenseNot gradedqualityAmaintenanceGives AI clients token-authenticated read/write access to Notion, letting them create and rewrite pages, query databases, append blocks, apply templates, comment, and upload files through natural language. It exposes 47 operations behind only three tools to keep context usage small, and runs headless with batched mutations, idempotency keys, and retry on rate limits.4,610 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents like Claude, Cursor, and VS Code to read and write Notion content through a token-authenticated connection, covering pages, databases, blocks, comments, and file uploads. It supports headless and CI use with context-efficient tooling, batched mutations, and idempotent retries.4,610 npmMIT
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.