Better Stack
Generally AvailableWith OAuth2 authorization, an agent can check monitor status, review active and past incidents, and search log events to diagnose reliability issues.
- Monitoring
- Incident Management
- Observability
- Authentication
- OAuth 2.0
- Hosting
- Vendor-hosted endpoint
- Required scopes
- 2
- Data actions
- Read and write
How it works
Every agent request passes through Ferentin policy before it reaches Better Stack.
- AI agentAsks for something
- Ferentin policies
- OAuth 2.0 consent
- Granular scope selection
- Audit logging
- Better Stack MCP serverAuthorized connection
- Governed resultMasked, logged, returned
What agents can do
111 tools · you choose which ones agents may callEvery tool this server exposes. You choose which ones agents may call.
- query
- render_chart
- acknowledge_incident
- create_incident_comment
- create_incident
- escalate_incident
- incident_comments
- incident
- available_incident_escalation_policies
- incident_timeline
- incidents
- reopen_incident
- resolve_incident
- escalation_policy
- severity
- escalation_policies
- severities
- create_monitor
- monitor_availability
- monitor
- monitor_response_times
- monitors
- create_heartbeat
- heartbeat_availability
- heartbeat
- heartbeats
- on_call
- on_call_event
- on_call_rotation
- on_call_events
- on_calls
- create_status_page_report
- create_status_page_report_update
- status_page
- status_page_resources
- status_page_report_update
- status_page_reports
- status_pages
- status_page_report_updates
- status_page_sections
- update_status_page
- create_status_page_resource
- update_status_page_resource
- remove_status_page_resource
- create_status_page_section
- update_status_page_section
- remove_status_page_section
- add_chart_to_dashboard
- add_dashboard_section
- create_application
- create_chart_alert
- create_cloud_connection
- create_dashboard
- create_metric_expression
- create_source
- delete_chart_alert
- delete_metric_expression
- edit_application
- edit_chart_alert
- edit_chart
- edit_dashboard_section
- edit_dashboard
- export_dashboard
- application
- chart_alert
- chart_alert_help
- chart_building_help
- chart
- dashboard
- dashboard_query_help
- exploration
- error
- errors_query_help
- explore_logs_query_help
- metric
- metrics_query_help
- metrics_schema
- query_help
- replays_query_help
- source
- source_fields
- import_dashboard
- applications
- chart_alerts
- clusters
- dashboard_templates
- dashboards
- explorations
- data_regions
- errors
- metric_expressions
- releases
- sources
- teams
- move_charts
- remove_chart
- remove_dashboard_section
- remove_dashboard
- remove_dashboard_variable
- remove_exploration_variable
- set_dashboard_variable
- set_exploration_variable
- toggle_chart_alert_pause
- update_error_state
- update_metric_expression
- documentation
- team_members
- team_roles
- invite_team_member
- change_team_member_role
- remove_team_member
Permissions requested
The OAuth 2.0 scopes Better Stack asks you to approve when you connect.
| Scope | Access |
|---|---|
| read | Read |
| write | Elevated |
Before you connect
- OAuth scopes: 'read' for querying, 'write' for mutations. PKCE (S256) and refresh tokens are supported; the OAuth client is public (token endpoint auth method 'none').
- Covers uptime tools (monitors, incidents, on-call schedules/rotations, escalation policies, status pages, heartbeats), telemetry tools (query logs/metrics, sources, dashboards, charts, alerts, ClickHouse SQL execution, data regions), and error tools (applications, releases, error states, session replays, exception analysis).
- The server honors per-request tool-allowlist headers (X-MCP-Tools-Only / X-MCP-Tools-Except) upstream; govern tool exposure via Ferentin MCP policies.
- The tool catalog populates on first live connection (tools/list against the upstream).
About Better Stack
Better Stack combines uptime monitoring, on-call incident management, and log aggregation into a unified observability and reliability platform.
Frequently asked about Better Stack
- What can AI agents do with Better Stack through Ferentin?
- Through Ferentin, agents can use Better Stack for check uptime, list incidents, search logs and read monitors. Every call is checked against your Ferentin policies first.
- How is Better Stack access secured?
- Requests through the Better Stack integration are covered by OAuth 2.0 consent, granular scope selection and audit logging. These controls are applied by Ferentin, not by Better Stack, so they hold across every connected agent.
- What permissions does the Better Stack integration require?
- The Better Stack integration requests 2 OAuth 2.0 scopes: read (read access); write (elevated access)
- How do I connect Better Stack to Ferentin?
- Open the Ferentin admin console, add Better Stack as a new connection and authenticate with OAuth 2.0. You then choose which permissions and which tools your agents may use, and the connection goes live for everyone covered by your policies.
- Is the Better Stack integration generally available?
- Yes. The Better Stack integration is generally available on Ferentin, including the free tier.
Related integrations
3
PagerDuty
Triage incidents, review on-call schedules, and coordinate response so an agent can accelerate outage handling.
MCP Servers
View
Datadog
Observability platform for logs, metrics, traces, monitors, incidents, security signals, and synthetic tests.
MCP ServersEnterprise-managed
View
Sentry
Error tracking and performance monitoring with AI-powered root cause analysis, issue search, replays, profiles, and event analytics.
MCP Servers
View