Host apps and websites, spin up Sandboxes, manage domains, run tests, deploy to any cloud, and automate delivery with pipelines, all in one platform. Configure everything through the UI, YAML, or code, or let Claude Code, Cursor, Copilot, and other AI agents operate Buddy directly through MCP or CLI, including deployments, infrastructure, and logs.
This is the 5th launch from Buddy Works. View more
Buddy AI Access (MCP)
Launching today
Your agent needs more than your repo
Give AI agents secure access to your infrastructure and workflow. With Buddy MCP agents can run pipelines, inspect logs, deploy apps, create sandboxes, publish artifacts and manage domains. Control exactly what they can access with workspace permissions and tool scopes. Works with Claude Code, Cursor, Codex, Copilot and other MCP clients.
Hi Product Hunt!
A coding agent can fix a bug in your repository, but it usually has no access to what happens in your delivery platform. If a pipeline fails, someone still has to check the logs, rerun it, and handle the deployment.
We built Buddy MCP to give agents direct and secure access to that part of the workflow.
It works with Claude Code, Cursor, Codex, Copilot, and other MCP clients. Access can be limited by workspace, permissions, and available tool categories, so an agent only gets the capabilities you choose to give it.
We are especially interested in where teams draw the line today.
Do you already let coding agents interact with delivery workflow and infrastructure, or do they still stop at the repository?
We use Buddy to build Buddy, so AI access has been a part of our own workflow for quite some time.
One of the things I use it for the most is debugging failed CI builds. It allows me to check the logs from my terminal, figure out what went wrong, push a fix and run the pipeline again without jumping between various tools. The productivity boost is tangible.
The same goes for working with targets. Being able to safely run commands on them means debugging becomes part of the flow instead of a disruption.
We're excited to finally share this with all of you. Would love to hear how you're using MCP clients in your own workflows!
Buddy Works
Buddy Works
Hi Hunters! 👋
I'm Paul, one of the makers behind Buddy.
We use Buddy to build Buddy, so AI access has been a part of our own workflow for quite some time.
One of the things I use it for the most is debugging failed CI builds. It allows me to check the logs from my terminal, figure out what went wrong, push a fix and run the pipeline again without jumping between various tools. The productivity boost is tangible.
The same goes for working with targets. Being able to safely run commands on them means debugging becomes part of the flow instead of a disruption.
We're excited to finally share this with all of you. Would love to hear how you're using MCP clients in your own workflows!