Introducing Magic Sentry 1.0.1

Know what broke before your users tell you.

Sentry error and performance monitoring for the Magic framework: a web-safe boot, the HTTP failures Http swallows, the signed-in user and breadcrumbs from your events.

Get started View on pub.dev

~/my_app

$ flutter pub add magic_sentry

✓ sentry_flutter and sentry_dio resolved

MagicSentry.run(configure: configureSentry, appRunner: _boot);

✓ Sentry starts before Magic.init, so a boot failure is reported too

Wired into Magic. Nothing to glue.

Sentry knows nothing about the Magic Http facade, its auth state or its router. Magic Sentry connects them so the reports carry the context you need.

Web-safe boot

MagicSentry.run opens one guarded zone and starts Sentry before Magic.init, so a failure during boot is reported.
Learn more about Web-safe boot
HTTP failures

The Http facade never throws, so Magic Sentry reports a 5xx or a dead connection as an event and a 4xx as a breadcrumb.
Learn more about HTTP failures
Signed-in user

The Sentry scope user follows Auth.stateNotifier, with your own id, email and extras.
Learn more about Signed-in user
Event breadcrumbs

Any Magic event that implements ReportsBreadcrumb becomes a breadcrumb.
Learn more about Event breadcrumbs
Navigation trail

A navigator observer on MagicRouter records where the user was and, with named routes, feeds release health.
Learn more about Navigation trail
Token scrubbing

SentryTokenScrubber masks tokens that travel in URLs before an event leaves the app.
Learn more about Token scrubbing

Your agent speaks Magic Sentry.

The Magic Sentry skill teaches your coding assistant to wire the service provider and the boot the way the framework expects, before the first line. One command wires it up.

npx skills add anilcancakir/ai --skill magic-sentry

run in your project other editors

works with

Claude Code
Cursor
OpenCode
VS Code Copilot
Codex CLI

✻ claude ~/my_app connected

$ npx skills add anilcancakir/ai --skill magic-sentry

✓ magic-sentry installed

› report failed API calls to Sentry with the signed-in user attached

● Skill(magic-sentry) loaded

⏺ Edit lib/config/app.dart

+ SentryServiceProvider<User>(app, userId: (user) => user.id)

✓ failed calls carry the signed-in user

And checks the docs.

Skills teach the wiring. The MCP server at mcp.anilcancakir.com/magic_sentry gives your agent live docs lookup while it edits, so it never guesses a signature.

Streamable HTTP

One endpoint, every client.
search-docs

Live query against the source.
Public, no auth

Read-only, free to use.

Connect your editor

mcp.anilcancakir.com/magic_sentry preview

# streamable http, the default

claude
                        mcp add
                                                    --transport http
                            magic_sentry
                            https://mcp.anilcancakir.com/magic_sentry

# or stdio, for clients without http

npx
                            -y mcp-remote https://mcp.anilcancakir.com/magic_sentry

Public, no auth.

Add it in seconds

~/my_app

flutter pub add
                magic_sentry

Or add to pubspec.yaml:

dependencies:
  magic_sentry: ^1.0.1

Or give your AI agent this prompt:

Read   https://anilcancakir.com/magic/docs/sentry/llms.txt   and   install   the   Magic   Sentry   package   in   this   project.

Docs
AI

Know what broke before your users tell you.

Wired into Magic. Nothing to glue.

Web-safe boot

HTTP failures

Signed-in user

Event breadcrumbs

Navigation trail

Token scrubbing

Your agent speaks Magic Sentry.

And checks the docs.

Streamable HTTP

search-docs

Public, no auth

Add it in seconds