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

Bring Ci Cd
to CrewAI

Learn how to connect Drone CI to CrewAI 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 CrewAI?

When paired with CrewAI, Drone CI becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Drone CI tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

  • Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

  • CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the mcps parameter and agents auto-discover every available tool at runtime

  • Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

  • Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

Drone CI in CrewAI

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 CrewAI 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 CrewAI

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 CrewAI 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 CrewAI

Every tool call from CrewAI 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

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

05

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

06

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

07

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

08

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Explore More MCP Servers

View all →