MCP protocol fails file upload support across 7 major services

A recent investigation into seven popular services revealed that none fully support file uploads through the Message Passing Protocol (MCP). While some services offer workarounds by bypassing the protocol, three services outright reject file uploads via MCP. The core issue stems from the MCP specification lacking a dedicated 'FileContent' type, with current options like 'EmbeddedResource' only pointing to URIs and not facilitating actual byte transfer. Although a proposed fix (SEP-1306) was introduced, it has been deferred, and work has moved to a dedicated working group, indicating no immediate solution for file uploads within the protocol. AI

IMPACT Limits the ability of AI agents to perform file-based tasks, hindering automation in workflows requiring document handling.

RANK_REASON Analysis of a protocol's limitations and proposed fixes. [lever_c_demoted from research: ic=1 ai=0.7]

Read on dev.to — MCP tag →

• Anthropic
• Confluence
• Freee
• GitHub
• GitHub Discussion #1197
• Gmail
• Google Drive
• Jira
• MCP
• Notion
• SEP-1306
• SEP-2356
• SEP-2631
• Slack

• product
• infra

AI-generated summary · Google Gemini · from 1 sources. How we write summaries →