buddy.works
Buddy provides infrastructure for software development workflows, including sandboxes, hosting, repositories, domains, package artifacts, and CI/CD-style automation. It offers these capabilities through a web platform plus programmatic interfaces for developers and AI agents.
Buddy exposes three developer integration surfaces on buddy.works subdomains: a REST API at api.buddy.works, an OAuth-protected remote MCP server at mcp.buddy.works/mcp, and the bdy CLI; the API and MCP accept Buddy bearer tokens, and MCP also supports self-onboarding OAuth discovery/DCR.
- Buddy MCP serverdetected
- Buddy REST APIdiscovered
- Buddy REST APIdeclared
- bdy CLIdeclared
Sign in to Buddy Security and create a personal access token with only the scopes you need. Use it as a bearer token in the Authorization header for the API and MCP server, or for the CLI run bdy login --token <token>; BUDDY_TOKEN is the non-interactive fallback for CI.
Point your MCP client at the server URL and approve access in the browser. The server supports OAuth Dynamic Client Registration (RFC 7591), so the client registers itself automatically — no developer-portal app, client_id, or client_secret to create.
conventions · 8/8 published
- integrations.json✓https://buddy.works/.well-known/integrations.json
- llms.txt✓https://buddy.works/llms.txt
- API catalog✓https://buddy.works/.well-known/api-catalog
- OpenAPI document✓https://buddy.works/openapi.json
- MCP server card✓https://mcp.buddy.works/mcp
- OAuth protected resource✓https://buddy.works/.well-known/oauth-protected-resource
- Agent card✓https://mcp.buddy.works/mcp
- Agent skills✓https://buddy.works/.well-known/agent-skills/index.json
Publish these signals → /publishing