← All guides
Playbook guide · Free

Check Errors and Issues Through Sentry and Your Muse

Verified 2026-11-12

Through a custom connector, your muse can read Sentry errors in plain words, listing your projects, finding the issues that need attention, and reading the events behind an issue.

What it does

The connector adds four read-only tools for the hosted Sentry service. It lists the projects in your organization, so you know what can be checked. It lists issues, which are groups of related errors, and it starts with unresolved issues unless you ask for a different search. You can narrow the list to one project and to a time range, such as the last 24 hours or 14 days. It reads one issue in full, and it lists the events for an issue, where each event is one single time that error happened. Ask for full events and you get the full event body and stack trace Sentry recorded.

How to use it

  1. In Sentry, open Personal Tokens in your user settings and create a token with organization and event read scopes.
  2. Note your organization short name, from your Sentry web address.
  3. Start an AnythingMCP account and add the Sentry connector with that token and that organization name.
  4. In Muse, open Settings, then Connectors, and add a custom connector with the address AnythingMCP gives you. Sign in and approve.
  5. Ask which projects exist, then ask for the unresolved issues in one project, then ask for the events behind the issue you care about.

What you need

  • A Muse account that can add custom connectors
  • An AnythingMCP account with the Sentry connector added
  • A Sentry account on the hosted service, or your own Sentry install
  • A Sentry personal token with organization and event read access
  • Your Sentry organization name

What to watch for

  • The connector only reads. It cannot fix, close, assign, or clear an issue. Changes stay in Sentry, by a person.
  • Access follows the token owner. The muse can only see the projects and issues that person can see in Sentry.
  • Full events are capped at 10 per page, because each one carries a full stack trace. Expect a short, detailed list, not a long one.
  • Use the long issue number the tools return, not the short code you see in the Sentry app, when you ask for one issue.
  • If you run your own Sentry, point the connector base address at your own install after setup.
  • 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 →