Send, receive and process files with an AI agent via DROP MCP
DROP gives a compatible AI agent a way to send and receive files through MCP. DROP handles delivery; your Agent can use its own tools to organize, summarize or convert the received files.
Open MCP setupConnect from a desktop agent or a remote MCP client
To send files from your computer or download deliveries into a folder you choose, open the MCP setup on DROP and follow the prompt to install the desktop bridge in your client.
If you are building an integration that already handles file uploads, connect a client that supports Streamable HTTP and custom headers to https://drop.space/mcp. Set the Authorization header to Bearer, a space, then your personal token from the MCP setup prompt. If you already installed the desktop bridge, reuse its saved token. Issuing a new token revokes the old one.
Example: receive a client’s sample and return a summary
- Sign in to DROP, open MCP from the plus menu and follow the setup prompt in your compatible client. Create a request, enable Agent processing for that request and add private instructions, for example: “List the files and summarize the attached brief.”
- Send the request link to the client. They upload without signing in. After the upload completes, the authorized Agent can claim the task and download the originals to the directory you selected.
- Ask the Agent to process the files with its own tools, then review the result. Choose which result file to send and explicitly authorize the upload. DROP returns a share link after that upload completes.
Does the Agent run when I close my computer?
Automatic pickup requires a running receiver. DROP queues eligible deliveries; it does not wake a closed client or run a model on its behalf. The request owner can still open the private delivery in a browser while the files are available.
Who can share the originals or results?
Incoming files and local outputs do not become public when a task is processed. Sharing a result requires your explicit authorization and applies only to the files you select. Anyone who holds the resulting valid link can download those files.
A two-step example you can try with sample files
For the collection task, try: “When files arrive for the Sample review request, use my selected folder, list the filenames and flag anything missing. Prepare a review checklist. Wait for my approval before sending it.” After reviewing the checklist, give a separate instruction: “Send only review-checklist.pdf through DROP and show me the link when the upload finishes.”
What to keep when a handoff needs an approval record
Open the Agent task to review its status, instruction version and listed outputs. Before asking it to send a file, record the recipient, the approved filename and version, and the approval in your project tracker. Send the finished link through your usual channel and save the recipient’s acknowledgment there if you need proof of receipt.
Official sources
Documentation reviewed 2026-11-13. Check the provider for current terms.