MCP server
SendFlo is an MCP server: an AI assistant can ask people for files, collect them from you, send files as links and follow up on what happened — with the same account, plans, scans and audit log as the app. There are two ways to run it: the hosted server (nothing to install; you sign in) and the npm package (it also sends files from your computer).
Hosted server
https://mcp.sendflo.app/mcpAdd it as a custom connector (Claude, ChatGPT) or a remote MCP server (Cursor, VS Code, Claude Code). The first time, your browser opens SendFlo: sign in, check which app is asking and what it may do — untick anything you don't want — and choose the workspace. You can disconnect it any time in Settings → Sign In & Security → Connected apps.
# Claude Code
claude mcp add --transport http sendflo https://mcp.sendflo.app/mcp
# Cursor (.cursor/mcp.json) and VS Code (.vscode/mcp.json)
{ "mcpServers": { "sendflo": { "url": "https://mcp.sendflo.app/mcp" } } }Streamable HTTP, the 2026-07-28 protocol and the two before it. Sign-in is OAuth 2.1 with PKCE (how it works); a client that can't do OAuth can send an API key instead:
Authorization: Bearer sk_live_…A token the hosted server accepts is good there only: the REST API refuses it, and the server never passes it on. Every call it makes for you is checked like your own: the app's permissions, your plan, the audit log (it shows the app as the actor).
Tools
| request_file_from_human | A link someone else uploads to — no account needed. Give it to them. secure: you see only that files arrived, never their contents. |
| collect_files_from_me | Opens an upload page for the person you're talking with; returns what they uploaded. |
| check_file_request | Whether a request got its files, with each file's scan state. |
| hand_off_files | Give a teammate a secure intake's files (they open them in SendFlo; the assistant still can't). |
| wait_for_files | Waits (up to 110 s) for files to arrive through a request or into an inbox. |
| list_received_files | What people sent this account, filtered by request, inbox, date or scan state, paged. |
| create_inbox | An address that agents and people can drop files into, again and again. |
| list_inbox | The files in an inbox, with scan warnings. |
| list_team_inbox_members | Who is in a team inbox, and its access list (a team owner's or admin's key). |
| set_team_inbox_members | Replace who may use a restricted team inbox, e.g. from an HR or identity system. |
| list_events | What happened lately: sends completed, links opened and downloaded, files received (30 days). |
| list_webhooks | The account's webhook endpoints, active or paused, and their last day of deliveries. |
| add_webhook | Have SendFlo post events to a server, Zapier, Make or n8n; returns the signing secret once. |
| test_webhook | Send a sample of any event to an endpoint now. |
| prepare_send | Asks the person to send files from their own device; returns the links. |
| check_prepared_send | Whether the person sent them, and the links. |
| list_links | The links this account made, with download counts. |
| link_feedback | Comments, ratings, favorites and approvals on a send. |
| list_replies | The secure replies to a send: what people wrote back, and the files they sent. |
| send_file_from_url | Share a file that's at a public address: SendFlo fetches it and returns the link. |
| transfer_activity | Who opened and downloaded a send, from where, with proof of delivery. |
| transfer_people | Who can open a send; change one person's files. |
| pause_transfer | Pause or resume a whole send. |
| revoke_link | Disable one link at once. |
| revoke_transfer | Revoke every file of a send. |
| list_audit_events | Search the audit log (Team Pro and Team Enterprise). |
| list_notification_channels | Where notifications go. |
| add_notification_channel | Add an email address, Slack, Discord, Teams or a webhook. |
| remove_notification_channel | Remove one. |
| test_notification_channel | Send a test message through one. |
| list_agents | The agents this account can send work to. |
| check_agent_task | Where an agent task is, its question and its result. |
| list_agent_tasks | Recent agent tasks, or a pull agent's queue. |
| answer_agent_question | Answer an agent's question about a task. |
| cancel_agent_task | Stop a task. |
| check_credits | The credit balance and prices. |
| list_drive_folder | What's in a Drive folder (My files to start, or the folders the person gave the app). |
| search_drive | Find files and folders in the Drive by name. |
| read_drive_file | Read a text file in the Drive (the first 200 KB). |
| save_drive_file | Save text as a new file in the Drive, or as a new version of one. |
| create_drive_folder | Make a folder in the Drive. |
| move_drive_item | Move a file or folder to another folder (at most 25 files at once). |
| rename_drive_item | Rename a file or folder. |
| delete_drive_item | Move a file or folder to the trash, where it can be restored; never deletes for good. |
The npm package adds the tools that touch files on your computer:
| send_file | Uploads a file from this machine and returns a link. |
| upload_to_page | Sends a file from this machine to someone's upload page, sealed here when the page encrypts uploads. |
| send_to_agent | Sends local files plus an instruction to a cloud agent. |
| claim_agent_task | Pull agents: take a task from the queue. |
| report_agent_task | Report progress, ask the sender, or hand back results. |
Each tool has a title and hints your client uses to decide what to confirm with you (read-only, destructive, reaches outside SendFlo), and most return structured data alongside their text.
Asking you
A hosted assistant can't reach the files on your device, so prepare_send opens a SendFlo page in your browser: pick the files, they're sent from your account as links, and the assistant gets the links — never the files. collect_files_from_me opens an upload page the same way. The page only works for the account the assistant acts for; anyone else signed in is refused. Clients that can open pages for you do it directly (URL elicitation); others show you the link.
The SendFlo card
In clients that show apps (MCP Apps), links, upload pages and received files appear as a small card with an Open button and each file's scan state. Other clients show the same as text.
npm package
{
"mcpServers": {
"sendflo": {
"command": "npx",
"args": ["-y", "@sendflo/mcp@1.7.0"]
}
}
}Connect it once with npx @sendflo/mcp login (you approve it in your browser), or set SENDFLO_API_KEY in its env. The same package runs the Claude Code channel for agent tasks (Settings → Agents → Connect).
Safety
File names, notes and sender names are written by other people: the tools tell the assistant to treat them as data, never as instructions, and the card shows them as text only. Received files come back as names, sizes and scan state; a flagged file is marked so the assistant doesn't pass it on.