MCP Tool Directory

Generates a ClickHouse SQL query from natural language for creating metrics visualizations in Better Stack Dashboards. Returns a query optimized for charts and dashboards that can be directly used in the Dashboard builder UI. **Note**: The generated query uses Better Stack's query syntax and will not work directly in raw ClickHouse.

Create a new application in Better Stack. Returns the created application details including ID, ingestion token, ingesting host URL, retention settings, and platform-specific integration documentation links with next steps for configuration

Create a secure cloud connection for direct ClickHouse query access to logs, spans, and metrics data. Returns connection credentials (host, port, username, password), sample queries for each data type, and cURL command examples. Connections expire after 1 hour by default

Create a new dashboard. Optionally use a template to start with pre-configured charts. Call get_chart_building_instructions for guidance on dashboard structure and layout. Optionally specify a source_id to preconfigure the dashboard with that source. Returns the new dashboard ID which can be used with add_chart_to_dashboard to add charts

Create a new log source in Better Stack. Returns the created source details including ID, ingestion token, ingesting host URL, retention settings, and platform-specific integration documentation links with next steps for configuration

Edit an existing chart name, query, type, or settings. Only provide the fields you want to change. **IMPORTANT: If changing the query:** If you haven't already verified the new query by previewing with `telemetry_chart` (which runs the query and reports errors automatically), test it with `telemetry_query` first before updating the chart. Call get_chart_building_instructions for chart type and settings reference. Use get_dashboard_details first to find the chart ID

Export a dashboard configuration as JSON. Returns the complete dashboard data structure including charts, sections, presets, and settings

Get comprehensive details of a specific application including its configuration, retention settings, ingestion details, custom bucket settings (if configured)

Get comprehensive instructions for building charts and dashboards, including chart types, units, axis settings, column mapping, legend placement, layout tips, and common mistakes. Call this before creating or editing charts

Get detailed information about a specific chart including its SQL queries, configuration, and settings. Use get_dashboard_details first to find the chart ID

Get detailed information about a specific dashboard including its charts, sections, layout, and configuration. Use this to understand a dashboard structure before modifying it

Get comprehensive details of a specific error including its type, message, call site information, first occurrence, and current state (unhandled, unresolved, ignored, resolved, or reoccurred)

Get comprehensive instructions for building SQL ClickHouse queries for error tracking, including both error patterns (metrics) and individual exceptions. Explains when to use each source and provides examples for common use cases

Get comprehensive details about a specific metric. Returns metric overview (data points, active series, available aggregations), definition (SQL expression or JSON path), example queries for different aggregation functions, and Prometheus tags (for pure metrics). Essential for understanding how to query and use a metric

Get instructions for building SQL ClickHouse queries for metrics, including available metrics, aggregations, and examples

Get complete metrics and cardinality for a source. Returns a table of all available metrics (pure and computed) with their names, types, data points count, and active series count

Get instruction for building SQL ClickHouse queries, including fields, aggregations, and examples, that can be used for running queries using direct connections to the ClickHouse proxy

Get comprehensive instructions for building SQL ClickHouse queries for session replays. Explains data structure, provides examples for listing replays, finding replays linked to errors, and filtering by user/environment

Get comprehensive details of a specific source including its configuration, retention settings, ingestion details, custom bucket settings (if configured)

Get complete field catalog for a logs or spans source. Returns a table of all queryable fields with their paths and data types. Essential for understanding what fields can be queried for building custom queries

Import a dashboard from JSON configuration. Creates a new dashboard with the provided data structure

List all available applications in a paginated table format. Returns application ID, name, platform type, team, status (active/paused), data region, and creation date

List all available storage clusters for a specific team. Returns a table with cluster IDs, names, and regions. Used primarily for creating cloud connections to query logs and metrics data directly via ClickHouse

List all available dashboard templates in a paginated table format. Returns template ID, name, description, and other metadata

List all available dashboards in a paginated table format. Returns dashboard ID, name, creation date, and last updated date

List all available data regions and clusters for application and source creation. Returns a table with region IDs (to use when creating applications or sources), display names, types (Region or Cluster), and geographical locations. Includes usage instructions for both standard regions and custom clusters

List all releases for a specific application in a paginated table format. Returns release reference, environments, first seen, and last seen timestamps

List all available sources in a paginated table format. Returns source ID, name, platform type, team, status (active/paused), data region, and creation date

List all available teams in Better Stack Logs. Returns a table with team IDs and names, grouped by organization

Move one or more charts to new positions on a dashboard. Validates the final layout for overlaps, allowing swaps and complex rearrangements. All moves are applied atomically - if any move is invalid, none are applied. Grid is 12 columns wide