This project uses [semver](https://semver.org/) for release versions. We have not graduated to 1.0, so breaking changes may occur for minor version
If you already use Chronosphere MCP, the chronosphere mcp mcp server is the piece that lets your assistant work with it directly. This project uses semver for release versions. We have not graduated to 1.0, so breaking changes may occur for minor version bumps.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Format — comma-separated list of MCP tool names (the Tool Name column in the Available Tools table)Notes — whitespace is ignored; unknown tool names are ignoredGroup — Tool Nameconfigapi — get_classic_dashboardevents — get_events_metadatalogs — get_logmetrics — list_prometheus_label_namesmetric_usage — list_metric_usages_by_label_namemonitors — list_monitor_statusestraces — list_tracesAuth — You can use either a Chronosphere API token or OAuth with the Chronosphere MCPReleases — We use goreleaser to manage releasesConfiguration is passed through the environment: CHRONOSPHERE_ORG_NAME, CHRONOSPHERE_API_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Chronosphere MCP's toolset — Format, Notes, Group and 9 more — is a fair guide to whether it matches your workflow. It is maintained by chronosphereio; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Chronosphere MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Format | comma-separated list of MCP tool names (the **Tool Name** column in the [Available Tools](#available-tools) table) |
| Notes | whitespace is ignored; unknown tool names are ignored |
| Group | Tool Name |
| configapi | get_classic_dashboard |
| events | get_events_metadata |
| logs | get_log |
| metrics | list_prometheus_label_names |
| metric_usage | list_metric_usages_by_label_name |
| monitors | list_monitor_statuses |
| traces | list_traces |
| Auth | You can use either a [Chronosphere API token](https://docs.chronosphere.io/tooling/api-info#create-an-api-token) or OAuth with the Chronosphere MCP server. To use MCP with OAuth, the MCP client must support OAuth. |
| Releases | We use [goreleaser](https://goreleaser.com/) to manage releases. |
{
"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>"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| CHRONOSPHERE_ORG_NAME | Configuration value read at startup. | Optional |
| CHRONOSPHERE_API_TOKEN | Credential the server authenticates with. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.