DROP File Transfer

Kirim file yang dipilih melalui agen AI, terima unggahan klien pada permintaan yang diaktifkan, dan bagikan hasil yang dipilih setelah disetujui. Token Bearer pribadi diperlukan.

Server MCP Terhosting

npx add-mcp 'https://drop.space/mcp'

Terpasang ke Claude Code, Codex, Cursor, dan lainnya

Dokumentasi

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 setup

How do I collect a client’s files and send back a list of what’s missing?

  1. First time connecting DROP? Open MCP setup above, sign in and choose Copy Prompt. Paste it into your own desktop agent and follow the setup instructions. If your receiver is already running, skip this step.
  2. Create a file request and enable Agent processing. In the private instructions, list what the client owes you, such as the copy and cover artwork. Give the client just the upload link. They can submit without signing in. Keep your receiver running so it can pick up the files.
  3. If the client sends the copy but forgets the cover, ask your agent to write a short list in missing.txt. Read it, then tell the agent, “Send only missing.txt.” Once the upload finishes, copy the result link into your reply to the client.

Set up a file request for your client

See which file appeared on the download link in our test

How do I send one file with an agent and keep the rest of the project private?

Your editor needs brief.txt. The same project folder also holds budget-notes.txt. In your desktop agent, select brief.txt and ask it to send that file through DROP. Wait for the upload to finish, then give your editor the download link. If a colleague’s agent needs the brief, your colleague can give it the same download link. Anyone holding that link can download the sent copy until it expires. Selecting the project folder sends its contents, including the budget notes.

What if you change the brief tomorrow? In our local test the first link still downloaded the original 26 bytes after we edited the file. Sending the revised brief produced a new link with the 25-byte copy. Give the editor that new link when they need the revision. The desktop agent’s own access to your computer is set in its host app.

Check the filenames and hashes from all three sends

Receive the client’s source CSV and return only the columns they need

The MCP directory lists DROP. How do I check my connection?

Look up space.drop/drop in the official MCP Registry. Version 1.0.0 lists https://drop.space/mcp as the Streamable HTTP endpoint. A connection without a personal credential receives HTTP 401 with a Bearer challenge.

In your own MCP client, configure the token from DROP and refresh the tool list. Look for drop_list_tasks. If a directory reports a failed health check, test the connection in your client first. A directory entry alone cannot confirm that your receiver is running.

Does a cloud agent need access to your laptop to deliver a file it just generated? If it already has the bytes, it can call drop_create_transfer, send each part with drop_upload_part, then call drop_complete_file and drop_complete_transfer to get the share link. To send a file selected on your computer or save a delivery to a local folder, use the desktop bridge.

We checked this with the official TypeScript SDK in an isolated copy of the released DROP server. The agent sent a 30-byte text file as editor/handoff.txt. A signed-out recipient downloaded the same 30 bytes, with a matching SHA-256. The linked script lets you check the tools your own remote client can see.

Run the read-only MCP check and inspect the sample file hashes

Connect 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.

I added DROP to Cursor or VS Code. Why do I get a 401?

If the install button only filled in the server URL, add the Authorization header from the example for your client. In Cursor, the example reads DROP_TOKEN from the environment. From the project directory, run agent mcp enable drop, then agent mcp list-tools drop. In our test with a temporary account, Cursor CLI listed 17 tools, including drop_list_tasks. An absent or incorrect token returned 401.

For a new VS Code Copilot setup, choose Copilot Global and use the example with mcpServers. It reads the token from the environment of the host running the session. If you maintain an older VS Code Local configuration, use the example with servers and inputs; the editor prompts for the token. The examples include both file formats and the results of our protocol checks.

Open the three config files and the Cursor test result

Find the right VS Code configuration file in Microsoft’s reference

How do I turn a client’s CSV shot list into JSON with an agent?

Our editor needs the shot number and caption. The studio’s CSV also has an internal_note column. Enable Agent processing on the request and run your connected receiver. The client uploads the original CSV through the request link. Your receiver gets the whole original, including the notes.

Tell the agent: “Convert shot and caption to JSON. Keep the shot number as text so 001 stays 001. Leave internal_note out.” Open the result and check the fields. When you are ready, tell it: “Send only client-shots.json.”

We tried this with three sample shots, including a Chinese caption and a line with quotation marks. A local Python tool did the conversion. The receiver reported the JSON and a review note. After the JSON was approved, the recipient link listed one file. Its 181 bytes matched the local result. The example below includes the original CSV, converter and downloaded JSON so you can repeat the check.

Download the shot list, converter and expected JSON (ZIP)

Check the returned filename and SHA-256 (JSON)

I sent a cut to two reviewers. How do I collect their feedback files?

  1. Send the cut out for review with a download link. In the same message, give reviewers a separate request link for their marked-up files. Include the cut version and the deadline for each link.
  2. Enable Agent processing on the request and keep your receiver running. Ask it to keep each submission in its own folder and list the feedback by batch. If both reviewers send review.txt, saving by batch preserves both originals. Ask reviewers to include their project reference if you need to match the notes to the brief.
  3. Read both sets of notes, select the revised cut and approve sending that file. Ask the agent for the download link once the upload finishes. Keep internal notes in your project folder.

Check both same-name originals from the two-browser test (JSON)

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.

How do I record which version the client was approved to receive?

Open the Agent task and note its status, instruction version and listed outputs. In your private project tracker, record who approved the handoff, when, the intended recipient and the exact file version. A full SHA-256 checksum lets a colleague verify the bytes even if two versions have the same filename.

For example, an editor could write “Approved by [name] at [time and time zone] for [client contact]. Send missing.txt only. SHA-256 [full checksum]. Keep internal-notes.txt in the project.” In the linked test, missing.txt was 10 bytes and its downloaded copy had the same checksum. The approval wording is an example you can copy into your own tracker.

If you change the file, have the reviewer approve the new version before sharing. Anyone holding a valid DROP link can download it. Keep any required sign-off and the recipient’s acknowledgment in the system your team uses for approvals.

Compare the approved sample and downloaded file checksums (JSON)

Read as Markdown · RSS