Drone CI integration
Drone CI is a self-hosted continuous integration and delivery platform. The REST API exposes user, repository, build, secret, and cron management - used to trigger pipelines, monitor build status, manage signing/encrypted secrets, and schedule recurring builds. Authentication uses a personal token issued from the Drone user account page.
Say what should happen.
The workflow builds itself.
Common Drone CI use cases
- Show a schedule UI
- Cancel a stuck build
- Retry a transient failure
- Verify Drone token is valid
- Build a repository picker UI
- Render a build history table
- Promote a build to production
- Reject a production promotion
- Add a Docker registry password
- Off-board a repository from Drone
What you can do with Drone CI
Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.
Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.
Build, 8 operations
approve_build_stageApprove build stagePOSTApproves a blocked build stage.cancel_buildCancel buildDELETECancels a running build.create_buildCreate buildPOSTTriggers a new build via the API.decline_build_stageDecline build stagePOSTDeclines a blocked build stage.get_buildGet buildGETReturns a single build with its stages and steps.list_buildsList buildsGETLists recent builds for a repository.promote_buildPromote buildPOSTPromotes a build to a deployment target.restart_buildRestart buildPOSTRe-runs a previous build with the same commit.
Repository, 8 operations
chown_repoChown repoPOSTReassigns repository ownership to the authenticated user.disable_repoDisable repoDELETEDisables (or removes) a Drone repository.enable_repoEnable repoPOSTActivates a repository in Drone.get_repoGet repoGETReturns metadata for a single Drone repository.list_user_reposList user reposGETLists all repositories visible to the authenticated user.repair_repoRepair repoPOSTRecreates the SCM webhook for a repository.sync_user_reposSync user reposPOSTForces a refresh of the repositories visible to the user.update_repoUpdate repoPATCHUpdates configurable fields of a Drone repository.
Cron, 4 operations
create_cronCreate cronPOSTCreates a recurring cron-triggered build.delete_cronDelete cronDELETEDeletes a cron entry.exec_cronExec cronPOSTTriggers a cron entry on demand.list_cronsList cronsGETLists cron jobs registered on a repository.
Secret, 3 operations
create_repo_secretCreate repo secretPOSTCreates a new repository secret.delete_repo_secretDelete repo secretDELETEDeletes a repository secret.list_repo_secretsList repo secretsGETLists secrets registered on a repository.
User, 1 operation
get_current_userGet current userGETRetrieves the authenticated Drone CI user's profile.
Use Drone CI from Claude Code, Cursor or Codex
Connect Drone CI in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Drone CI operations become tools the client can call, next to every other integration you connected.
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"
[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"{
"mcpServers": {
"livecontext": {
"type": "http",
"url": "https://livecontext.ai/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}How to connect Drone CI
- Create your workspace
Sign up free. Nothing to install.
- Connect Drone CI once
Add your Drone CI connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
- Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.
Drone CI integration FAQ
What can you do with the Drone CI integration?
LiveContext exposes 24 operations on Drone CI, covering build, repository, cron and secret. Common uses include Show a schedule UI, Cancel a stuck build and Retry a transient failure.
