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.Try Better Stack MCP now
What your agents can ask once Better Stack MCP is connected.
Select the tools your AI agents can call
120 tools from the Better Stack MCP schema.
Showing 120 tools
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.
| Category | Covers | Access | Suggested policy |
|---|---|---|---|
| Error Tracking | Error 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 replays | Read / Write | Create 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 Pages | Status pages and their settings, the resources and sections displayed on them, and incident reports and maintenance announcements with their updates | Read / Write | A 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 |
| Dashboards | Listing dashboards, groups and templates, dashboard detail with charts and layout, creating from a template or source, configuring, dashboard variables, and JSON export and import | Read / Write | Remove 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 |
| Charts | Chart detail with its SQL queries and settings, chart building and dashboard query instructions, adding, configuring and removing charts, dashboard sections, and rearranging chart positions | Read / Write | Chart removal is permanent. Get chart building instructions and Get dashboard query instructions should be read before writing any chart query |
| Incidents | Creating and listing incidents, full detail with error messages and screenshots, timeline, comments, acknowledging, escalating, resolving and reopening | Read / Write | Escalate incident routes to users, teams, schedules or policies and reaches real people. Reopen only works within 24 hours of resolution |
| On-call & Escalation | Who 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 settings | Read | Entirely read-only: this server reads the on-call configuration but changes it only through incident escalation |
| Monitors & Heartbeats | Listing and detailing monitors and heartbeats, creating them, SLA and uptime summaries and response time trends | Read / Write | Creation only; there is no tool to pause or delete a monitor, so an agent cannot silence uptime checking here |
| Chart Alerts | Listing chart alerts with their status, alert detail with SQL and current incident info, creation instructions, and creating, configuring, removing and pausing or resuming alerts | Read / Write | Pausing an alert silences monitoring without deleting anything, which is the failure mode where nothing looks broken until something is missed |
| Metrics | The 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 fields | Read / Write | Metric expressions change what is extracted going forward; removing one stops a metric being produced without touching any dashboard that reads it |
| Query & Analysis | Executing 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 documentation | Read | Execute 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 Management | Listing team members including pending invitations with their email, name and role, listing organization roles including custom ones, inviting members, changing roles and removing members | Read / Write | These 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 |
| Sources | Listing log sources with status and configuration, source detail including ingestion settings, creating sources with integration guides, and discovering the fields available for querying | Read / Write | Get source fields is the prerequisite for writing a correct query. Source detail exposes ingestion settings |
| Explorations | Saved Explore queries: listing them with chart type, sources and group, their detail with variables and saved time range, and setting or removing an exploration variable | Read / Write | An exploration variable most often decides which sources the exploration queries, so changing it changes what a saved query reads |
| Infrastructure | Data regions available for storing data, storage clusters for direct access, teams with telemetry platform access, and creating temporary credentials for direct ClickHouse access | Read / Write | Create 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.
- 01
Sign in to NeuralTrust
Open the NeuralTrust platform, sign in and go to Getting started, then Connect your tools.
- 02
Choose your agent
When asked which agent you use, pick Claude Code, Codex, Cursor, Windsurf, Copilot or your own code.
- 03
Connect Better Stack
Find Better Stack in the tool list and connect it.
- 04
Connect your agent
Follow the steps on screen to add the config to your agent, then send the test prompt.
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 MCP | 120 TOOLS AVAILABLE |
|---|---|
| Code review agent | 4 tools, read only |
| Issue triage bot | 9 tools |
| Platform team assistant | all 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 assistants | Connection & credentialsper user | Error Tracking17 tools |
| Internal copilots | Tool access policiesdeny by default | Status Pages16 tools |
| Workflow automations | Request & response inspectioninline | Dashboards11 tools |
| Compatible MCP clients | Activity monitoringalerts and logs | All other tools76 tools |
Use Better Stack MCP with any AI agent framework
Setup guides for the tools your team already uses.
Claude CodeAdd Better Stack MCP to Claude Code from the terminal
CursorUse Better Stack MCP tools inside Cursor's agent
CodexConnect Better Stack MCP to the OpenAI Codex CLI
WindsurfGive Windsurf's Cascade access to Better Stack MCP
Gemini CLICall Better Stack MCP from Gemini CLI prompts
Google AntigravityLet Antigravity agents work with Better Stack MCP
GitHub CopilotUse Better Stack MCP in Copilot agent mode
Claude EnterpriseRoll out Better Stack MCP across your Claude workspace
Microsoft Copilot StudioAdd Better Stack MCP as a tool for Copilot Studio agents
Open WebUIBring Better Stack MCP tools into Open WebUI chats
LangChainLoad Better Stack MCP tools into LangChain agents
HaystackPlug Better Stack MCP into Haystack agent pipelines
Strands AgentsGive Strands agents Better Stack MCP tools
Vercel AI SDKCall Better Stack MCP from Vercel AI SDK apps
n8nUse Better Stack MCP in n8n AI agent workflows
Common questions about running Better Stack MCP through TrustGate.
Other MCP servers
More servers from the catalog.
)
incident.io
Securely connect your AI agents to incident.io through TrustGate: incidents, alerts, escalations, on-call schedules, investigations, telemetry, runbooks and operational analysis, scoped per agent and logged.
91 toolsViewHoneycomb
Securely connect your AI agents to Honeycomb through TrustGate: queries, traces, spans, service maps, Boards, Triggers, SLOs and Canvas investigations, scoped per agent and logged.
34 toolsViewDatadog
Securely connect your AI agents to Datadog through TrustGate: logs, traces, metrics, monitors, hosts, incidents and dashboards, scoped per agent and logged.
25 toolsViewPostHog
Securely connect your AI agents to PostHog through TrustGate: insights, SQL, dashboards, feature flags, experiments, error tracking and documentation, scoped per agent and logged.
1135 toolsView
Connect Better Stack MCP instantly
Pick the tools, point your agent at TrustGate, and Better Stack MCP is live: scoped, inspected, logged.