Chronosphere MCP Server – Observability AI Access
Chronosphere provides a remote Model Context Protocol server for AI-enabled developer tools and agents to query Chronosphere Observability Platform. It exposes read-only access to telemetry data and platform resources so agents can investigate incidents, explain monitor behavior, and help build PromQL queries without mutating Chronosphere configuration.
Overview
Chronosphere MCP Server connects AI agents and AI-enabled developer tools to Chronosphere Observability Platform. It is designed for read-only operational investigation, giving an agent structured access to telemetry and configuration context that would otherwise require manually navigating dashboards, logs, traces, monitors, and metrics.
What the MCP server enables
The server lets an MCP-compatible client query telemetry data such as metrics, logs, traces, and change events. It can also read Chronosphere resources including dashboards, monitors, SLOs, notification policies, recording rules, rollup rules, mapping rules, and shaping rules such as drop rules. Chronosphere documents get, list, and query tools for resources and telemetry, including Prometheus label discovery, PromQL instant and range queries, log range queries, trace listing, monitor status checks, and rendering a Prometheus range query as a PNG.
The server is intentionally read-only. Chronosphere states that it cannot update dashboards, write metrics or logs, delete monitors, or perform other mutation actions through the MCP server.
When to use it
Use this MCP server when an AI agent needs current Chronosphere context while troubleshooting production systems. Practical examples include asking an agent to find error logs with stack traces for a service, explain why a monitor is firing, inspect how an SLO or notification policy is configured, help write PromQL for a service, or identify high-cardinality labels and unused metrics that may affect cost or telemetry hygiene.
Connection and authentication
Chronosphere documents the MCP server as a remote HTTP server at https://TENANT.chronosphere.io/api/mcp/mcp, where TENANT is the Chronosphere tenant name. Authentication can use a Chronosphere API token, generated either as a personal access token or through a service account, by sending it in the Authorization header. Chronosphere also supports OAuth when the MCP client supports OAuth; for OAuth, the header is omitted and the client completes the OAuth flow.
Key considerations
Access follows the identity and permissions associated with the token or OAuth login. Personal access tokens are tied to a user identity and team permissions, while service accounts require administrative access to create. Chronosphere recommends storing API tokens outside configuration files, such as in an environment variable, separate file, or Kubernetes Secret. By default, the server exposes all available tools, but clients can hide selected tools with the X-Chrono-MCP-Disable-Tools header. Query tools can return large result sets, so log and metric range queries should use appropriately short time windows.
Supported Transports
streamable_http
URL: https://${CHRONOSPHERE_TENANT}.chronosphere.io/api/mcp/mcp
Frequently Asked Questions
- When should an AI agent use the Chronosphere MCP Server?
- Use it when an agent needs live, read-only observability context from Chronosphere, such as investigating errors, understanding why a monitor is firing, checking SLOs, exploring logs and traces, or helping write PromQL queries for a service.
- What does the Chronosphere MCP Server add to an AI agent's capabilities?
- It gives the agent structured access to Chronosphere telemetry and resources, including metrics, logs, traces, change events, dashboards, monitors, SLOs, notification policies, shaping rules, recording rules, and rollup rules.
- Can an AI agent change Chronosphere resources through this server?
- No. Chronosphere documents the MCP server as read-only and says it cannot perform mutation actions such as updating dashboards, writing metrics or logs, deleting monitors, or changing platform resources.
- How is authentication configured for the Chronosphere MCP Server?
- The server can be authenticated with a Chronosphere API token in the Authorization header. Tokens can be personal access tokens or service-account tokens. OAuth is also supported when the MCP client supports OAuth, in which case the client omits the API-token header and completes the OAuth flow.
- Which transport should be used for the Chronosphere MCP Server?
- Use the remote HTTP MCP endpoint at https://TENANT.chronosphere.io/api/mcp/mcp. Configure the tenant-specific URL in MCP clients such as Claude Code or Cursor, and pass the API token through a secure environment variable or secret rather than hard-coding it.