FlutterSDK Dusk MCP server

Dusk

End-to-end driver for Flutter apps. Read by humans, driven by AI agents. Snapshot the Semantics tree, drive any gesture, capture screenshots, observe live state, all from one CLI and one stdio MCP server.

Documentation · pub.dev · Issues

[!NOTE]

Requires Dart SDK >= 3.4.0 and Flutter >= 3.22.0. dusk is debug-only: production builds tree-shake the entire driver across web, desktop, and mobile.

Installation

flutter pub add fluttersdk_dusk
dart run fluttersdk_dusk dusk:install      # patches lib/main.dart + scaffolds ./bin/fsa + registers dusk plugin

That's it. After the second command, all 36 dusk: commands surface through ./bin/fsa (~110ms warm) or dart run fluttersdkdusk (works the same, ~3s startup), and the MCP server is one dart run fluttersdkdusk mcp:install away. When fastcli (./bin/fsa) is absent, mcp:install writes dart run fluttersdkdusk mcp:serve into .mcp.json automatically; no manual edit required. See MCP install: 8 clients for the per-client wiring. Manual wiring, Magic-stack integration, and the full per-command flag reference live in the Getting Started guide.

[!TIP]

fastcli is the AOT-compiled artisan dispatcher (~110ms warm) shipped as ./bin/fsa. dusk:install scaffolds it for you automatically (best-effort; falls through to a warning when dart is not on PATH). After that, every ./bin/fsa is the fast path. The CLI also runs as dart run fluttersdk_dusk with the same surface, ~3s slower per call.

Why Dusk?

End-to-end testing on Flutter has always been a stitched-together ritual. flutterdriver ships a one-off socket protocol that does not survive hot restart. integrationtest runs in-process against a simulated WidgetTester, but you write a test file, build, run, and wait. AI coding agents that want to drive the running app reach for ad hoc flutter test invocations, copy stack traces back into the prompt, and paste screenshots back, calling it a workflow.

Shortened. The full README is on GitHub.