← All guides
Playbook guide · Free

Manage Incidents, Alerts, and On-Call Through incident.io and Your Muse

Verified 2026-11-18

Through an AnythingMCP custom connector, your muse can work in incident.io for you: read live incidents with their updates and timeline, check alerts, see who is on call, and, with your approval, declare incidents, post updates, and page people.

What it does

incident.io is the incident response service teams use when systems break. Connected this way, the muse gets 43 tools. It lists live and triage incidents with severity, status, type, roles, and custom fields, and reads one incident in full. It lists alerts and their sources, and can resolve a firing alert by hand. It reads schedules, rotations, and escalation paths, so it can answer who is on call now. With your approval it declares an incident, posts updates, edits details, creates actions during the incident and follow-ups after it, and starts an escalation to page people. It also reads users, teams, and the catalog.

How to use it

  1. In incident.io, open Settings, then API keys, and add a new key. Check only what the muse may do: viewing for reading, plus create and edit rights only if you want writes.
  2. Copy the key, shown once, into the connector in AnythingMCP, without the word Bearer in front of it.
  3. Install the connector, then ask the muse to show the key identity. It reports the key name and its roles.
  4. In Muse, open Settings, then Connectors, and add a custom connector with the address AnythingMCP gives you. Sign in and approve.
  5. Ask in plain words: show me the live incidents, who is on call tonight, and draft an update for the worst one.

What you need

  • A Muse account that can add custom connectors
  • An AnythingMCP workspace, on Cloud or self-hosted
  • An incident.io account, and an admin or a role allowed to manage API keys

What to watch for

  • All 43 tools are on at install, including the write tools. The real limit is the key: a tool the key has no right for answers with an error, so keep the key narrow.
  • A new incident opens a chat channel and alerts people, and an escalation pages people on call. The muse shows what it is about to do and waits for your yes.
  • Private incidents need their own permission on the key. Without it, the muse cannot see them. Test incidents stay hidden unless you ask for them.
  • This is a custom connector, and Meta does not review custom connectors. You can disconnect it in Settings at any time. The muse prepares, you decide.

Tried this guide?

Tell the town how it went, or ask for help getting it working.

Talk about this on MuseFM →

Playbook Pro

Want to skip the lessons?

Help your agent learn everything at once. 1,015 skills, one pass, $49 for 90 days.

Get the Pro Pass
More guides →