WETRANSFER FOR AI AGENTS

Let your AI agent send files through WeTransfer.

Add the WeTransfer MCP to your coding agent and send files the same way you work — from your terminal, straight to a WeTransfer link.

Connect your agent
wetransfer / mcpMCP
Endpointhttps://mcp-server.wetransfer.com/mcp

Cursor example

{
  "mcpServers": {
    "wetransfer": {
      "url": "https://mcp-server.wetransfer.com/mcp"
    }
  }
}

WHAT IS WETRANSFER MCP

Send anything, from any agent.

The WeTransfer MCP server lets clients — Claude Code, OpenCode, Cursor, Gemini CLI, JetBrains IDEs and others — send files through your WeTransfer account. Add the endpoint, sign in once with WeTransfer OAuth, and your agent can upload files from your machine and hand you back a link.

WHY YOU'LL LIKE IT

Built for the way you already work

One endpoint, every client

Point your client at a single URL — Claude Code, OpenCode, Cursor, Gemini CLI and more — and it can send files through WeTransfer.

Straight from your machine

Built for people who work locally: the agent reads a file by its absolute path and uploads it from your computer, with no re-uploading by hand.

Secure by design

Sign-in runs through WeTransfer OAuth in your browser. There are no API tokens to create, paste, or leak — the agent acts as you.

GET SET UP IN MINUTES

One endpoint. Any client.

Most clients add MCP servers with a new entry in a JSON or TOML config file. Add the endpoint, sign in with OAuth, and you are set.

  1. 1Add the endpoint to your client's MCP configuration.
  2. 2Sign in with WeTransfer OAuth in the browser that opens.
  3. 3Ask your agent to send a file by its absolute path, and it returns a link.
cursor / mcp.json

Global: ~/.cursor/mcp.json · Project: .cursor/mcp.json

{
  "mcpServers": {
    "wetransfer": {
      "url": "https://mcp-server.wetransfer.com/mcp"
    }
  }
}

If your client isn't listed here, the same JSON pattern usually works — check its docs for where the MCP config file lives.

FOR YOUR AGENT

A brief you can hand your agent

Paste this into your agent. It covers the access it needs, how to sign in, and the exact flow to follow.

Copy into your agent's instructions

Setup requirements:
- Use an MCP-capable client with local filesystem, terminal, and outbound network access.
- Add the endpoint above to the client MCP configuration.
- Complete WeTransfer OAuth in the browser when prompted. Never request or paste an API token.

To send a local file:
1. Receive an absolute path from the user.
2. Request upload URLs from the WeTransfer MCP.
3. PUT every complete file using every header returned by the MCP.
4. Call the completion tool.
5. Return the final WeTransfer link to the user.

GOOD TO KNOW

Good to know, whatever client you use

  • Local uploads need the right agent

    Uploading from disk requires a client that can read the local filesystem and send HTTP PUT requests. Allow filesystem, terminal, and outbound network access when it asks.

  • No API tokens

    Authentication opens in your browser through WeTransfer OAuth. Do not manually create or paste an API token.

  • In-browser chats work differently

    Claude.ai, ChatGPT on the web, and similar chat surfaces cannot reach files on your computer. There, use the regular send_files tool.

  • How to ask your agent to send a file

    Ask the agent to send a file by its absolute path. It requests an upload URL, PUTs the whole file with the headers it gets back, then calls the completion tool.

FAQs

All your questions answered.

Connect your agent to WeTransfer

Connect your agent