MCP Server
About
Fetch logs, metrics, traces, and events from the Chronosphere observability platform.
Details
- Author
- chronosphereio
- Downloads
- 230
- Categories
- Cloud Service, Infrastructure, Other
Jump to
- Fetches logs, metrics, traces, and events from Chronosphere
- Also retrieves select Chronosphere entities
- Uses standard Chronosphere authentication (API token)
- Supports Streamable HTTP transport for debugging
- Includes experimental Librechat and agent integrations
Build the binary with make chronomcp, then configure it as an MCP server in your client (e.g., Claude Desktop or Cursor) by providing the path to the binary, a config file, and environment variables CHRONOSPHERE_ORG_NAME and CHRONOSPHERE_API_TOKEN. Alternatively, run directly with make run-chronomcp.
MCP server forChronosphere. Serves tools for fetching logs, metrics, traces, events as well as select entities.
This project usessemverfor 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)
The easiest way to use the MCP server is using our remote hosted server:
You can use either aChronosphere API tokenor 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:
- MCP client you're using (e.g. VS code, codex, cursor, etc)
- What steps you took to attempt authentication
- What error you're seeing.
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 (theTool Namecolumn in theAvailable Toolstable)
- Example value:query_logs_range,render_prometheus_range_query
- Notes: whitespace is ignored; unknown tool names are ignored
{ "mcpServers": { "chronosphere": { "url": "https://<org name>.chronosphere.io/api/mcp/mcp", "headers": { "Authorization": "Bearer <chronosphere api token>", "X-Chrono-MCP-Disable-Tools": "<optional list of tools to disable>" } } } }
This configuration should work for Cursor and VSCode. Leave out theheaderssection to use OAuth instead of a Chronosphere API token. RemoveX-Chrono-MCP-Disable-Toolsto expose all tools.
More details for VSCodehereand Cursorhere
Adding chronosphere MCP server to claude code
claude mcp add -t http \ -H "Authorization: Bearer ${CHRONOSPHERE_API_TOKEN}" \ -H "X-Chrono-MCP-Disable-Tools: <list of tools to disable>" \ chronosphere "https://${CHRONOSPHERE_ORG_NAME}.chronosphere.io/api/mcp/mcp"
You can leave out the Authorization header if you are using OAuth. Once you're in claude type/mcpand select the server to login to trigger the OAuth flow. Remove theX-Chrono-MCP-Disable-Toolsheader to expose all tools.
experimental_use_rmcp_client = true [mcp_servers.chronosphere] url = "https://<org_name>.chronosphere.io/api/mcp/mcp" bearer_token = "<chronosphere api token>"
For oauth login, you must enableexperimental_use_rmcp_client = trueand then runcodex mcp login chronosphere
CHRONOSPHERE_ORG_NAME=<your org> CHRONOSPHERE_API_TOKEN=<your api token> gemini mcp add chronosphere "https://${CHRONOSPHERE_ORG_NAME}.chronosphere.io/api/mcp/mcp" \ -H "Authorization: Bearer ${CHRONOSPHERE_API_TOKEN}" \ -H "X-Chrono-MCP-Disable-Tools: <list of tools to disable>" # Drop the -H authorization header option if you want to use OAuth.
SeeGemini MCP docsfor more information.
{ "mcpServers": { "chronosphere-mcp": { "command": "<PATH/TO/REPO>/bin/chronomcp", "args": [ "-c", "<PATH/TO/REPO>/config.yaml" ], "env": { "CHRONOSPHERE_ORG_NAME": "<your org here>", "CHRONOSPHERE_API_TOKEN": "<your api token here>" } } } }
This MCP server uses the same authentication methods as chronoctl. By default, the Makefile expects the API token to be stored in.chronosphere_api_token.
make run-chronomcp CHRONOSPHERE_ORG_NAME=<your org here> CHRONOSPHERE_API_TOKEN=<your api token here>
The MCP project provides an inspector useful for directly calling tools APIs. To use:
- Start the MCP server with streamable http transportmake run-chronomcp CONFIG_FILE=./config.http.yaml CHRONOSPHERE_ORG_NAME=<your org here>
- Runnpx @modelcontextprotocol/inspector node build/index.js.
- Openhttp://localhost:6274/#resources, fill inhttp://0.0.0.0:8081/mcpin the URL, with transport type Streamable HTTP.
Note: To regenerate this table after tool updates, run:make tools-gen && go run scripts/generate-tools-table.go
You'll need agithub tokenand put it in a .github_release_token file. The token needs at least the followingpermissions
To create a new release, first create a tag:
Then run the following command to perform a dry run of the release:
sh make release-dry-run # verify the release looks good, then run: make release
```
The IBM Instana MCP server enables seamless interaction with the IBM Instana observability platform, allowing you to access real-time observability data directly within your development workflow.
Query and interact with kubernetes environments monitored by Metoro
Interact with the Datadog API to monitor your cloud infrastructure, applications, and logs.
Provides comprehensive Datadog monitoring capabilities through any MCP client.
An MCP server for the Dynatrace observability platform.
Retrieve logs from the Mezmo observability platform.
Kubernetes observability and diagnostics MCP server for cluster health, workload diagnosis, logs, events, topology, audit findings, and remediation actions.
Seamlessly bring real-time production context—logs, metrics, and traces—into your local environment to auto-fix code faster.
Provides access to OpenTelemetry traces and metrics through Logfire.
Civilian situational awareness for AI deployments — real-time risk dashboards, multi-source threat correlation, anomaly detection, and automated alerting for critical infrastructure and enterprise AI systems.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
