Supercharge your AI with Woodpecker CI. Control builds, agents, and secrets from chat.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Connect to your AI in seconds.
Woodpecker CI lets you manage your entire continuous integration and deployment stack directly from chat. Trigger builds, monitor agent health, update repository settings, and handle secrets without opening a dashboard or writing a single command line.
It gives developers and ops engineers full control over their build pipelines using natural language.
What your AI can do
Activate repo
Marks a repository as active on the server.
Cancel pipeline
Stops a pipeline that is currently running.
Chown repo
Changes the owner of a repository to your current user account.
Trigger manual builds, restart failed processes, or cancel running jobs for any code repository.
View all connected build agents, check their operational health, and create or delete them as needed.
Create, list, and manage sensitive configuration keys at the global, organization, or repository level.
Retrieve detailed system metrics, server versions, and current user permissions to audit the environment.
Activate new codebases, update their settings, or repair broken webhooks directly through conversation.
Ask an AI about this
Compatible AI Apps
OAuth 2.0 Compatible Gemini Waiting for input…
34 Woodpecker CI Tools Available
These tools give you granular control over every part of the DevOps lifecycle: managing pipelines, monitoring agents, and securing credentials.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Woodpecker CI on VinkiusActivate Repo
Marks a repository as active on the server.
Cancel Pipeline
Stops a pipeline that is currently running.
Chown Repo
Changes the owner of a repository to your current user account.
Create Agent
Adds and configures a brand new build agent for the system.
Create Global Secret
Creates a secret accessible across all organizations on the server.
Create Repo Secret
Adds a sensitive key specific to one repository.
Delete Agent
Removes an agent from the system completely.
Delete Pipeline
Deletes a previously run pipeline record.
Delete Repo
Deactivates or permanently deletes an entire repository.
Get Agent
Fetches specific details about a single build agent.
Get Healthz
Checks the overall operational health of the CI server instance.
Get Metrics
Retrieves detailed performance metrics from Prometheus for monitoring purposes.
Get Org Permissions
Lists what permissions a user has within an organization.
Get Pipeline Config
Fetches the actual configuration files used by a given pipeline.
Get Pipeline
Retrieves general details about a specific pipeline run.
Get Repo
Gets general metadata and details for any repository.
Get User
Identifies the user account currently authenticated to the system.
Get Version
Reports the current version number of the Woodpecker server software.
List Agent Tasks
Shows all tasks that are currently assigned to a specific agent.
List Agents
Lists every available build agent connected to the server.
List Global Secrets
Displays all secrets created at the global administrative level.
List Org Agents
Lists agents that belong only to a specific organization.
List Org Secrets
Shows all secrets created at the organization level.
List Orgs
Retrieves a list of every organizational container on the server.
List Pipelines
Lists all completed pipeline runs for a specific repository.
List Repo Secrets
Displays all secrets that are attached to one particular repository.
List Repos
Lists every single repository available on the entire server.
List Users
Displays a list of all user accounts configured in the system (Admin only).
Lookup Repo
Finds and retrieves details for a repository using its full name or slug.
Repair Repo
Fixes broken webhooks for an existing repository so it can trigger builds again.
Restart Pipeline
Forces a restart of a pipeline that previously ran.
Trigger Pipeline
Manually starts a new build process for a repository.
Update Agent
Modifies the configuration of an existing build agent.
Update Repo
Updates general settings and parameters for a specific repository.
Connect to your AI in seconds. Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token from
cloud.vinkius.com. For OAuth-protected servers, expand Advanced
settings to add credentials.
Start a conversation
Open a new chat. The Woodpecker CI integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Woodpecker CI, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Woodpecker 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.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 34 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Checking on build status feels like a full-time job.
Right now, when a deployment fails or an agent goes offline, you have to open the CI dashboard. You click the repo, then find the pipeline history tab, scroll through dozens of runs, and finally check which specific agents were assigned to that build. It's endless clicking just to answer: 'Is it running?'
With this MCP, you just ask your agent. Tell it: 'What is the status of all our build agents.' The system responds immediately with a clean list, or if something broke, you can run `get_healthz` and get an instant report. You cut out the dashboard navigation entirely.
Managing secrets gets simple with Woodpecker CI MCP
Before this, if a key needed updating, you might have to check documentation or talk to an admin just to know if the token was global or specific to one project. Finding and verifying that secret required jumping between different configuration sections.
Now, you can ask your agent: 'Show me all organization-level secrets.' The system provides a clear list of everything available using `list_org_secrets`. You've got instant, audited visibility into your entire security perimeter.
What your AI can actually do with this
You can automate all the complex steps involved in building and deploying code through your AI client. Instead of jumping between dashboards to check agent status or manually triggering builds, you talk to this MCP. You tell it which pipeline needs running for a specific repo, and it handles the rest.
It lets you manage secrets—whether they’re global organization settings or just specific repository keys—and keeps tabs on everything. Need to know if an agent is online? Ask. Want to check what configuration files a build used? It finds them. You can even update repo settings, like repairing webhooks that break.
Because Vinkius handles all credentials using a zero-trust proxy, your sensitive tokens never sit on disk—it’s safe.
This capability lets you orchestrate entire DevOps workflows across multiple platforms. For instance, you can chain this MCP with a messaging tool to automatically post success status updates once the build finishes. The whole thing runs through Vinkius AI Analytics, so you always see exactly which tools were called and how much of your budget was used.
019e390c-bee6-70c8-8a60-0849fc4ae8ee 
Here's how it actually works
The bottom line is you manage complex infrastructure using simple commands in chat.
Provide your Woodpecker Server URL and the necessary personal access token.
Connect this MCP to your preferred AI client (Claude, Cursor, etc.).
Tell your agent exactly what needs doing—for example: 'Check the health of all agents' or 'Trigger a pipeline for repo X'.
Who is this actually for?
This is for the SRE who spends too much time clicking through dashboards at 2 am to debug a failing build, or the developer who needs to quickly check if their code was deployed without leaving their IDE. It centralizes infrastructure control.
Monitoring build agents and troubleshooting complex, failing pipelines using natural language queries.
Keeping an eye on the CI infrastructure health, managing organizational secrets, and auditing system performance metrics.
Triggering test builds or checking pipeline status directly from their code editor without switching applications.
What Changes When You Connect
You get immediate visibility into infrastructure health. Use get_healthz or list_agents to quickly check if your build runners are online without opening a dedicated monitoring dashboard.
Managing credentials is painless. You can use create_global_secret or create_repo_secret to store sensitive keys, and the process is safe because Vinkius handles credentials using a zero-trust proxy; your tokens never sit on disk.
Debugging pipelines is faster than ever. Instead of guessing what went wrong, you can ask for the configuration files with get_pipeline_config or check past runs using list_pipelines to see exactly where it failed.
Repository maintenance is simple. If a webhook breaks, running repair_repo fixes it instantly from your conversation, letting you get back to coding without manual intervention.
You can automate the entire lifecycle. You don't just trigger builds; you use tools like trigger_pipeline and then follow up with get_user details to log who initiated the deployment.
See it in action
A build fails, and I need to know why.
The dev noticed a pipeline failure. Instead of digging through logs, they ask their agent to use get_pipeline for the last run and then use list_pipelines to see the history. They find out the build failed because the repository needed its webhooks repaired using repair_repo.
We need a new dedicated testing environment.
The ops team needs more capacity. They use their agent to first check if they can create resources (create_agent) and then run it for the specific repo using activate_repo before running test builds via trigger_pipeline.
I need to update a deployment secret.
A critical API key expires. The developer uses their agent to find all relevant secrets with list_global_secrets, updates the required credential using create_repo_secret, and ensures it’s properly linked via update_repo.
The build system seems slow or unstable.
The SRE needs to check performance. They use get_metrics for detailed Prometheus data, then use list_users and get_user to confirm who has admin access and what their permissions are via get_org_permissions.
The honest tradeoffs
Trying to manually fix webhooks
Logging into the CI dashboard, navigating to the repo settings, and clicking through multiple tabs just to find a broken webhook URL.
Use the repair_repo tool. Tell your agent, 'Fix the webhooks for this repository.' It handles the entire process in one step.
Forgetting which secrets are where
Searching through dozens of files to remember if a critical token was set as a global secret or just per-repo.
Use list_global_secrets and then follow up with list_repo_secrets to get a complete, categorized inventory of every key.
Assuming the build agent is fine
The build fails, but no one checks if the agent itself was decommissioned or needs updating.
First, run list_agents to see who's online. If something looks off, use get_agent or update_agent before triggering a new pipeline.
When It Fits, When It Doesn't
Use this MCP if your job involves managing the entire lifecycle of code: building it, testing it, deploying it, and securing the credentials used across those steps. You need tools like trigger_pipeline, list_agents, and secret management (create_repo_secret). Don't use this if you only need simple file storage or static website hosting; look for a dedicated asset management MCP instead. If your primary goal is just reading code, that’s a source control tool job. This is the orchestration layer—it makes sure all the other pieces talk to each other and run securely.
Questions you might have
How do I trigger a new build with the Woodpecker CI MCP? +
You use the trigger_pipeline tool. Just tell your agent which repository and what kind of manual run you need, and it starts the process immediately.
What if I want to stop a build that's running right now? Use cancel_pipeline. +
To halt an active job, use cancel_pipeline. You just reference the pipeline ID or name, and your agent sends the cancellation signal to the server.
Can I update my repository settings using the Woodpecker CI MCP? +
Yes, you can use update_repo to adjust general repo parameters. You'll need to provide the specific changes and the ID of the repository you want to modify.
How do I check if my webhooks are broken? Use repair_repo. +
If a build isn't triggering automatically, run repair_repo. This tool fixes any broken webhook connections for that repo, getting your CI process running again fast.
What is the difference between list_agents and get_agent? +
Use list_agents to see every agent connected to the system. If you need detailed status or specific info on just one, run get_agent.
How do I check if my Woodpecker CI server is actually operational using get_healthz? +
It provides an immediate status report on the entire CI infrastructure. This simple call confirms if the whole system is up and running smoothly, helping you rule out service outages before triggering any builds.
I'm setting up a new project; how do I make sure my repository is ready to build using activate_repo? +
Using activate_repo makes the repository fully visible and ready for CI processes. Sometimes, repos need explicit activation before agents can properly run builds or hooks against them.
How do I view all organization-level secrets with list_org_secrets? +
This tool shows credentials set up for the entire organization. It lets you verify shared keys and tokens that multiple agents need to access, keeping your critical configurations centralized.
Can I trigger a new pipeline build for a specific repository? +
Yes. Use the trigger_pipeline tool by providing the repository ID. You can also specify a branch or commit if needed to start a new execution immediately.
How do I check if my build agents are online and healthy? +
You can use list_agents to see all connected agents and their status. For more detail on a specific agent, use get_agent or list_agent_tasks to see what it's currently working on.
Is it possible to manage environment secrets through this agent? +
Yes, the server includes tools like create_repo_secret and list_repo_secrets to manage sensitive variables at the repository level, as well as global and organization-level secret tools.
We've already built the connector for Woodpecker CI. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 34 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.