file.rocksdocs
Menu

One-click storage API for agents·View as Markdown

MCP overview

file.rocks ships a production Model Context Protocol server so agents can list buckets, search files, and ask the bucket agent without hand-rolling HTTP.

Endpoint

https://www.file.rocks/api/mcp

Streamable HTTP (stateless). Authenticate every request with your API key.

Security model

  • Bearer API keys only this pass (no OAuth / CIMD client flow yet)
  • Same dogfood gate as REST intelligence APIs
  • Per-tool scope checks identical to /api/v1
  • Optional bucketIds allowlist on the key

Never put a live key in a public repo. Prefer client secret stores / env vars.

Why MCP

Agents get typed tools (list_files, ask_agent, …) instead of scraping docs for curl. Docs are also exposed as MCP resources so clients can pull markdown context.

Upload

Agents must use MCP for upload. After presign_upload and PUT, call complete_upload (files:upload). Do not call REST upload-complete (Cloudflare may return 1010). Do not request files:write to register a file.

To display a file, use file.url or presign_view. To save a file, use presign_download (attachment).

→ Upload, display, download

Next

  1. Install — Cursor / Claude / generic
  2. Tools — catalog
  3. Upload flow — presign, PUT, complete, view vs download
  4. Auth & scopes

REST remains available: API overview.

MCP overview · file.rocks docs