Published:

File uploads in MCP: a draft extension keeps PDFs and exports out of the model

In short: On 10 November 2026 the MCP project presented a draft extension, io.modelcontextprotocol/files, that lets AI apps send files to MCP tools and receive files back without the bytes passing through the model. The server approves the metadata first; the upload follows separately over HTTPS. It is experimental, with stable planned before the end of 2026.

Files are one of MCP's practical gaps. If you want an MCP tool to process a contract, a batch of invoices or a data export, today you mostly rely on workarounds: encoding the file as base64 text inside the tool call, or building your own upload link outside the protocol. In a blog post on 10 November, Den Delimarsky (MCP lead maintainer) and Wil St. Charles (Google) describe a standard approach. The File Uploads working group, set up in April with members from Anthropic and OpenAI, added downloads to its scope on 21 October.

How does the files extension work?

The extension works with protocol revision 2026-07-28 and later, the stateless version of the specification. The flow in five steps:

How mature is the extension?

Not mature enough for production. The experimental-ext-file-uploads repository says so itself: the extension is not part of the MCP specification, has not been proposed as a SEP, and breaking changes should be expected. There is no reference implementation yet. The blog calls the definition "rough" and expects a stable version before the end of 2026.

Outside the project, people are already building on it. The holon-sh Python SDK merged a client and server prototype on 10 November, noting that the interfaces follow the drafts and may change. In the nmi-agro GitHub organisation, an issue opened the same day proposes importing lab reports (PDF) and Dutch government (RVO) field shapefiles through an MCP server. That proposal deliberately starts with a temporary upload link and plans to add the extension later, because it has not been approved yet.

Separately, the maintainers announced a fixed six-month release cycle on 11 November. The next specification version is scheduled for 30 March 2027.

Which risks remain open?

The blog and an independent analysis on dev.to flag the same issues:

Our advice

(1) If you are building an MCP server that handles documents now, choose a simple interim route (a temporary single-use upload link, or a reference to a file already in your own storage) and design the interface so the extension can be added later as a second route. Base64 in the tool call only suits small files. (2) For every MCP integration that handles files, record in your data processing agreements where those files end up, how long they are kept and who operates the storage; the upload bypasses the model but lands in the server vendor's storage. See MCP and EU regulation. (3) When adopting the extension, enforce an allowlist of upload origins, even if the specification ends up not requiring one. More on risks: MCP security.

The bigger picture: MCP is moving from text-in, text-out to real business processes: quotes, claims files, exports. Keeping the file out of the model is a win for both cost and data protection. But it shifts the question to the storage layer: anyone building their own MCP server will need to design upload storage, retention and deletion alongside tools and authorisation.

Sources

Frequently asked questions

Can I use the MCP files extension in production yet?

Not advisable yet. According to its own repository, io.modelcontextprotocol/files is experimental, not part of the MCP specification and not yet proposed as a SEP; breaking changes are expected. There is no reference implementation. The maintainers aim for a stable version before the end of 2026. Prototyping is fine.

Does an uploaded file pass through the AI model?

No, that is the point. The client (the AI app) fills the file argument, not the model. Small files travel inline in the tool call; larger ones are sent separately over HTTPS to an upload target provided by the server. The bytes stay out of the model context and out of JSON-RPC messages.

What does a server need to support the extension?

The extension works with protocol revision 2026-07-28 and later. The server advertises it in its server/discover response, marks file arguments with x-mcp-file in the input schema and, for large files, returns an upload_required result with upload targets and a tamper-protected requestState.

Last updated: