Works with Claude, ChatGPT, Cursor & VS Code

MCP file upload for AI agentsYour AI can read anything.Except the file you have.

The Model Context Protocol has no way to move files. MCP File Upload gives Claude, ChatGPT, Cursor and VS Code a signed, single-use upload URL — you drop the file (or your agent PUTs it), and your MCP tools get it. No base64, no token bills, no 4 MB walls.

Get 20 files free See how it works

No credit card. Connect in under a minute.

Analyze my Q3 sales export — it's 38 MB.

request_upload

mcpupload.app/u/7f3a… · expires in 30 min
Done ✓

check_upload

q3-sales.csv · text/csv · 38.2 MB
Got it. Revenue is up 18% QoQ — the jump comes from 3 accounts in LATAM. Want the breakdown?

The problem

Agents got hands. They still can't take a file from you.

Today the only path is stuffing the whole file into a tool argument as base64 — generated token by token by the model. It's slow, expensive, and it breaks on anything bigger than a screenshot.

120K

output tokens to base64 a single 126 KB image through a tool call

4 MiB

request limit in the official MCP Python SDK — then HTTP 413

0

standard ways for a file you attach in chat to reach an MCP tool

How it works

Three steps. Zero base64.

  1. 01

    Connect once

    Add MCP File Upload as a connector in Claude, ChatGPT, Cursor or VS Code and sign in. Takes a minute.

  2. 02

    Your agent asks

    When it needs a file, it calls request_upload and hands you a signed link that works once and expires in 30 minutes.

  3. 03

    You drop, it reads

    Drag the file in. The agent calls check_upload and gets the name, size, type and a private download URL.

The file layer MCP forgot to ship.

Single-use links

Each link accepts exactly one file, then it's dead. Replays are rejected.

Short-lived by design

Links expire after 30 minutes. Download URLs after about an hour.

Up to 100 MB

Spreadsheets, PDFs, videos, archives — straight to storage, never through the model.

Private by default

Files are tied to your account. Only you and your connected assistant can read them.

Zero tokens burned

The file never enters the context window. Your agent only sees a short ticket id.

Spec-aligned

Built around the upcoming MCP file-transfer proposal (SEP-2631), so you're ready when clients catch up.

Pricing

Simple plans for MCP file uploads

Start free with 20 files total. Upgrade when your assistants move real work. Cancel anytime.

Starter

For individuals trying it on real work

$9.99 / month

  • 500 files / month
  • 20 GB storage
  • 10 GB downloads / month
  • Up to 100 MB per file
Choose Starter
Recommended

Pro

For daily use with Claude, ChatGPT & Cursor

$19.99 / month

  • 2,000 files / month
  • 50 GB storage
  • 20 GB downloads / month
  • Up to 100 MB per file
Get Pro

Business

For teams and agents moving files all day

$49.99 / month

  • 10,000 files / month
  • 150 GB storage
  • 40 GB downloads / month
  • Up to 100 MB per file
Choose Business

Not ready? Start free — 20 files total, 2 GB storage, 2 GB downloads / month. No credit card.

Questions

Which assistants does it work with?

Any client that supports remote MCP connectors: Claude (web, desktop, Code), ChatGPT, Cursor, VS Code and more.

Does the file go through the AI model?

No. It goes straight from your browser to encrypted storage. The model only sees a short ticket id and, when it needs the content, a temporary download URL.

Who can see my files?

Only you and the assistants you connect with your account. Upload links work once and expire after 30 minutes.

How much does it cost?

Free covers 20 files. Starter is $9.99/month (500 files, 20 GB), Pro $19.99/month (2,000 files, 50 GB, recommended) and Business $49.99/month (10,000 files, 150 GB). Cancel anytime.

What about the official MCP file spec?

The protocol's file-transfer proposal (SEP-2631) is still a draft. MCP File Upload works today, and is built to follow the spec once clients ship it.