Buddy MCP server

MCP detected

Details

Endpoint: https://mcp.buddy.works/mcp
Transport: streamable-http
Docs: https://buddy.works/docs

Authentication

OAuth 2.0 oauth2 detected

OAuth · resolves from well-known metadata

OAuth 2.0 — self-onboarding

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.

Buddy personal access token api_key declared Get key ↗

Authorization: Bearer <credential>

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.