Chronosphere MCP Server
Query logs, metrics, traces, and events from Chronosphere via the MCP protocol.
Data last scanned today · Reviewed today
Overview
The Chronosphere MCP server provides tools to interact with Chronosphere observability data directly from within AI assistants. It enables users to fetch logs, metrics, traces, events, and select entities by configuring the server via API tokens or OAuth. The server architecture emphasizes security controls for users, including the ability to disable specific tools through header-based configuration and an opt-in mechanism for write operations. Users must explicitly enable write access via server-side settings and specific HTTP headers, as these capabilities are restricted by default.
Our verdict
With a security score of 43/100, this server is classified as high-risk. This rating stems primarily from the fact that it is a community-maintained project rather than an official vendor release, and critical aspects such as its authentication method and read-only mode behavior have not yet been editorially reviewed. Given the potential for unauthorized data exposure and the pre-1.0 development status where breaking changes are frequent, this tool should be used with caution in environments handling sensitive observability data.
- Zero direct dependencies reduce the supply-chain surface area.
- Explicit header-based control to disable specific MCP tools.
- Granular opt-in process for sensitive write operations.
- Apache-2.0 open source licensing.
- High-risk score due to lack of official vendor maintenance.
- Authentication methods have not yet been editorially reviewed.
- Pre-1.0 release status may result in frequent breaking changes.
- Read-only mode implementation is currently unverified.
Tools
| Tool | Description | Risk |
|---|---|---|
| get_classic_dashboard | Get classic-dashboards resource | low |
| get_dashboard | Get dashboards resource | low |
| get_drop_rule | Get drop-rules resource | low |
| get_mapping_rule | Get mapping-rules resource | low |
| get_monitor | Get monitors resource | low |
| get_notification_policy | Get notification-policies resource | low |
| get_recording_rule | Get recording-rules resource | low |
| get_rollup_rule | Get rollup-rules resource | low |
| get_slo | Get slos resources | low |
| list_classic_dashboards | List classic-dashboards resources | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›What authentication methods does the server support?
The server supports authentication via either a Chronosphere API token or OAuth. Note that OAuth support is considered new and may not be compatible with all MCP clients.
›Can I prevent specific tools from appearing in my MCP client?
Yes, you can hide specific tools by providing a comma-separated list of tool names in the X-Chrono-MCP-Disable-Tools HTTP header.
›Are write tools enabled by default?
No, write tools are hidden and disabled by default. To use them, the server operator must enable them via the server configuration, and HTTP or SSE clients must additionally set the X-Chrono-MCP-Enable-Writes header to true.
›Is this project considered stable?
The project follows semantic versioning and has not yet reached version 1.0. Consequently, breaking changes may occur during minor version updates.
Changelog
Badge
Maintain this server? Add the live badge to your README.