MCP server
Connect Cursor or Claude Desktop to Bopbee upload projects via the official MCP server.
The Bopbee MCP server wraps the public REST API as tools. It uses the same team API keys and plan limits as the REST API.
Upload projects only: GitHub deploys are not exposed.
HTTP (recommended for hosted use)
Endpoint:
https://mcp.bopbee.com/mcpSend your team API key:
Authorization: Bearer bb_live_your_keyHealth check (no auth): GET https://mcp.bopbee.com/health
Stdio (Cursor / Claude Desktop)
Add to your MCP config:
{
"mcpServers": {
"bopbee": {
"command": "bun",
"args": ["run", "/path/to/bopbee-mcp/src/index.ts"],
"env": {
"BOPBEE_API_KEY": "bb_live_your_key",
"BOPBEE_API_BASE_URL": "https://api.bopbee.com/v1"
}
}
}
}Tools
| Tool | Description |
|---|---|
bopbee_get_account | Team, plan, quotas |
bopbee_list_projects | List upload projects (limit, cursor) |
bopbee_get_project | Project details |
bopbee_create_project | Create upload project |
bopbee_update_project | Rename or pause/resume |
bopbee_delete_project | Delete project |
bopbee_list_deployments | Deployment history (limit) |
bopbee_trigger_deployment | Redeploy (optional upload_version) |
bopbee_get_deployment | One deployment by ID |
bopbee_upload_files | Upload base64-encoded files (optional deploy) |
bopbee_list_domains | Custom domains |
bopbee_add_domain | Add domain |
bopbee_remove_domain | Remove domain |
OpenAPI resource
The MCP server exposes bopbee://openapi.json: the same filtered OpenAPI document as GET /v1/openapi.json (requires a valid API key).
Uploads via MCP
Use bopbee_upload_files with base64-encoded file content:
{
"project_id": "proj-abc123",
"files": [
{ "filename": "index.html", "content_base64": "PGh0bWw+..." }
],
"deploy": true
}For large archives or many files, the REST POST /projects/{id}/uploads multipart endpoint may be more efficient.