
Beecargo
io.github.BeecargoPublished by GitHub account Beecargov0.1.0Updated Oct 24, 2026
Publish a file from an agent and get a durable beecargo.net/d/{shortId} share link.
Overview
Beecargo lets an assistant publish files to Beecargo hosting and hand back a durable share link, with optional folders, paid shares and Stripe checkout.
- What you can do
- Register an agent and mint a bootstrap API key after a proof-of-work step
- Upload files by public URL, small base64 or local path, and poll async upload jobs
- Manage shares: visibility, price, retention, unlock protection and handoff messages
- List, inspect and delete owned files, and create or list folders
- Get signed download URLs, claim anonymous uploads, and mint or claim paid-share checkouts
- Search the server's own tools by keyword
- When to use it
- Useful when an assistant needs to hand a generated file or artifact to a person or another agent as a stable share link, or when you want to sell or gate access to a file through Beecargo. Not needed if you only work with local files or already have another hosting service.
- Requirements
- Remote endpoint at mcp.beecargo.net over streamable HTTP; OAuth is declared as required, and the README also describes a guest bootstrap path and anonymous uploads. An API key (bc_ prefix) is optional for some tools and required for others; a Pro key is needed for higher limits. No environment variables or headers are declared in the manifest.
Installation
In SourceWeft
- Open Beecargo in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.Beecargo%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"beecargo": {
"type": "http",
"url": "https://mcp.beecargo.net/mcp"
}
}
}README
Beecargo MCP
Model Context Protocol server for the Beecargo file hosting API.
Portable marketplace packaging (Agent Plugins 1.0 + Cursor manifest) lives in ../agent-plugin.
Fastest path (agents)
Publish a durable share link with no human dashboard login:
- Add hosted MCP with no headers:
https://mcp.beecargo.net/mcp(full tools; seeexamples/cursor-http.mcp.json). If/mcprequires auth, usehttps://mcp.beecargo.net/mcp/guestfor bootstrap-only tools. - Call
beecargo_register_agent→ solves a short PoW, returns bootstrapbc_*(10GB / 100rpm; session adopts the key). - Call
beecargo_uploadwith a public HTTPSurl→ hand offhttps://beecargo.net/d/{shortId}(always the full share URL). Multi-file handoff:openShare: trueon the first file, thenshareShortIdon later uploads (same link, one unlock). - Optional:
beecargo_update_share_settingswithprotect: true(+handoffMessage) onfileIdor ShipmentshortId→ returnunlockCodeandhandoffUrl(/h/…) on a private channel.
For production agents (100GB included concurrent storage / 1000rpm / high remote/hr): mint a Pro-tier key via dashboard POST /api-keys/agent (Pro required) or operator POST /agent/api-keys.
Skip registration for ephemeral uploads: beecargo_upload works anonymously (stricter limits; save deletionToken).
Tools
Advanced
Detailed guides: upload, upload status, run artifacts, upload delegation, folders, share settings, seller payouts, and buy a priced share.
Stdio (local)
Optional: BEECARGO_API_KEY=bc_… in env. After beecargo_register_agent, the stdio session adopts the new key automatically.
See examples/cursor-stdio.mcp.json.
HTTP (hosted)
https://mcp.beecargo.net/mcp (full tools when authenticated). Guest bootstrap: https://mcp.beecargo.net/mcp/guest. See examples/cursor-http.mcp.json.
Existing key: examples/cursor-http-with-key.mcp.json.
Env: see .env.example. Highlights:
BEECARGO_API_URL: defaulthttps://api.beecargo.netBEECARGO_API_FETCH_TIMEOUT_MS: raise for large sync remotes (default guidance: 300000)BEECARGO_MCP_REQUIRE_AUTH: settrueto require transport bearer orbc_*on/mcp(default: open bootstrap, rate-limited)BEECARGO_MCP_BEARER_TOKEN: optional shared transport secret whenREQUIRE_AUTH=trueBEECARGO_MERCHANT_OAUTH_ENABLED: publish OAuth resource metadata and enable Connect with Beecargo (requires matchingINTERNAL_API_KEYon API + MCP)
Official MCP Registry
server.json is the Official MCP Registry manifest for io.github.Beecargo/mcp (schema 2025-12-11). The hosted remote is https://mcp.beecargo.net/mcp. Discovery copies also live at /.well-known/mcp/server.json on this host and on https://beecargo.net.
This file does not mean the server is already listed in the registry.
CLI (local scripts)
Use the dedicated package @beecargo/cli:
From the monorepo: pnpm cli upload ./artifact.zip. Publish flags (--ttl, --protect, …) match MCP beecargo_upload. share --price-cents / download --purchase-token match MCP share-settings and retrieve.
Parity with lomi MCP
Publish
Scope is @beecargo. First publish is manual with --otp. After that, set Trusted Publisher on the npm package to GitHub Beecargo/mcp workflow publish.yml. Then bump the patch in package.json and push main.
Source: README.md at commit be9459a
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
