Get tools
The following tools return individual resources, such as a single dashboard, monitor, or log.List tools
The following tools list multiple resources, such as a list of all available dashboards, monitors, and log field names.Query tools
The following tools run a query for a particular data type, such as a query for log data.Customize available tools
By default, the Chronosphere MCP server exposes all available tools to your MCP client. You can use theX-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 on this page. Whitespace between entries is ignored,
and unknown tool names are silently ignored.
Claude Code
To disable specific tools when using Claude Code, include theX-Chrono-MCP-Disable-Tools header when adding the MCP server:
-
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:
To expose all tools, omit the
X-Chrono-MCP-Disable-Tools header from the command.Cursor
To disable specific tools when using Cursor, add theX-Chrono-MCP-Disable-Tools
header to the headers section in your mcp.json file:
-
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:
To expose all tools, remove the
X-Chrono-MCP-Disable-Tools line from the headers
section.
