Compatible with every major AI agent and IDE
What is the Drone CI MCP Server?
Connect your Drone CI server to any AI agent to streamline your DevOps lifecycle through natural language.
What you can do
- Build Management — List, get details, restart, or stop builds across your repositories using
list_builds,get_build, andrestart_build. - Repository Control — Enable, update, or repair repository settings and sync them with your source control provider via
enable_repoandsync_user_repos. - Secret & Config Management — Manage environment secrets, cron jobs, and templates without leaving your chat interface using
list_secretsandcreate_cron_job. - User Administration — (Admin only) Create, update, or delete users and manage organizational access with
list_usersandcreate_user. - Log Inspection — Fetch build logs to debug pipeline failures instantly using
get_build_logs.
How it works
- Subscribe to this server
- Provide your Drone Server URL and Personal Access Token
- Start orchestrating your pipelines from Claude, Cursor, or any MCP client
Who is this for?
- DevOps Engineers — Monitor pipeline health and trigger builds via voice or text.
- Software Developers — Check build logs and status directly from the IDE.
- SREs — Manage secrets and cron jobs across multiple projects efficiently.
Built-in capabilities (39)
Approve a blocked build
Change repository ownership to current user
Create a custom build for a branch
Create a new cron job
Create a new repository secret
Create a new template
Create a new user account (Admin)
Decline a blocked build
Delete a cron job
Delete a repository secret
Delete a template
Delete a user account (Admin)
Disable or delete a repository
Enable/register a repository in Drone
Get specific build info including stages and steps
Get logs for a specific step in a build stage
Get cron job details
Get current authenticated user info
Get current user repositories
Get repository info
Get repository secret details
Get template details
Get user info by login (Admin)
List recent builds for a repository
List cron jobs for a repository
List repository secrets
List organization templates
Requires administrative privileges. List all registered users (Admin)
Promote a build to a target environment
Repair repository webhooks
Restart a specific build
Stop a running build (Admin)
Synchronize user repositories
Manually trigger an existing cron task
Update a cron job
Update repository configuration
Update a repository secret
Update a template
Update a user account (Admin)
Why Cursor?
Cursor's Agent mode turns Drone CI into an in-editor superpower. Ask Cursor to generate code using live data from Drone CI and it fetches, processes, and writes. all in a single agentic loop. 39 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Drone CI in Cursor
Drone CI and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Drone CI to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Drone CI in Cursor
The Drone CI MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 39 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Drone CI for Cursor
Every tool call from Cursor to the Drone CI MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I view the logs of a specific build to debug an error?
Yes, use the get_build_logs tool by providing the owner, repo name, and build number. Your agent will retrieve the full output from the pipeline steps.
How do I trigger a new build for a repository?
You can use the create_build tool to trigger a new build or restart_build to re-run an existing build number for a specific repository.
Is it possible to manage environment secrets through this agent?
Absolutely. You can use list_secrets, create_secret, and update_secret to manage your repository's sensitive data securely from the conversation.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
HHS Open Payments
6 toolsAccess the HHS Open Payments database to search for physicians, teaching hospitals, and financial relationships in the healthcare industry.

BL.INK
10 toolsManage enterprise links via BL.INK — shorten URLs, track analytics, and manage branded domains directly from any AI agent.

Jira Software Cloud
31 toolsManage Jira Software Agile workflows — list boards, track sprints, manage backlogs, and inspect epics directly from your AI agent.

ZIP Codes API
6 toolsManage ZIP code data — audit locations, distances, and regions via AI.
