MCP servers that can share a file

3 verified servers expose a tool that can create a shareable link for a file

Getting a file to someone usually means a link, not an attachment. Sharing a file creates a URL anyone with it can open, so an agent can hand off a document, an export, or an asset without emailing the bytes around.

These verified servers let an agent create a shareable link for a file.

Top pick

Box

Box

Official

Box's hosted MCP server lets agents search, read, organize, and run Box AI over your enterprise content via OAuth.

file-storage
Tool:
  • add_file_shared_link

Box's add_file_shared_link creates or updates a shared link for a file, the URL an agent hands off instead of the bytes.

Pick 2

Dropbox

Dropbox

Official

Dropbox's hosted MCP server lets agents search, read, organize, and share files in your Dropbox over OAuth.

file-storage
Tool:
  • CreateSharedLink

On Dropbox, CreateSharedLink makes a link for a file or folder, the way an agent shares storage content by URL.

Pick 3

Google Drive (Workspace MCP)

taylorwilsdon

Community

The Google Workspace MCP, scoped to Drive, lets an agent search, read, create, and share your Google Drive files over OAuth.

file-storage
Tool:
  • get_drive_shareable_link

For a Drive file, get_drive_shareable_link returns a shareable URL an agent can drop into a message or doc.

What to know

A shared link is the standard way to hand off a file from cloud storage: the file stays where it is, and the link is what travels. The three servers do the same thing on their store, Box creates or updates a shared link for a file, Dropbox a link for a file or folder, Google Drive a shareable link for a Drive file. The link usually carries access rules, anyone with it or restricted, which matters because a too-open link is a quiet data leak. From the call an agent gets the URL to drop into a message or a doc.

A share link an agent creates is a standing grant of access, so it is worth remembering what it shared and with what scope. An agent that re-shares the same file generates duplicate links, and one that forgets a link it made cannot revoke it later. Holding what was shared keeps access auditable.

Questions

Who can open a shared link?
It depends on the access rules the link carries, typically anyone with the link, or restricted to specific people. That setting matters: a link scoped to anyone is convenient but a quiet way to leak a file, so an agent should match the scope to how sensitive the content is.
Does sharing move or copy the file?
Neither. The file stays where it is in storage; the link is just a URL pointing at it. That is the advantage over attaching, the bytes do not travel, and revoking the link cuts access without touching the file itself.