Bronto launches hosted MCP server with OAuth-based access

Authored by Ciaran McGauran, the post announces Bronto's hosted MCP server, a follow-up to the earlier local MCP server offering. The hosted model eliminates the need for users to clone a repo, manage a local server process, or distribute API keys — instead, administrators enable MCP login in the Bronto UI, select which authentication methods are allowed, and users sign in through Bronto's standard auth flow. MCP clients complete a browser-based OAuth flow, and Bronto issues and validates the MCP access tokens. This approach is positioned for teams that want centralized access control and a SaaS-like sign-in experience, and it also unlocks Bronto in platforms that only support remote MCP endpoints, such as AWS DevOps Agent.

At the tool level, clients retain access to the same Bronto capabilities: datasets, keys, values, log search, and metrics.

At the tool level, clients retain access to the same Bronto capabilities: datasets, keys, values, log search, and metrics. The post uses CDN log analysis as a primary demonstration, running example prompts against Claude Opus 4.6. The illustrated workflows cover identifying production CDN datasets, surfacing elevated 5xx responses grouped by host, path, and status code, comparing response-time metrics across time windows to find regressions, analyzing cache miss rate trends over 24 hours, and detecting unusual request-volume spikes by client IP, user agent, host, and path. The post notes that the local server remains the better fit for individual developers doing local experimentation, while the hosted version is suited to teams needing managed authentication and administrative oversight.

Key facts

1. 01Bronto now offers a hosted MCP server endpoint in addition to its existing local MCP server.
2. 02Teams enable MCP access in the Bronto UI and authenticate via OAuth, SSO, or Google Social — no API key distribution required.
3. 03Administrators can centrally control which sign-in methods are allowed and who can connect.
4. 04The hosted endpoint supports environments that only allow remote MCP, such as AWS DevOps Agent.
5. 05MCP clients complete a browser-based OAuth flow; Bronto issues and validates the access tokens.
6. 06Clients retain access to Bronto datasets, keys, values, log search, and metrics through the hosted endpoint.
7. 07Example prompts in the post use Claude Opus 4.6 against CDN log data for operational investigations.

Topics