How to Use the Drone CI MCP in CrewAI

Q: Can I restrict which agents use Drone CI tools?

You can. By using the toolfilter in your agent definition, you ensure only the specific agents responsible for CI/CD can touch your pipelines.

Deploy a specialized crew of agents to manage Drone CI. Monitor, analyze, and repair pipelines without human intervention.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Drone CI MCP to CrewAI

Create your Vinkius account to connect Drone CI to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Drone CI with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Specialized pipeline monitoring

Assign a 'Monitor' agent to watch your builds using `list_builds`. It keeps an eye on the health of your pipelines while other agents focus on development. When the monitor detects an issue, it alerts the rest of the crew. It's a proactive way to maintain your infrastructure.

Autonomous repair operations

If a build fails, your 'Engineer' agent can use `get_build_logs` to diagnose the error. It then takes corrective action by calling `restart_build` or `repair_repo`. This removes the need for a human to wake up at 3 AM to fix a simple webhook failure. The crew handles the routine maintenance for you.

Hierarchical build management

Use a hierarchical structure where a 'Lead' agent authorizes the `promote_build` commands sent by subordinates. It adds a layer of oversight to your automated releases. This setup mirrors a real team, ensuring that actions are vetted before they hit production. It provides structure to your autonomous CI/CD operations.

Setup guide

Set up Drone CI MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Drone CI tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Drone CI Analyst",
    goal="Access and analyze Drone CI data via MCP.",
    backstory="Expert analyst with direct Drone CI access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Drone CI transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Drone CI Analyst",
        goal="Access and analyze Drone CI data via MCP.",
        backstory="Expert analyst with direct Drone CI access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Drone CI transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Drone CI. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Drone CI now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Drone CI MCP in CrewAI

You pass the server URL directly to the agent's MCP configuration. Once connected, your agents can access the full suite of 39 tools to interact with your build pipelines.

Yes. One agent can query repository data, and another can analyze it. They share memory to ensure the crew knows exactly which build needs attention.

The agent receives an error message back from the MCP Server. You can program your agents to handle these errors by logging them to a specific channel or retrying the operation.

You can. By using the `tool_filter` in your agent definition, you ensure only the specific agents responsible for CI/CD can touch your pipelines.

Your build metadata and logs are processed within the secure memory of your agents. We use ephemeral sessions to ensure that your sensitive CI/CD data isn't persisted beyond the scope of the task.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript