4,000+ servers built on vurb.ts
Vinkius

Drone CI MCP Server for CrewAIGive CrewAI instant access to 39 tools to Approve Build, Chown Repo, Create Build, and more

MCP Inspector GDPR Free for Subscribers

Connect your CrewAI agents to Drone CI through Vinkius, pass the Edge URL in the `mcps` parameter and every Drone CI tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Ask AI about this MCP Server for CrewAI

The Drone CI MCP Server for CrewAI is a standout in the Ship It category — giving your AI agent 39 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Drone CI Specialist",
    goal="Help users interact with Drone CI effectively",
    backstory=(
        "You are an expert at leveraging Drone CI tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Drone CI "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 39 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
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

About Drone CI MCP Server

Connect your Drone CI server to any AI agent to streamline your DevOps lifecycle through natural language.

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.

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.

The Drone CI MCP Server exposes 39 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 39 Drone CI tools available for CrewAI

When CrewAI connects to Drone CI through Vinkius, your AI agent gets direct access to every tool listed below — spanning ci-cd, build-automation, repository-management, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

approve

Approve build on Drone CI

Approve a blocked build

chown

Chown repo on Drone CI

Change repository ownership to current user

create

Create build on Drone CI

Create a custom build for a branch

create

Create cron job on Drone CI

Create a new cron job

create

Create secret on Drone CI

Create a new repository secret

create

Create template on Drone CI

Create a new template

create

Create user on Drone CI

Create a new user account (Admin)

decline

Decline build on Drone CI

Decline a blocked build

delete

Delete cron job on Drone CI

Delete a cron job

delete

Delete secret on Drone CI

Delete a repository secret

delete

Delete template on Drone CI

Delete a template

delete

Delete user on Drone CI

Delete a user account (Admin)

disable

Disable repo on Drone CI

Disable or delete a repository

enable

Enable repo on Drone CI

Enable/register a repository in Drone

get

Get build on Drone CI

Get specific build info including stages and steps

get

Get build logs on Drone CI

Get logs for a specific step in a build stage

get

Get cron job on Drone CI

Get cron job details

get

Get current user on Drone CI

Get current authenticated user info

get

Get current user repos on Drone CI

Get current user repositories

get

Get repo on Drone CI

Get repository info

get

Get secret on Drone CI

Get repository secret details

get

Get template on Drone CI

Get template details

get

Get user on Drone CI

Get user info by login (Admin)

list

List builds on Drone CI

List recent builds for a repository

list

List cron jobs on Drone CI

List cron jobs for a repository

list

List secrets on Drone CI

List repository secrets

list

List templates on Drone CI

List organization templates

list

List users on Drone CI

Requires administrative privileges. List all registered users (Admin)

promote

Promote build on Drone CI

Promote a build to a target environment

repair

Repair repo on Drone CI

Repair repository webhooks

restart

Restart build on Drone CI

Restart a specific build

stop

Stop build on Drone CI

Stop a running build (Admin)

sync

Sync user repos on Drone CI

Synchronize user repositories

trigger

Trigger cron job on Drone CI

Manually trigger an existing cron task

update

Update cron job on Drone CI

Update a cron job

update

Update repo on Drone CI

Update repository configuration

update

Update secret on Drone CI

Update a repository secret

update

Update template on Drone CI

Update a template

update

Update user on Drone CI

Update a user account (Admin)

Connect Drone CI to CrewAI via MCP

Follow these steps to wire Drone CI into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Install CrewAI

Run pip install crewai
02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
03

Customize the agent

Adjust the role, goal, and backstory to fit your use case
04

Run the crew

Run python crew.py. CrewAI auto-discovers 39 tools from Drone CI

Why Use CrewAI with the Drone CI MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Drone CI through the Model Context Protocol.

01

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

02

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

03

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

04

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

Drone CI + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Drone CI MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries Drone CI for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries Drone CI, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain Drone CI tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries Drone CI against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for Drone CI in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Drone CI immediately.

01

"List all my active repositories in Drone."

02

"Show me the logs for build #42 of the 'acme/api' repository."

03

"Create a new secret named 'DB_PASSWORD' for the 'acme/web-app' repo."

Troubleshooting Drone CI MCP Server with CrewAI

Common issues when connecting Drone CI to CrewAI through Vinkius, and how to resolve them.

01

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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.

Drone CI + CrewAI FAQ

Common questions about integrating Drone CI MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.

Explore More MCP Servers

View all →