Deliver files with AI - FileBolt

Connect your AI

Add this URL to a client that supports remote MCP using Streamable HTTP. Authentication: none. Start with get_limits and reuse its private client_token.

Protocol integration is tested with the official MCP TypeScript client. Other clients must support remote MCP and custom tools; platform-specific compatibility is not implied.

From AI to a download link

Submit the files you want to share. FileBolt processes the upload in the background. The AI checks progress and gives you a link when every file is ready.

get_limits

Read current limits and obtain an anonymous client token.

create_transfer

Import direct HTTPS file URLs into one transfer.

upload_text

Create a UTF-8 text file, including Markdown, CSV, JSON or code.

get_transfer_status

Check progress and retrieve the browser link when complete.

cancel_transfer

Cancel an unfinished upload and remove its files.

{
  "name": "upload_text",
  "arguments": {
    "client_token": "<get_limits.client_token>",
    "request_id": "<UUID>",
    "name": "report.md",
    "text": "# Report\n..."
  }
}

Limits and supported sources

Free: up to 10 GB total per transfer, 20 files and 3 days of retention from task creation. Text submissions are limited to 256 KiB of UTF-8 data. Tasks time out after 6 hours.

URL import supports GitHub file hosts, Azure Blob, Google Cloud Storage, Amazon S3, Cloudflare R2 and supported oaiusercontent hosts. Use a direct public or signed HTTPS URL, not a login page or private sandbox path. get_limits lists the exact hosts. Sources must expose their size; files over 4 MiB also require byte ranges and a strong ETag.

Automated uploads share a daily service budget and have client, network and concurrency limits. URL jobs temporarily reserve available capacity up to 10 GB; unused capacity is released after cleanup. get_limits reports availability. Keep the client token and task token private; reuse the same request UUID only when retrying the same upload.

Privacy of AI uploads

Browser uploads use client-side end-to-end encryption. AI uploads use a different path: FileBolt receives and processes plaintext, then encrypts it for storage. AI uploads are not end-to-end encrypted.

Source URLs and submitted text are removed from task storage after completion or cleanup. Task credentials and decryption keys are encrypted at rest and removed at transfer expiry. Operational logs contain event counts, byte totals and error codes, not source URLs, file names, text or keys.

Downloads happen on the regular FileBolt page. There is no MCP download tool or file-content resource. Anyone with the complete share link can access the files; this is not a restriction against browser automation.