Skip to main content
The following table includes tools that the Chronosphere MCP server supports interacting with. After authenticating, you can submit read-only queries to Observability Platform from within your code editor.
Tool typeEndpointDescription
APIget_classic_dashboardGet classic dashboards tools.
APIget_dashboardGet dashboards tools.
APIget_drop_ruleGet drop rules tools.
APIget_mapping_ruleGet mapping rules tools.
APIget_monitorGet monitors tools.
APIget_notification_policyGet notification policies tools.
APIget_recording_ruleGet recording rules tools.
APIget_rollup_ruleGet rollup rules tools.
APIget_sloGet SLO tools.
APIlist_classic_dashboardsList classic dashboards tools.
APIlist_dashboardsList dashboards tools.
APIlist_drop_rulesList drop rules tools.
APIlist_mapping_rulesList mapping rules tools.
APIlist_monitorsList monitors tools.
APIlist_notification_policiesList notification policies tools.
APIlist_recording_rulesList recording rules tools.
APIlist_rollup_rulesList rollup rules tools.
APIlist_sloList SLO tools.
Eventsget_events_metadataList properties you can query on events.
Eventslist_eventsList events from a given query.
Eventslist_events_label_valuesList values for a given label name.
Logsget_logGet a full log message by its ID. The ID is the unique identifier for the log.
Logsget_log_histogramGet histogram of logs from a given query.
Logslist_log_field_namesList field names of logs.
Logslist_log_field_valuesList field values of logs.
Logsquery_logs_rangeExecute a range query for logs. This endpoint returns logs as either timeSeries or gridData. This query might return a large amount of data, so use a shorter range such as one hour.
Metricslist_prometheus_label_namesReturns the list of label names (keys) available on metrics that match the given selectors. Use this tool when you need to discover what labels are available on specific metrics or services.
Metricslist_prometheus_label_valuesReturns the list of values for a specific label name, optionally filtered by selectors. Use this tool when you know the label name and want to discover what values it has across your metrics.
Metricslist_prometheus_seriesReturns the complete time series (full label sets with all key-value pairs) that match the given selectors. Each result shows the exact combination of labels for an active time series.
Metricslist_prometheus_series_metadataReturns metadata for the given metric in the form of type, help, and unit.
Metricsquery_prometheus_instantEvaluates a Prometheus instant query at a single point in time.
Metricsquery_prometheus_rangeExecutes a Prometheus PromQL query over a specified time range and returns time series data points in JSON format. Supports standard PromQL syntax plus Chronosphere custom functions.
Metricsrender_prometheus_range_queryEvaluates a Prometheus expression query over a range of time and renders it as a PNG image.
Monitorslist_monitor_statusesLists the current status of all monitors. Returns monitor statuses with alert states and optional signal and series details.
Traceslist_tracesList traces from a given query.

​
Customize available tools

By default, the Chronosphere MCP server exposes all available tools to your MCP client. You can use the X-Chrono-MCP-Disable-Tools header to selectively hide specific tools from your client’s tool list. The header accepts a comma-separated list of tool names. Tool names must match the endpoint names listed in the tools table above. Whitespace between entries is ignored, and unknown tool names are silently ignored.

​
Claude Code

To disable specific tools when using Claude Code, include the X-Chrono-MCP-Disable-Tools header when adding the MCP server: 
claude mcp add --transport http chronosphere "https://TENANT.chronosphere.io/api/mcp/mcp" \
--header "Authorization: API_TOKEN" \
--header "X-Chrono-MCP-Disable-Tools: TOOLS"
Replace the following:
  • TENANT: The name of your Observability Platform tenant.
  • API_TOKEN: The API token generated from your service account. Chronosphere recommends storing your API token in a separate file or Kubernetes Secret and calling it using an environment variable, such as $API_TOKEN.
  • TOOLS: A comma-separated list of tool names you want to hide. For example: 
    query_logs_range, render_prometheus_range_query
To expose all tools, omit the X-Chrono-MCP-Disable-Tools header from the command.

​
Cursor

To disable specific tools when using Cursor, add the X-Chrono-MCP-Disable-Tools header to the headers section in your mcp.json file: 
{
  "mcpServers": {
    "chronosphere": {
      "url": "https://TENANT.chronosphere.io/api/mcp/mcp",
      "headers": {
        "Authorization": "Bearer API_TOKEN",
        "X-Chrono-MCP-Disable-Tools": "TOOLS"
      }
    }
  }
}
Replace the following:
  • TENANT: The name of your Observability Platform tenant.
  • API_TOKEN: The API token generated from your service account. Chronosphere recommends storing your API token in a separate file or Kubernetes Secret and calling it using an environment variable, such as $API_TOKEN.
  • TOOLS: A comma-separated list of tool names you want to hide. For example: 
    query_logs_range, render_prometheus_range_query
To expose all tools, remove the X-Chrono-MCP-Disable-Tools line from the headers section.