NeuralTrust has been recognized by Gartner → Read more

Connect Better Stack MCP to your AI agents, securely.

One secured endpoint for every Better Stack call your AI agents make, scoped per user, inspected, and logged.

Select the tools your AI agents can call

120 tools from the Better Stack MCP schema.

Showing 120 tools

  • Execute queryreadExecutes a ClickHouse SQL query against telemetry data, including logs, spans, metrics, exceptions and replays.
  • Render chartreadExecutes a ClickHouse SQL query and renders the result as a line, bar or pie chart directly in the conversation.
  • Plan query windowsreadEstimates how many rows a long-range query reads and, when it is too much for one call, splits the time range into windows.
  • Get query instructionsreadProvides instructions for building logs and spans queries to run via the query tools.
  • Get explore logs query instructionsreadProvides instructions for writing queries for the Explore logs page and live-tail charts.
  • Search documentationreadSearches Better Stack documentation and returns the contents of relevant articles.
  • List incidentsreadFinds incidents by date, status, monitor or other criteria.
  • Get incident detailsreadShows full incident information including error messages and screenshots.
  • Get incident timelinereadDisplays the complete incident history.
  • Get incident commentsreadRetrieves the comments on an incident.
  • Create incident commentwriteAdds a team collaboration comment to an incident.
  • Acknowledge incidentwriteTakes ownership of an incident, which stops escalations.
  • Resolve incidentwriteMarks an incident as fixed.
  • Reopen incidentwriteReopens a resolved incident, within 24 hours of resolution.
  • Create incidenthigh riskReports a new incident with context and metadata, starting the real response process.
  • Escalate incidenthigh riskRoutes an incident to users, teams, schedules or policies, reaching real people.
  • Get on-call detailsreadShows who is on call for a calendar, right now or at a given time.
  • List on-call calendarsreadProvides information about on-call calendars and rotations.
  • List on-call eventsreadLists upcoming shifts and schedule changes.
  • Get on-call event detailsreadFetches the details for a specific on-call event.
  • Get on-call rotation detailsreadExplains how a rotation is configured.
  • Get available incident escalation policiesreadShows the escalation targets available for a given incident.
  • List escalation policiesreadLists the configured escalation rules and their steps.
  • Get escalation policy detailsreadProvides detailed information about an escalation policy.
  • List severitiesreadShows the incident severity levels and their configurations.
  • Get severity detailsreadExplains a specific severity's settings, including its notification behaviour.
  • List monitorsreadShows all monitors with filtering options.
  • Get monitor detailsreadProvides a monitor's configuration, status and settings.
  • Get monitor availabilityreadCalculates SLA summaries and uptime percentages.
  • Get monitor response timesreadAnalyses performance metrics and trends for a monitor.
  • List heartbeatsreadShows all heartbeat monitors and their status.
  • Get heartbeat detailsreadProvides a heartbeat's configuration and recent activity.
  • Get heartbeat availabilityreadTracks uptime for scheduled tasks.
  • Create monitorwriteCreates a monitor to track the availability of a website, host or service.
  • Create heartbeatwriteCreates a heartbeat that alerts when a cron job or background task stops reporting.
  • List status pagesreadShows all status pages.
  • Get status page detailsreadProvides a status page's configuration and current status.
  • Get status page resourcesreadLists the monitors and heartbeats displayed on each page.
  • Get status page sectionsreadLists the sections of a status page.
  • List status page reportsreadShows the status reports for a specific page.
  • List status page report updatesreadLists the updates for a specific report.
  • Get status page report update detailsreadProvides details for a specific report update.
  • Update status pagewriteUpdates status page settings such as company name, theme, layout or custom domain.
  • Add status page resourcewriteAdds a monitor, heartbeat or group to a status page.
  • Update status page resourcewriteChanges a resource's public name, description, widget type or placement.
  • Create status page sectionwriteCreates a section to group status page resources under a heading.
  • Update status page sectionwriteRenames a section or moves it to a new position.
  • Remove status page resourcehigh riskRemoves a resource from a status page, changing what the public sees.
  • Remove status page sectionhigh riskRemoves a section and its resources from a status page.
  • Create status page reporthigh riskCreates a public incident report or maintenance announcement on a status page.
  • Create status page report updatehigh riskAdds a public update to an ongoing status page report.
  • List sourcesreadShows all log sources with their status and configuration.
  • Get source detailsreadProvides detailed source configuration and ingestion settings.
  • Get source fieldsreadDiscovers the fields available for querying logs and spans.
  • Create sourcewriteCreates a new log source with an integration guide.
  • List dashboardsreadLists all dashboards with their ID, name, creation and update dates.
  • List dashboard groupsreadLists the groups dashboards are organised into and how many each holds.
  • Get dashboard detailsreadShows detailed dashboard information including charts, sections, layout and configuration.
  • List dashboard templatesreadLists all available dashboard templates with ID, name, description and platform.
  • Export dashboardreadExports a dashboard's full configuration, including charts, sections and settings, as JSON.
  • Create dashboardwriteCreates a dashboard, optionally from a template or with a specific source.
  • Configure dashboardwriteUpdates a dashboard's name or source eligibility.
  • Set dashboard variablewriteCreates or updates a dashboard variable, a toolbar filter referenced in chart queries.
  • Remove dashboard variablewriteRemoves a dashboard variable by name.
  • Import dashboardwriteImports a new dashboard from a JSON configuration.
  • Remove dashboardhigh riskPermanently removes a dashboard and all its associated charts.
  • Get chart detailsreadShows a chart's configuration, SQL queries and settings.
  • Get chart building instructionsreadProvides guidance on chart types, units, axis settings and best practices.
  • Get dashboard query instructionsreadProvides instructions for writing the ClickHouse queries used inside dashboard charts.
  • Add chart to dashboardwriteAdds a new chart with a SQL query to a dashboard.
  • Configure chartwriteUpdates a chart's name, type, query or settings.
  • Add dashboard sectionwriteAdds a section divider to organise charts into groups.
  • Configure dashboard sectionwriteUpdates a section's title, description or collapsed state.
  • Move chartswriteRearranges chart positions on the dashboard grid.
  • Remove charthigh riskPermanently removes a chart from its dashboard.
  • Remove dashboard sectionhigh riskRemoves a section divider from a dashboard.
  • List chart alertsreadLists chart alerts with their ID, name, chart and status.
  • Get chart alert detailsreadShows an alert's configuration, SQL queries and current incident info.
  • Get chart alert instructionsreadProvides instructions for creating and configuring chart alerts, including alert types and operators.
  • Create chart alertwriteCreates an alert on an existing chart, supporting threshold, relative and anomaly detection types.
  • Configure chart alertwriteUpdates an existing chart alert's configuration.
  • Remove chart alerthigh riskPermanently removes a chart alert, ending the monitoring it provided.
  • Pause or resume chart alerthigh riskPauses or unpauses a chart alert, silencing monitoring without removing it.
  • List explorationsreadLists saved explorations with their ID, name, chart type, sources and group.
  • Get exploration detailsreadShows an exploration's sources, chart type, variables, saved time range and query.
  • Set exploration variablewriteCreates or updates an exploration variable, most often to change which sources the exploration queries.
  • Remove exploration variablewriteRemoves an exploration variable by name.
  • Get metrics schemareadShows the available metrics with their data points and series count.
  • Get metric detailsreadExplains how to query and use a specific metric, with examples.
  • Get metric query instructionsreadProvides instructions for building metrics queries to run via the query tools.
  • List metric expressionsreadLists the extract-metrics-from-logs rules on a source.
  • Create metric expressionwriteCreates a new metric or label extracted from log fields.
  • Update metric expressionwriteUpdates a metric expression's name, SQL expression, type or aggregations.
  • Remove metric expressionhigh riskDeletes a metric expression from a source, stopping that metric being produced.
  • List data regionsreadShows the regions available for storing data.
  • List clustersreadLists the storage clusters available for direct data access.
  • List teamsreadShows the teams with telemetry platform access.
  • Create cloud connectionhigh riskCreates temporary credentials for direct ClickHouse access, bypassing this server and reaching the data store itself.
  • List applicationsreadShows all error tracking applications with their status and configuration.
  • Get application detailsreadProvides detailed configuration, ingestion settings and available data tables, including the DSN.
  • List releasesreadShows all releases for an application with first and last seen timestamps.
  • List errorsreadLists error patterns with occurrence counts, affected users and current state, filterable by state, release, environment or time range.
  • Get error detailsreadShows the error type, message, call site, first occurrence and current state: unhandled, unresolved, ignored, resolved or reoccurred.
  • Get error commentsreadReads the conversation on an error, including Better Stack comments, replies in its Slack thread and comments synced from a linked Linear issue.
  • Get replays query instructionsreadProvides instructions for querying session replay data, including the fields and patterns for finding replays linked to errors or users.
  • Get errors query instructionsreadDocuments the two-layer errors and exceptions architecture, available columns, query patterns and best practices.
  • Create applicationwriteCreates a new error tracking application with a platform-specific integration guide.
  • Edit applicationwriteRenames an application, pauses or resumes ingestion, or sets its VRL transformations including the exception grouping program.
  • Create releasewriteRegisters a release so it appears as soon as it deploys, before its first error arrives.
  • Update error statewriteMarks an error as resolved, ignored or unresolved, with optional notification settings.
  • Link error to issuewriteLinks an error to an existing Linear issue or Jira work item, then posts every state change as a comment on it.
  • Create issue for errorwriteCreates a Linear issue or Jira work item for an error through the team's integration and links the two.
  • Unlink error from issuewriteRemoves the link between an error and a Linear, Jira or GitLab issue, leaving the issue untouched.
  • Create error commentwritePosts a comment on an error, marked as posted via MCP. If the error is linked to a Linear issue that syncs comments, it is posted there too.
  • Remove releasehigh riskPermanently removes a release. One that still receives errors is detected again with its next event.
  • List team membersreadShows the members of a team, including pending invitations, with each member's email, name and role.
  • List organization rolesreadLists the roles in the organization with their IDs, including custom roles.
  • Invite team memberhigh riskInvites someone to a team by email address, with an optional role.
  • Change team member rolehigh riskChanges an existing team member's role.
  • Remove team memberhigh riskRemoves a member from a team, or cancels a pending invitation.

What Better Stack MCP exposes

Better Stack MCP groups its 120 tools into 14 categories, each with a suggested starting policy.

All 120 tools as JSON, ready to paste.

CategoryCoversAccessSuggested policy
Error TrackingError tracking applications and their ingestion settings, releases, error patterns with occurrence counts and state, linking errors to Linear or Jira issues, error comments, and query instructions for errors and session replaysRead / WriteCreate issue for error and Link error to issue reach into Linear or Jira, and error comments sync through to a linked Linear issue, so a comment written here appears in another system
Status PagesStatus pages and their settings, the resources and sections displayed on them, and incident reports and maintenance announcements with their updatesRead / WriteA status page report is a public statement to customers. Unlike some servers here, nothing forces a human into the loop, so the approval has to come from the gateway
DashboardsListing dashboards, groups and templates, dashboard detail with charts and layout, creating from a template or source, configuring, dashboard variables, and JSON export and importRead / WriteRemove dashboard takes every chart on it with it. Export dashboard pulls the full configuration including chart SQL, which carries the shape of the underlying data
ChartsChart detail with its SQL queries and settings, chart building and dashboard query instructions, adding, configuring and removing charts, dashboard sections, and rearranging chart positionsRead / WriteChart removal is permanent. Get chart building instructions and Get dashboard query instructions should be read before writing any chart query
IncidentsCreating and listing incidents, full detail with error messages and screenshots, timeline, comments, acknowledging, escalating, resolving and reopeningRead / WriteEscalate incident routes to users, teams, schedules or policies and reaches real people. Reopen only works within 24 hours of resolution
On-call & EscalationWho is on call now or at a given time, calendars and rotations, upcoming shifts and schedule changes, escalation policies and their steps, available escalation targets, and severity levels with their notification settingsReadEntirely read-only: this server reads the on-call configuration but changes it only through incident escalation
Monitors & HeartbeatsListing and detailing monitors and heartbeats, creating them, SLA and uptime summaries and response time trendsRead / WriteCreation only; there is no tool to pause or delete a monitor, so an agent cannot silence uptime checking here
Chart AlertsListing chart alerts with their status, alert detail with SQL and current incident info, creation instructions, and creating, configuring, removing and pausing or resuming alertsRead / WritePausing an alert silences monitoring without deleting anything, which is the failure mode where nothing looks broken until something is missed
MetricsThe metrics schema with data points and series counts, metric detail with example queries, metric query instructions, and the rules that extract metrics and labels from log fieldsRead / WriteMetric expressions change what is extracted going forward; removing one stops a metric being produced without touching any dashboard that reads it
Query & AnalysisExecuting ClickHouse SQL against logs, spans, metrics, exceptions and replays, rendering a result as a chart, planning query windows for long ranges, query-writing instructions, and searching Better Stack documentationReadExecute query reaches the raw telemetry, which routinely contains customer data in log lines. Plan query windows exists because a long-range query can read more than one call can handle
Team ManagementListing team members including pending invitations with their email, name and role, listing organization roles including custom ones, inviting members, changing roles and removing membersRead / WriteThese are identity and access changes. An agent that can invite a member and set its role can widen access to everything else on this list
SourcesListing log sources with status and configuration, source detail including ingestion settings, creating sources with integration guides, and discovering the fields available for queryingRead / WriteGet source fields is the prerequisite for writing a correct query. Source detail exposes ingestion settings
ExplorationsSaved Explore queries: listing them with chart type, sources and group, their detail with variables and saved time range, and setting or removing an exploration variableRead / WriteAn exploration variable most often decides which sources the exploration queries, so changing it changes what a saved query reads
InfrastructureData regions available for storing data, storage clusters for direct access, teams with telemetry platform access, and creating temporary credentials for direct ClickHouse accessRead / WriteCreate cloud connection hands out credentials that bypass this server entirely and reach the data store directly. Restrict it and log every issuance

Connect Better Stack MCP to your AI agent

Four steps, under ten minutes.

  1. 01

    Sign in to NeuralTrust

    Open the NeuralTrust platform, sign in and go to Getting started, then Connect your tools.

    Sign in to NeuralTrust
  2. 02

    Choose your agent

    When asked which agent you use, pick Claude Code, Codex, Cursor, Windsurf, Copilot or your own code.

    Choose your agent
  3. 03

    Connect Better Stack

    Find Better Stack in the tool list and connect it.

    Connect Better Stack
  4. 04

    Connect your agent

    Follow the steps on screen to add the config to your agent, then send the test prompt.

    Connect your agent

Permissions down to the single tool

You do not allow Better Stack MCP or block it. You allow the exact tools each agent can call, one by one.

Better Stack MCP120 TOOLS AVAILABLE
Code review agent4 tools, read only
Issue triage bot9 tools
Platform team assistantall 120 tools
  • Tool by toolConnecting the server is not the unit of access. Each tool is granted on its own.
  • Default denyA tool you have not enabled is never exposed to the agent.
  • Approval on writesTools that change or delete things can require a human to confirm.

Is Better Stack MCP secure?

One endpoint instead of raw credentials. Every call is checked against policy and logged.

AI agentsConnect through your MCP client configuration.NeuralTrustApply controls based on your configuration.Better Stack MCP120 documented tools, all exposed by default. The X-MCP-Tools-Only and X-MCP-Tools-Except headers allowlist or blocklist specific tools at the connection.
Coding assistantsConnection & credentialsper userError Tracking17 tools
Internal copilotsTool access policiesdeny by defaultStatus Pages16 tools
Workflow automationsRequest & response inspectioninlineDashboards11 tools
Compatible MCP clientsActivity monitoringalerts and logsAll other tools76 tools
FAQ

Common questions about running Better Stack MCP through TrustGate.

Connect Better Stack MCP instantly

Pick the tools, point your agent at TrustGate, and Better Stack MCP is live: scoped, inspected, logged.