flutter mcp toolkit guide

AI Community

Skill notes

When to use

Use this skill when the user wants to inspect or drive a running Flutter app from this conversation. Examples: "Tap the login button in my app" "Why is the home screen blank?" "Take a screenshot and tell me what's broken"

Step 1: Preflight

Always run flutter-mcp-toolkit doctor --json first. Parse the output: status: "ok" — proceed to Step 2. status: "error" and error.code: "binary_not_found" — load flutter-mcp-toolkit-setup and follow its install instructions. status: "error" and error.code: "vm_not_connected" — load

Step 2: Pick the right skill for the user's intent

User intent · Load skill Read state ("what's on screen?", "show me errors", "screenshot") · flutter-mcp-toolkit-inspect Drive UI ("tap X", "type into Y", "scroll to Z", "hot reload") · flutter-mcp-toolkit-control Diagnose ("why is X failing?", "show recent logs", "evaluate expression") · flutter-mcp-toolkit-debug Register app-specific MCP tools/resources (MCPCallEntry, bootstrapFlutter additionalEntries) · flutter-mcp-toolkit-custom-tools

Step 3: Execute

Each task skill has the tool list, parameter shapes, and example calls. Follow the prelude at the top of the skill — it tells you whether you're calling MCP tools or shelling out to the CLI.

Tool taxonomy reference

The core toolkit tools fall into these categories. The full list with parameter shapes lives in the task skills. Inspection (read-only): discover_debug_apps, get_app_errors, get_screenshots, get_view_details, get_vm, get_extension_rpcs, semantic_snapshot, inspect_widget_at_point, capture_ui_snapshot,

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Preflight

Always run `flutter-mcp-toolkit doctor --json` first. Parse the output: `status: "ok"` — proceed to Step 2. `status: "error"` and `error.code: "binary_not_found"` — load `flutter-mcp-toolkit-setup` and follow its install instructions. `status: "error"` and `error.code: "vm_not_connected"` — load

02
Step 2: Pick the right skill for the user's intent

User intent · Load skill Read state ("what's on screen?", "show me errors", "screenshot") · `flutter-mcp-toolkit-inspect` Drive UI ("tap X", "type into Y", "scroll to Z", "hot reload") · `flutter-mcp-toolkit-control` Diagnose ("why is X failing?", "show recent logs", "evaluate expression") · `flutter-mcp-toolkit-debug` Register app-specific MCP tools/resources (`MCPCallEntry`, `bootstrapFlutter` `additionalEntries`) · `flutter-mcp-toolkit-custom-tools`

03
Step 3: Execute

Each task skill has the tool list, parameter shapes, and example calls. Follow the prelude at the top of the skill — it tells you whether you're calling MCP tools or shelling out to the CLI.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.