4,000+ servers built on vurb.ts
Vinkius
CursorIDE
Drone CI MCP Server

Bring Ci Cd
to Cursor

Learn how to connect Drone CI to Cursor and start using 39 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Approve BuildChown RepoCreate BuildCreate Cron JobCreate SecretCreate TemplateCreate UserDecline BuildDelete Cron JobDelete SecretDelete TemplateDelete UserDisable RepoEnable RepoGet BuildGet Build LogsGet Cron JobGet Current UserGet Current User ReposGet RepoGet SecretGet TemplateGet UserList BuildsList Cron JobsList SecretsList TemplatesList UsersPromote BuildRepair RepoRestart BuildStop BuildSync User ReposTrigger Cron JobUpdate Cron JobUpdate RepoUpdate SecretUpdate TemplateUpdate User

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Drone CI

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, and restart_build.
  • Repository Control — Enable, update, or repair repository settings and sync them with your source control provider via enable_repo and sync_user_repos.
  • Secret & Config Management — Manage environment secrets, cron jobs, and templates without leaving your chat interface using list_secrets and create_cron_job.
  • User Administration — (Admin only) Create, update, or delete users and manage organizational access with list_users and create_user.
  • Log Inspection — Fetch build logs to debug pipeline failures instantly using get_build_logs.

How it works

  1. Subscribe to this server
  2. Provide your Drone Server URL and Personal Access Token
  3. 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_build

Approve a blocked build

chown_repo

Change repository ownership to current user

create_build

Create a custom build for a branch

create_cron_job

Create a new cron job

create_secret

Create a new repository secret

create_template

Create a new template

create_user

Create a new user account (Admin)

decline_build

Decline a blocked build

delete_cron_job

Delete a cron job

delete_secret

Delete a repository secret

delete_template

Delete a template

delete_user

Delete a user account (Admin)

disable_repo

Disable or delete a repository

enable_repo

Enable/register a repository in Drone

get_build

Get specific build info including stages and steps

get_build_logs

Get logs for a specific step in a build stage

get_cron_job

Get cron job details

get_current_user

Get current authenticated user info

get_current_user_repos

Get current user repositories

get_repo

Get repository info

get_secret

Get repository secret details

get_template

Get template details

get_user

Get user info by login (Admin)

list_builds

List recent builds for a repository

list_cron_jobs

List cron jobs for a repository

list_secrets

List repository secrets

list_templates

List organization templates

list_users

Requires administrative privileges. List all registered users (Admin)

promote_build

Promote a build to a target environment

repair_repo

Repair repository webhooks

restart_build

Restart a specific build

stop_build

Stop a running build (Admin)

sync_user_repos

Synchronize user repositories

trigger_cron_job

Manually trigger an existing cron task

update_cron_job

Update a cron job

update_repo

Update repository configuration

update_secret

Update a repository secret

update_template

Update a template

update_user

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

See it in action

Drone CI in Cursor

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

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.

Drone CI
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

The Vinkius Advantage

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.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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.

02

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.

03

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.

04

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.

05

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.

06

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.

07

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.

08

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

09

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Explore More MCP Servers

View all →