MCP with Claude
Drive your Buda agents from Claude Desktop over the Model Context Protocol — authenticate with an API key and call Buda right from your chat.
You shouldn't have to leave the chat you're already in. Buda exposes a Model Context Protocol (MCP) server, so Claude Desktop — and any MCP-capable client — can call your Buda account directly: list agents, kick off tasks, and read results without switching apps.
What MCP is
MCP is an open standard that lets AI clients call external tools and read external data. Buda's MCP endpoint wraps Buda's public API as MCP tools, so an MCP client can operate your account on your behalf, authenticated with your API key.
Configure Claude Desktop
Create an API key. In Buda, open Settings → API keys and generate one. Copy it now — you won't see it again. See Authentication for details.
Add Buda to your MCP config. In Claude Desktop's MCP server configuration, add an entry pointing at Buda's endpoint:
{
"mcpServers": {
"buda": {
"url": "https://buda.im/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}Restart Claude Desktop so it picks up the new server, then confirm Buda's tools appear and start asking it to act on your Buda account.
Authenticate with an API key
Buda's MCP server uses bearer authentication — your API key in the Authorization header, exactly as shown above. The same key powers Buda's REST API, and the MCP server acts as the user that owns the key. Treat it like a password: keep it out of shared configs and rotate it if it leaks.
Anyone with your API key can act as you in Buda. Store it securely and revoke it from Settings → API keys if it's ever exposed.
Available tools and resources
The MCP server is generated from Buda's public OpenAPI surface, so the tools track the REST API — listing and managing agents, starting tasks, and reading their output. For the authoritative list of operations and full request and response shapes, see the MCP reference and the REST API docs.