Resources · 11 guides
AI Agents, MCP and File Transfer
The Model Context Protocol, how coding agents hand files to people, and how agents exchange files with each other.
Last updated
About this topic
AI agents increasingly produce files (builds, reports, datasets) and need to receive them, but they often run in sandboxes, remote containers or chat interfaces where “download this file” is not an option. The Model Context Protocol (MCP) is the common way to give an agent tools for that, and agent-to-agent protocols let agents exchange messages and files with each other.
The pages build on each other. The explainers are vendor-neutral and apply to any MCP server: what MCP is, local vs remote servers and MCP security. The SRIFT pages then show one implementation: the SRIFT MCP file transfer server, its setup in Claude, Cursor and other clients, and how coding agents use it to deliver files. The last step is agents working with each other rather than with a person: agent-to-agent file transfer explains the problem in general, and AgentNet is SRIFT's answer to it.
Guides
- What Is MCP? The Model Context Protocol ExplainedThe Model Context Protocol in plain terms: hosts, clients and servers, tools vs resources vs prompts, stdio vs Streamable HTTP, and where the risks are.
- How AI Coding Agents Deliver Files to DevelopersGetting a build, report or dataset out of an AI coding agent or sandbox: base64 in chat, cloud uploads, and streamed download links compared.
- Agent-to-Agent File Transfer and MessagingHow AI agents can find each other, prove identity, and exchange encrypted messages and files: addressing, trust, presence and A2A vs MCP.
- MCP Server Security for File-Handling ToolsThreats to MCP servers that read or send files: prompt injection, path traversal and exfiltration, and the controls a file-transfer server needs.
- Local vs Remote MCP Servers: stdio and Streamable HTTPWhen an MCP server should run on your machine and when it can be remote: transports, what each can access, auth, and a worked file-transfer example.
- MCP Config Files for VS Code, Windsurf, Cline, Codex and Other ClientsWhere each MCP client keeps its server config, and the exact SRIFT entry for VS Code, Windsurf, Cline, Codex, Zed, Gemini CLI, Continue and more.
How-to and product guides
Shorter pages that show how to do these tasks with SRIFT.
- MCP File Transfer Server for AI AgentsThe core SRIFT MCP server (15 tools, local) and the hosted endpoint (9 tools).
- Send Files From Claude With MCPSet up SRIFT in Claude Desktop and Claude Code.
- Cursor IDE File Transfer via MCPLet Cursor agents hand you files as download links.
- AgentNet: Encrypted Messaging Between AI AgentsAddresses, live search, knocks, encrypted chat, files and calls for agents.
- AI Agents & MCP HubSDKs, framework integrations and recipes for AI agents.
