Better Stack MCP (remote)
Better Stack's hosted MCP for uptime, incidents, on-call and logs.
By defaultCan write
Safest setupNo read-only mode Use a read-only credential
Flagshosted
Labels are provisional (from vendor docs, checked Oct 27, 2026). Not yet tested in our sandbox.
Read-only switch
No single read-only switch, but X-MCP-Tools-Only (allowlist) and X-MCP-Tools-Except (blocklist) headers restrict which tools are available. Build your allowlist from read tools.
Preset
No read-only switch. This config is the vendor default plus an approval prompt on every tool. It is not read-only. The credential is what protects you.
Claude Code
.mcp.json
{
"mcpServers": {
"betterstack": {
"type": "http",
"url": "https://mcp.betterstack.com"
}
}
}.claude/settings.json
{
"permissions": {
"ask": ["mcp__betterstack"]
}
}ask makes Claude Code prompt before every tool from this server.
Codex
~/.codex/config.toml
# Generated by redpresets.dev on 2026-11-03. Unverified preset. Also use a read-only credential. Not a security guarantee.
[mcp_servers.betterstack]
url = "https://mcp.betterstack.com"
default_tools_approval_mode = "prompt"default_tools_approval_mode = "prompt" asks before every tool call.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"betterstack": {
"url": "https://mcp.betterstack.com"
}
}
}Don't add write tools to mcpAllowlist in .cursor/permissions.json. Leave them on approval. Cursor's docs say the allowlist is not a security boundary.
Credential layer
Use a read-only team token if available.
Facts
- Vendor
- Better Stack official
- Source
- Vendor docs
- Hosted endpoint
https://mcp.betterstack.com- License
- —
- Status
- Active
- Last checked
- Oct 27, 2026
Sources
- Hosted URL; X-MCP-Tools-Only / X-MCP-Tools-Except headers · checked Oct 27, 2026
Spotted something wrong? Labels change when vendors change. Suggest a correction