Notion Large File Upload runs on your own machine — the client starts it, so there is no endpoint to ping. 326 installs a week from npm. Last commit 29 Oct 2026.
Upload local files up to 5 GB to Notion and attach them to pages, read from disk, not the chat.
What the code does
We read the source, 4 d ago · rules 995398eba69f
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
const file = path.join(dir, name);
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Nothing serious here today
Today is the operative word: we check Notion Large File Upload every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add notion-large-file-upload -e 'NOTION_KEY=<NOTION_KEY>' -e 'NOTION_UPLOAD_ALLOWED_DIRS=<NOTION_UPLOAD_ALLOWED_DIRS>' -- npx -y notion-large-file-upload-mcp{
"mcpServers": {
"notion-large-file-upload": {
"command": "npx",
"args": [
"-y",
"notion-large-file-upload-mcp"
],
"env": {
"NOTION_KEY": "<NOTION_KEY>",
"NOTION_UPLOAD_ALLOWED_DIRS": "<NOTION_UPLOAD_ALLOWED_DIRS>"
}
}
}
}[mcp_servers.notion-large-file-upload]
command = "npx"
args = ["-y", "notion-large-file-upload-mcp"]
env = { NOTION_KEY = "<NOTION_KEY>", NOTION_UPLOAD_ALLOWED_DIRS = "<NOTION_UPLOAD_ALLOWED_DIRS>" }{
"mcpServers": {
"notion-large-file-upload": {
"command": "npx",
"args": [
"-y",
"notion-large-file-upload-mcp"
],
"env": {
"NOTION_KEY": "<NOTION_KEY>",
"NOTION_UPLOAD_ALLOWED_DIRS": "<NOTION_UPLOAD_ALLOWED_DIRS>"
}
}
}
}{
"servers": {
"notion-large-file-upload": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"notion-large-file-upload-mcp"
],
"env": {
"NOTION_KEY": "<NOTION_KEY>",
"NOTION_UPLOAD_ALLOWED_DIRS": "<NOTION_UPLOAD_ALLOWED_DIRS>"
}
}
}
}Put your own values in place of
<NOTION_KEY> (Notion integration token. The integration needs access to the pages you attach files to), <NOTION_UPLOAD_ALLOWED_DIRS> (Folders the server may upload files from, separated by : (; on Windows). Uploads are refused until this is set).
The author’s registry entry marks them as required.
Alternatives to Notion Large File Upload
same job, measured the same wayNotion pages, databases and blocks via the REST API, as MCP tools.
Token-auth Notion MCP: pages, databases, blocks, comments, files. Runs headless in CI and agents.
Operate Notion with a single Markdown document — read, create, and update pages in one call.
Search, read and save your Linko notes and resources (AI knowledge base) from any AI chat.
Notion for AI agents — search, read pages/blocks, query databases, create pages.
Read-only MCP for the Eco game wiki: search, Markdown pages, and wiki_* lookups. No keys, no writes.
Your team's design feedback from Figma, Jira and Notion: ask, search, read, reply, mark done.
Search, read and write your Notion workspaces, with pages as Markdown and typed database queries.
Notion Large File Upload — questions
Answers built from our own checks of this server.