# Drone CI MCP for AI Agents MCP > Drone CI lets your AI client manage entire DevOps pipelines right from chat. Connect it to monitor builds, handle repository settings, and manage critical environment secrets without logging into a dashboard. It brings continuous integration and deployment control directly into your natural conversation. ## Overview - **Category:** ship-it - **Price:** Free - **Tags:** ci-cd, build-automation, repository-management, pipeline-monitoring, secrets-management, deployment ## Description Need to keep track of build failures or manually trigger a test run? This MCP connects your AI agent to the Drone CI system, giving you full command over your development lifecycle via plain language commands. Instead of jumping between dashboards, you talk to your agent and it performs actions like listing recent builds, getting detailed log reports, or even restarting failed deployments. It handles more than just code checking; you can manage infrastructure pieces too. You'll use it to create necessary environment secrets, set up scheduled tasks using cron jobs, or control repository access. If your current setup feels scattered across multiple tools, connecting this via Vinkius lets all those functions live under one roof. It gives developers and SREs the ability to monitor pipeline health and manage resources directly from their chat interface. ## Tools ### approve_build Approves a build that is currently blocked and awaiting manual sign-off. ### chown_repo Changes the ownership of a repository to be assigned to your current user account. ### create_build Starts a custom build process for a specific branch in a repository. ### create_cron_job Sets up and registers a new automated, scheduled task (a cron job). ### create_secret Generates and stores a new secret credential for use within the repository. ### create_template Creates a reusable template that can define build or deployment steps. ### create_user Adds a new user account to the organization (Admin privilege required). ### decline_build Declines a build that was blocked and awaiting manual sign-off. ### delete_cron_job Removes an existing automated cron job from the system. ### delete_secret Permanently deletes a repository secret credential. ### delete_template Deletes a reusable template that was previously created. ### delete_user Removes an existing user account from the organization (Admin privilege required). ### disable_repo Disables or completely removes a repository from service. ### enable_repo Activates and registers a repository within the Drone CI system. ### get_build_logs Retrieves detailed logs for a specific step during a build stage, helping you find errors. ### get_build Pulls all the details about a specific build, including its stages and steps. ### get_cron_job Retrieves the current configuration and status of an existing cron job. ### get_current_user_repos Lists all repositories that belong to your currently authenticated user account. ### get_current_user Provides information about the user who is currently logged into the system. ### get_repo Retrieves detailed information for a specific repository by name or ID. ### get_secret Shows the current details and metadata of a stored repository secret. ### get_template Retrieves detailed information about a specific reusable template. ### get_user Looks up details for another user account using their unique login name (Admin privilege required). ### list_builds Retrieves a list of the most recent build attempts for your repository. ### list_cron_jobs Shows all scheduled cron jobs configured for a specific repository. ### list_secrets Lists all the secret credentials currently stored for your repository. ### list_templates Displays a list of reusable templates available across the entire organization. ### list_users Lists every user registered in the system (Admin privilege required). ### promote_build Moves a successful build from one environment to a more advanced target environment. ### repair_repo Fixes any issues with the repository's webhooks, ensuring proper communication. ### restart_build Forces a specific build run to start again from scratch. ### stop_build Stops a running build process immediately (Admin privilege required). ### sync_user_repos Updates and synchronizes the list of repositories associated with your user account. ### trigger_cron_job Manually executes an existing scheduled cron task right now. ### update_cron_job Modifies the schedule or parameters of a running cron job. ### update_repo Changes general configuration settings for an existing repository. ### update_secret Modifies the value or metadata of a stored repository secret. ### update_template Makes changes to the structure or content of an existing reusable template. ### update_user Modifies details for another user account in the organization (Admin privilege required). ## Prompt Examples **Prompt:** ``` Show me all my repositories and what their latest build status is. ``` **Response:** ``` **Current User Repositories** | Repo Name | Latest Build Status | Last Updated | | :--- | :--- | :--- | | acme/web-app | ✅ Success (Build #45) | 2026-06-10 | | acme/api | 🟡 Failed (Build #43) | 2026-06-11 | | docs/site | ✅ Success (Build #12) | 2026-06-05 | Looks like the API build failed. Would you like me to fetch the logs for that run? ``` **Prompt:** ``` I need a new secret key for the staging environment database. ``` **Response:** ``` **Secret Creation Initiated** * **Repository:** acme/web-app * **New Secret Name:** `STAGING_DB_PASSWORD` * **Status:** Pending Value Input Please provide the secure value for this secret. Once you send it, I'll store it and update the configuration automatically. ``` **Prompt:** ``` What cron jobs are running for the API repo? ``` **Response:** ``` **Scheduled Tasks for acme/api** * **Job Name:** Daily Health Check * **Schedule:** 0 3 * * * (3 AM daily) * **Status:** Active * **Last Run:** 2026-06-12 at 3:00 AM I can also trigger this job right now if you need to test it. ``` ## Capabilities ### View and Control Build Status Get a list of recent builds, check detailed build information, or restart specific failed pipelines. ### Manage Repository Settings Enable, update, or synchronize repository settings with your source control provider. ### Handle Secrets and Credentials Create, read, update, or delete sensitive environment secrets and credentials needed for deployment. ### Schedule Automated Tasks (Cron) Set up new scheduled cron jobs or manually trigger existing background tasks. ### Administer Users and Access Create, delete, or update user accounts and manage overall organizational access permissions (requires admin rights). ## Use Cases ### Investigating a Failed Deployment A developer notices the staging environment build failed. They ask their agent to 'Show me the logs for the latest API build.' The agent uses `get_build_logs` and immediately identifies that the error is a connection timeout, allowing them to fix it instantly. ### Implementing Scheduled Maintenance The SRE needs to run a cleanup job every Monday at 3 AM. Instead of logging into the scheduler UI, they ask their agent to 'Set up a cron job for user data cleanup.' The MCP uses `create_cron_job` and handles the scheduling. ### Adding New Security Credentials A new microservice requires database access. The developer asks the AI client to 'Create a secret key for the production DB credentials.' The agent runs `create_secret`, making sure the credential is stored securely and ready for use. ### Auditing User Access The Ops Manager needs to know who has access. They ask their agent to 'List all registered users' which uses `list_users`. The manager gets a full list of accounts, speeding up compliance checks. ## Benefits - Instead of manually checking a web dashboard, you can ask your agent to list recent builds or get details on the latest run using `list_builds` or `get_build`. - You eliminate context switching when managing credentials. Use the MCP to create and retrieve secrets via `create_secret` or `get_secret`, all within your chat window. - The agent handles complex admin tasks, like setting up recurring maintenance jobs using `create_cron_job` and keeping track of them with `list_cron_jobs`. - When a deployment fails, you don't hunt through logs. You simply ask to get build logs using `get_build_logs` and the failure point appears instantly. - Admin tasks become conversational. Need to onboard someone? Use your agent to create new users or sync repositories with `create_user` or `sync_user_repos`. ## How It Works The bottom line is that once connected, your agent translates natural language into specific DevOps API calls, giving you immediate control over complex CI/CD systems. 1. Subscribe to the Drone CI MCP in Vinkius and provide your specific Drone Server URL and Personal Access Token. 2. Select this MCP within any compatible client, like Cursor or Claude. Your agent now has access to all build, repo, and secret tools. 3. Tell your AI client what you need done—for example, 'List the last five builds for my web app'—and it executes the command. ## Frequently Asked Questions **How does the Drone CI MCP help me monitor build status?** You can ask your agent for a list of builds or check specific details about a recent run. It pulls this data directly, showing you if deployments succeeded or failed without needing to visit the dashboard. **Can I use Drone CI MCP to manage my sensitive credentials?** Yes, it lets you create, read, update, and delete secrets right from the chat. This keeps your process secure and fast; you never have to copy/paste passwords into a UI. **Does Drone CI MCP handle scheduling tasks?** Absolutely. You can use it to set up new automated cron jobs or manually trigger existing ones, managing all recurring work from one place. **What if a build fails? Can the Drone CI MCP help me find the error?** When you ask about a failure, your agent can retrieve detailed logs for that specific step. It gives you the exact technical message and line number needed to fix the problem immediately. **Is Drone CI MCP only for admins?** No, while some tools require admin rights (like deleting users), most common tasks—checking status or viewing logs—are available to any user who needs visibility into the pipeline health.