Squadcast MCP server

What the model can do

Squadcast (SolarWinds Incident Response) on-call and incident management: incidents by time window, status, priority, service and assignee, one incident with its timeline, an incident's war-room notes, teams, services, users, on-call schedules and escalation policies; when you ask, can add or delete a note, acknowledge, resolve, reassign, re-prioritise, snooze or tag an incident, and write a postmortem.

Reads

• squadcast_teamsTeams in the Squadcast organisation, with their ids (most reads are per team) and member counts.
• squadcast_incidentsIncidents for one team in a time window (default the last 7 days, at most 90), filtered by status, priority, service, assignee or text.
• squadcast_incidentOne incident by id: message, description, status, priority, service, assignees, tags, when it was created and acknowledged, and its timeline…
• squadcast_incident_notesThe war-room notes on an incident, oldest first, with author and time.
• squadcast_servicesA team's services: name, description, escalation policy, maintainer, maintenance mode, dependencies and tags.
• squadcast_usersPeople in the Squadcast organisation: id, name, role, title and time zone.
• squadcast_schedulesA team's on-call schedules: name, description, time zone, whether paused, owner and tags.
• squadcast_escalation_policiesA team's escalation policies: who is notified at each step, after how many minutes and by which channels, and how often it repeats.

Acts, when you ask

These change something in Squadcast. 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.

• squadcast_add_noteAdds a note to an incident's war room in Squadcast, visible to everyone who can see the incident; it may fire note webhooks.
• squadcast_delete_notePermanently deletes a war-room note from an incident.
• squadcast_acknowledge_incidentAcknowledges a Squadcast incident as the token's user, which stops its escalation notifications and fires acknowledged webhooks and integrations.
• squadcast_resolve_incidentResolves a Squadcast incident with a resolution reason, which ends its notifications and fires resolved webhooks and integrations (status pages…
• squadcast_reassign_incidentReassigns an unresolved Squadcast incident to a user, a squad or an escalation policy, which pages the new assignee.
• squadcast_set_prioritySets a Squadcast incident's priority, P1 (highest) to P5.
• squadcast_snooze_incidentSnoozes a Squadcast incident's notifications for a number of minutes; nobody is paged about it until the snooze ends.
• squadcast_add_tagsAdds tags (key and value) to a Squadcast incident, keeping the tags it already has; a tag with an existing key takes the new value.
• squadcast_create_postmortemWrites a postmortem for a Squadcast incident, owned by a team, with markdown text, a status (in progress…

Connect it

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

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

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

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

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 Squadcast 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

• › Which P1 incidents are open on checkout?
• › What does the timeline of the last database incident show?
• › Who is notified at each step of the Payments escalation policy?
• › Which incidents were resolved yesterday?
• › Add a note to the checkout incident saying the rollback is done.

Questions

Is this an official Squadcast MCP server?

No. It is Memtro's MCP server with Memtro's Squadcast connector behind it: the connector reads Squadcast through its API with the credentials you connect on Dashboard → Connections, and Squadcast 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 Squadcast?

Only when you ask, and only what it has been granted: add a note to an incident's war room; delete a war-room note; acknowledge an incident; resolve an incident with a resolution reason; reassign an incident to a user, squad or escalation policy; set an incident's priority; snooze an incident's notifications; add tags to an incident; write a postmortem for an incident. 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.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server