Create a key, find tools, send files, and return their share links.
Hosted MCP is the simplest option for agents. Use the API when you prefer direct HTTP calls. Use the CLI for local scripts and files on disk.
Connect to https://mcp.beecargo.net/mcp/guest without headers, call beecargo_upload with a public url, and return https://beecargo.net/d/{shortId} immediately (do not wait on the safety check for human handoff). Register only when you need owned storage, list, or claim.
Tool
Authentication
For a fast one-shot handoff, connect to https://mcp.beecargo.net/mcp/guest with no headers (rate-limited, typically under 30 seconds to a share link). For lasting access, call beecargo_register_agent, or send an existing API key as Authorization: Bearer bc_… or x-beecargo-api-key. Keep the key secret.
Use Add to Cursor or Add to Grok Bot, or add https://mcp.beecargo.net/mcp with no headers in Claude, OpenCode, or Codex. Complete Connect with Beecargo in the browser. The client sends the OAuth access token for you. Clients without OAuth can still use an API key.
Usage notes
beecargo_uploadTool
Authentication
No API key required. About 5 registrations per hour per client IP. This tool solves a short proof-of-work for you.
Parameters
Usage notes
bc_ and is shown only once. Store it if you need it outside this session.POST /agent/register/challenge, solve the PoW, then POST /agent/registerCommand
Authentication
No API key required.
Usage notes
--save to store the key in ~/.config/beecargo/config.json.beecargo_register_agent and POST /agent/register.Prefer MCP beecargo_register_agent, or call POST /agent/register/challenge, solve the PoW, then POST /agent/register. Send the key as a Bearer token with file requests.
Endpoint
Request examples
# Prefer MCP beecargo_register_agent or the beecargo CLI (they solve PoW for you).
# Raw REST: challenge → solve SHA-256(challenge_id:nonce) leading-zero bits → register.
curl -X POST https://api.beecargo.net/agent/register/challenge
# then POST https://api.beecargo.net/agent/register with {"label":"my-agent","challenge_id":"…","nonce":"…"}From a terminal: npx --yes github:Beecargo/cli register --save, then upload ./file --json or remote <url> --json. Return the printed https://beecargo.net/d/{shortId}. Hosted MCP cannot read local disk; the CLI (or stdio MCP path) can.
Tool
Authentication
No API key required.
Parameters
Usage notes
Use beecargo_search_tools to find the right tool for large files, folders, sharing, or downloads.
https://mcp.beecargo.net/mcp/guest with no headers, then beecargo_upload with a public url. OAuth-capable clients can use /mcp to sign in. Call beecargo_register_agent only when you need owned storage, list, or claim.beecargo_register_agent succeeds, this session keeps the API key so beecargo_list_files and beecargo_claim_file work without pasting the key again.https://mcp.beecargo.net/mcp. That is the supported way to connect.challenge_idnoncebeecargo_upload for uploads on your agent account.Usage notes
POST /agent/register/challenge, solve the proof-of-work, then POST /agent/register with challenge_id and nonce. Limited to about 5 registrations per hour per IP. Official MCP/CLI solve the challenge for you.bc_ and is shown only once. The response includes the trust tier. MCP beecargo_register_agent keeps the key in the session for you.Endpoint
Usage notes
beecargo_register_agent for IDE agents on mcp.beecargo.net/docs/mcp/register for the MCP tool referenceEndpoint