Chronosphere MCP Server

MCP server for Chronosphere. Serves tools for fetching logs, metrics, traces, events as well as select entities.

This project uses semver for release versions. We have not graduated to 1.0, so breaking changes may occur for minor version bumps.

MCP config with popular hosts (claude desktop, cursor)

Remote Server

The easiest way to use the MCP server is using our remote hosted server:

Auth

You can use either a Chronosphere API token or OAuth with the Chronosphere MCP server. To use MCP with OAuth, the MCP client must support OAuth.

OAuth support is new and have not been tested with all clients. If it does not work for you, please raise the issue to Chronosphere support in slack with the following information:

1. MCP client you’re using (e.g. VS code, codex, cursor, etc)
2. What steps you took to attempt authentication
3. What error you’re seeing.

Header-based configuration

Some MCP hosts let you attach custom HTTP headers to requests sent to the MCP server. The Chronosphere MCP server supports the following user-facing headers.

Disable tools (X-Chrono-MCP-Disable-Tools)

Use this header to hide specific tools from the tool list exposed to your MCP client.

• Format: comma-separated list of MCP tool names (the Tool Name column in the Available Tools table)
• Example value: query_logs_range,render_prometheus_range_query
• Notes: whitespace is ignored; unknown tool names are ignored

Enable writes (X-Chrono-MCP-Enable-Writes)

Write tools are hidden and cannot be called by default. The server operator must first permit writes with server.tools.enableWrites: true. HTTP and SSE clients must additionally set this header to true; the header cannot override a disabled server setting. Other values do not enable writes.

Stdio has no request headers, so the server setting alone enables writes for that transport. The Chronosphere credentials used by the server must still authorize the underlying API operation.

Cursor/VSCode

{
    "mcpServers": {
        "chronosphere": {
            "url": "https://.chronosphere.io/api/mcp/mcp",
            "headers": {
                "Authorization": "Bearer ",
                "X-Chrono-MCP-Disable-Tools": ""
            }
        }
    }
}

This configuration should work for Cursor and VSCode. Leave out the headers section to use OAuth instead of a Chronosphere API token. Remove X-Chrono-MCP-Disable-Tools to expose all tools.

More details for VSCode here and Cursor here

Claude code

Adding chronosphere MCP server to claude code

claude mcp add -t http \