POST /api/mcp/connectors/upload (a zip) or POST /api/mcp/connectors/upload-github, the server queues a build and answers 202 with a build_id. Use that build_id with the route on this page to follow the build to the end. Upload guide: Deploy an MCP server.
The CLI does this for you: nasiko mcp connector upload waits on this route and prints each state change.
Authentication
Send the session JWT fromPOST /api/auth/login as Authorization: Bearer <token>, or use the dashboard cookie. Any authenticated user can call it, but only for their own uploads. A superuser can read any upload.
Endpoints
Get upload status
GET /api/mcp/connectors/uploads/{upload_id}
Returns the current state of one upload’s build. Poll it after an upload until status is success or failed.
Prefer this route over GET /api/mcp/connectors/{id}/build-status for polling. If a first-time upload fails, the connector is removed so you can re-upload under the same name, and the connector-scoped route then returns 404. This route keeps answering for the upload either way.
Auth: session JWT or dashboard cookie. Role: the user who uploaded, or a superuser.
Path parameters
Example
Upload, then poll:Response fields
States
A build that stops without finishing is marked
failed with the message build job did not complete.
Errors
Errors use the envelope{ "data": null, "status_code": <n>, "message": "..." }.
Notes
- Read-only and safe to call repeatedly. There’s no push notification or stream; poll on an interval. The CLI polls every 2 seconds.
- The
connector_idreturned by the upload stays useful for build logs while the connector exists.