flutter-mcp-toolkit-inspect

When to use

Use this skill for read-only state inspection of a running Flutter app: what is shown on screen, recent errors, available debug targets, VM metadata, and widget tree details. Do not use for driving interaction — that is the interact skill. Start with discover_debug_apps when no connection target is established. Start with semantic_snapshot when you need to know which widgets are on screen.

Recipes

Snapshot the visible UI

1. Call semantic_snapshot().
2. Each interactive node has a stable ref (s_0, s_1, …) and the response includes a snapshot_id.
3. Pass refs to interaction tools; pass snapshot_id to detect staleness.

Find an error by message

1. Call get_app_errors(count: 10).
2. Inspect the errors array — each entry has message, stack trace, and timestamp.
3. Match on message text to find the source.