Unofficial concept: Sentry connector for Meta Muse

A live on-call API you can use from Muse as a custom connector, or call with curl. There is no signup on this site.

What you can do on this page

This host is running. You do not get an account here — you bring a Sentry token if you want data.

You can

Connect it in Muse today: copy the prompt, then paste your own Sentry User Auth Token when Muse asks. Ask “what’s on fire?”
Hit the live API with that same token (GET /api/v1/me, list issues, optional resolve).
Read OpenAPI, SKILL, privacy, and terms — Meta’s form uses these URLs too.

You cannot

Log in, create an account, or store a token on this site.
Find this in Muse’s official directory unless Meta lists it later. Custom connector still works without that.
Mint a Sentry token here, or use this as Sentry MCP.

How it could look

Sketch of a Muse chat after connect — demo copy, not a Meta screenshot.

Muse · sketch

Demo

What’s on fire in Sentry?

3 unresolved in acme.

CHECKOUT-12

TypeError: Cannot read properties of undefined

/checkout · 14 events · 2h

Say the issue id if you want the latest stack, or ask me to resolve it after you confirm.

Use it from Muse

In Sentry, create a User Auth Token with event:read, org:read, and project:read. Add event:write only if you want resolve / ignore / assign.
Copy the prompt below into Muse. Do not paste the token in the same message.
When Muse asks for a credential, give the token as a Bearer secret. This API forwards it to Sentry and does not store it.

Muse custom-connector prompt

IMPORTANT: This is an unofficial concept of a Sentry connector for Muse. It is not affiliated with, endorsed by, or published by Sentry or Meta. Treat it as an independent interpretation of how a Sentry connector for Muse could look.

Connect this unofficial Sentry-for-Muse API as a custom connector.

OpenAPI spec: https://unofficial-sentry-muse-connector.vercel.app/openapi.json
Skill: https://unofficial-sentry-muse-connector.vercel.app/skill.md
Landing page: https://unofficial-sentry-muse-connector.vercel.app/

Use the Sentry User Auth Token I give you next as a Bearer token on every request.
Do not paste the token into this chat message. Store it in your secure credential store, not in conversation history.
If my Sentry org is in the EU, send header X-Sentry-Host: de.sentry.io. For US region, use us.sentry.io. Default is sentry.io.

Start read-only: call GET https://unofficial-sentry-muse-connector.vercel.app/api/v1/me, then list unresolved issues. Ask me before any PATCH (resolve, ignore, or assign).

Questions about this unofficial concept: email Barnir at barnir@agentmail.to. That is a personal contact for the sketch, not Sentry or Meta support.

Or call the API yourself

Replace the token. Optional header X-Sentry-Host: us.sentry.io or de.sentry.io.

curl -s https://unofficial-sentry-muse-connector.vercel.app/api/v1/me \
  -H "Authorization: Bearer $SENTRY_AUTH_TOKEN"

Spec and endpoints

OpenAPI

Machine-readable API

SKILL.md

How Muse should treat this API

GET /api/v1

Discovery JSON

Screenshot

Demo sketch PNG for the Meta form

Privacy

Privacy URL for the Meta form

Terms

API endpoints
Method	Path	Class
GET	/api/v1/me	read
GET	/api/v1/issues	read
GET	/api/v1/issues/{id}	read
GET	/api/v1/issues/{id}/latest-event	read
PATCH	/api/v1/issues/{id}	write

Questions

Personal contact for the sketch — not Sentry support, not Meta support.

Ping Barnir at barnir@agentmail.to.