MCP · Model Context Protocol

Agentic control plane for security and audit

Burgus exposes tenant operations through Streamable HTTP MCP at https://mcp.burgus.ai/mcp, protected by Cloudflare Access. Registration and onboarding happen in the browser at /register — not via MCP tools.

Discovery

• Public overview: mcp.burgus.ai
• Agent index: /.well-known/agent-index.json
• API catalog (RFC 9727): /.well-known/api-catalog
• Commercial catalog tool: commercial_product_catalog

Typical workflow

1. Sign in at mcp.burgus.ai/register (email PIN, SSO, or service token)
2. Paste MCP config into Cursor (Settings → MCP) or your agent runtime
3. customer_add_key — bring your upstream provider API keys
4. Point SDK base_url at assigned {provider}.llmproxy.burgus.ai hostnames
5. Query audit, platform alerts, content policy, and behavioral tools via MCP

Authentication

MCP secure tools are scoped to your tenant via Access identity. For automation, use CF-Access-Client-Id and CF-Access-Client-Secret service token headers. LLM traffic uses provider-native API keys on the data plane — not the MCP session.