Is this an official Better Stack MCP server?

No. It is Memtro's MCP server with Memtro's Better Stack connector behind it: the connector reads Better Stack through its API with the credentials you connect on Dashboard → Connections, and Better Stack publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Better Stack?

Only when you ask, and only what it has been granted: add a comment to an incident; open a new incident, alerting on-call by the channels chosen; acknowledge an ongoing incident, stopping further escalation; resolve an ongoing incident; escalate an ongoing incident to a person, team, schedule, policy or the whole organisation (pages them); delete an incident (permanent). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Engineering and operations

Better Stack MCP server

Better Stack in any MCP client, through Memtro: Better Stack does not publish this server. Memtro's Better Stack connector reads Better Stack through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Read incidents (cause, status, who acknowledged and resolved them, when) and uptime monitors from Better Stack; when you ask, can comment on an incident, open one (paging on-call by the channels you choose), acknowledge, resolve or escalate one, or delete one.

Reads

betterstack_list_incidentsIncidents in Better Stack, newest first: what failed, the cause, status (Started, Acknowledged, Resolved), when it started…
betterstack_get_incidentOne Better Stack incident by id, with its cause, status and who acknowledged and resolved it.
betterstack_list_monitorsUptime monitors in Better Stack: name, URL checked, type, current status (up, down, paused…), last check and check frequency.

Acts, when you ask

These change something in Better Stack. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

betterstack_create_incident_commentAdds a comment to a Better Stack incident (markdown), visible to everybody who can see the incident.
betterstack_create_incidentOpens a new incident in Better Stack and alerts the current on-call person by each channel set true here (call, sms, email, push, critical_alert…
betterstack_acknowledge_incidentAcknowledges an ongoing Better Stack incident, which stops further escalation (nobody else is paged for it).
betterstack_resolve_incidentResolves an ongoing Better Stack incident.
betterstack_escalate_incidentEscalates an ongoing Better Stack incident, paging whoever it is escalated to: one user, a team, an on-call schedule, an escalation policy…
betterstack_delete_incidentPermanently deletes a Better Stack incident and its record.

Connect it

First connect Better Stack on Dashboard → Connections, then add Memtro to your client once. The Better Stack tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Better Stack connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› What went down this week, and how long did each incident take to resolve?
› Is anything ongoing in Better Stack right now?
› Which monitors are down or paused?
› Who acknowledged last night's API incident, and what was the cause?
› Resolve the checkout incident and add a comment that the certificate was renewed at 09:40

Questions

Is this an official Better Stack MCP server?: No. It is Memtro's MCP server with Memtro's Better Stack connector behind it: the connector reads Better Stack through its API with the credentials you connect on Dashboard → Connections, and Better Stack publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Better Stack?: Only when you ask, and only what it has been granted: add a comment to an incident; open a new incident, alerting on-call by the channels chosen; acknowledge an ongoing incident, stopping further escalation; resolve an ongoing incident; escalate an ongoing incident to a person, team, schedule, policy or the whole organisation (pages them); delete an incident (permanent). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.