Our grade: 4 checks
Based on public data, not a full audit. See how we grade. Something changed? Request a re-grade.
Community rating
- 5 7
- 4 6
- 3 4
- 2 0
- 1 0
Trust in production
- Trust it - 59%
- With caveats - 35%
- Wouldn't - 6%
82% would recommend this server
How reviewers scored it
- Setup & docs 4.2
- Auth experience 4.5
- Reliability 3.9
- Maintainer responsiveness 4.4
Why it got an A
Hosted by Better Stack at https://mcp.betterstack.com. You sign in with OAuth in the browser, or send an API token as a Bearer header. Read tools list and fetch incidents, monitors, heartbeats, status pages, dashboards and errors, and an execute-query tool runs ClickHouse SQL over logs, spans, metrics and exceptions. The docs list many write tools that change a live account: create, acknowledge, escalate, resolve and reopen incidents; create, update and remove monitors and heartbeats; edit status page reports; change escalation policies, webhooks and Slack integrations; and invite, re-role or remove team members. Writes need OAuth Full access or a Read & write token, and the allowlist and blocklist headers can trim the tool set, so use a read-only connection or filter the tools unless you want your agent changing on-call and team access. Biggest deduction: the server itself is closed source, so this grade rests on Better Stack's documentation and its plugin repo (skills and config only, no server code) rather than code we could read, and we scored maintenance one band lower. The docs give no dated changelog and don't describe team scoping.
How to connect
Hosted: https://mcp.betterstack.com over HTTP; OAuth sign-in on first use. Claude Code: claude mcp add --transport http betterstack https://mcp.betterstack.com
Is Better Stack MCP Server safe?
Is Better Stack MCP Server safe to use?
Better Stack MCP Server grades A (strong public trust signals). Upkeep is hard to verify (closed source or a single maintainer), so pin the version you tested.
Does Better Stack MCP Server have known vulnerabilities?
Not in our current data: it has no open CVEs or advisories. We re-check as new ones are published.
Does Better Stack MCP Server support authentication?
Yes. It requires a login, so access can be tied to a person or a scoped key.
Alternatives in Developer Tools
- A Amplitude MCP ServerAmplitude's hosted MCP server for product analytics - search and query events, charts, dashboards, experiments, feature flags, cohorts and session replay, with OAuth sign-in and a separate EU endpoint.
- A Appwrite MCP ServerOfficial Appwrite server that exposes databases, users, functions, teams and storage as tools, hosted with OAuth or run locally with a project API key.
- A Atlassian Rovo MCP ServerOfficial hosted Atlassian server for Jira, Confluence, Jira Service Management, Compass, Bitbucket, Loom, Goals, Projects, and Teams, with OAuth 2.1 sign-in.
- A Buildkite MCP ServerOfficial Buildkite server for pipelines, builds, jobs, logs, annotations, and Test Engine data, hosted or local.
- A Checkly MCP ServerOfficial hosted Checkly server to read check results, root-cause analyses and status pages, and to create, change, delete and run checks and post incidents, with OAuth or an API key.
Community reviews
No complaints after a month
Been running this for about a month now. You can tell it is actively maintained, the rough edges keep getting fixed. Turned on read-only mode on day one, highly recommend doing the same. Scoped the token to just what the agent needs and it respected that. Would recommend without hesitation.
Used for Scripting routine maintenance tasks
- Setup & docs 4/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Our team uses it every day
Our agents call this dozens of times a day. Updates land regularly, and nothing broke when I upgraded. Good choice if you need Better Stack in your agent.
Used for Keeping project tickets in sync with code changes
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Recommended it to two teams already
Replaced a homegrown script with Better Stack MCP Server and have not looked back. Sign-in flow was painless and I never had to paste a key into a config file. It drives a real browser, so I give it a separate profile with no saved logins.
Used for Keeping project tickets in sync with code changes
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 3/5
- Maintainer responsiveness 3/5
Quietly reliable
Tried it on a side project first, then rolled it out at work. Sign-in flow was painless and I never had to paste a key into a config file. Token setup is the fiddliest part, after that it is smooth.
Used for Onboarding new devs with an agent that answers repo questions
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
OK for read-only work
Took longer to configure than I expected. Sign-in flow was painless and I never had to paste a key into a config file. Hosted endpoint means no local process to babysit. For anything real I would look elsewhere.
Used for CI failure investigation
- Setup & docs 3/5
- Auth experience 4/5
- Reliability 2/5
- Maintainer responsiveness 5/5
Useful, with a few rough edges
Some tools are great, a couple feel half finished. I like that access goes through a proper sign-in instead of a long-lived secret on disk. Hosted endpoint means no local process to babysit. I would use it in prod, but only with a human approving writes.
Used for Generating boilerplate from existing patterns
- Setup & docs 3/5
- Auth experience 4/5
- Reliability 3/5
- Maintainer responsiveness 3/5
Better than the DIY script it replaced
Hooked Better Stack MCP Server into Claude Code and it worked on the first try. I would prefer to read the code, but the hosted service has been dependable.
Used for Internal developer assistant
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Set it up once, forgot about it
Of the Better Stack integrations I tried, this one is the most predictable. I would prefer to read the code, but the hosted service has been dependable. I like that access goes through a proper sign-in instead of a long-lived secret on disk.
Used for Debugging sessions in Cursor
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Trustworthy enough for real work
Started with it as an experiment, now it is a fixture. Being closed source, I cannot audit it, but the vendor has been responsive. Auth is handled properly, and revoking access later was one click. Easy recommendation.
Used for Looking up Better Stack data without leaving the editor
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 4/5
Does what it says, no drama
Clear tool names, sensible outputs, very few surprises. Releases come often and the changelog is clear. Happy to run it in production.
Used for Automating release notes
- Setup & docs 4/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Good defaults, good docs
Simple to set up in Cursor, simple to reason about. Filed an issue and got a reply within two days. I gave it a database user that can only read the tables it needs. I like that access goes through a proper sign-in instead of a long-lived secret on disk. Good choice if you need Better Stack in your agent.
Used for Onboarding new devs with an agent that answers repo questions
- Setup & docs 4/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Mixed feelings after two weeks
It does the job, but it took some tweaking. I like that access goes through a proper sign-in instead of a long-lived secret on disk. Recommended, with sensible guardrails.
Used for Letting a coding agent open and triage issues
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Saves me a context switch every hour
I use this almost daily. Nothing to install, I just point the client at the URL. Auth is handled properly, and revoking access later was one click.
Used for Pairing with Claude Code on a monorepo
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Easy win for our agent setup
Simple to set up in Cursor, simple to reason about. Scoped the token to just what the agent needs and it respected that.
Used for CI failure investigation
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Exactly what I needed from Better Stack
Set this up for our team after comparing a few options. Sign-in flow was painless and I never had to paste a key into a config file. It is in our production agent and I sleep fine.
Used for Debugging sessions in Cursor
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Solid and well behaved
Installed it on a Friday, it was part of my workflow by Monday. The OAuth flow worked first time in Claude Code.
Used for Code review summaries for pull requests
- Setup & docs 4/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Solid core, fiddly setup
I like it, with reservations. The OAuth flow worked first time in Claude Code. Scoped the token to just what the agent needs and it respected that. Nothing to install, I just point the client at the URL.
Used for Letting a coding agent open and triage issues
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 2/5
- Maintainer responsiveness 3/5
Write a review
Ran this server? Tell other teams how it went. You get one review per server. We email you a link to confirm it, then an editor checks it before it goes up. We never show your email.