From flutter-mcp-toolkit
Entry point for AI-driven inspection, control, debugging, and custom tooling of running Flutter apps; performs preflight check and routes to task-specific skills.
How this skill is triggered — by the user, by Claude, or both
Slash command
/flutter-mcp-toolkit:flutter-mcp-toolkit-guideThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<!-- @FMT_MODE_PRELUDE -->
Use this skill when the user wants to inspect or drive a running Flutter app from this conversation. Examples:
If the user is asking about Flutter concepts unrelated to a running app (architecture questions, package selection), this skill does not apply.
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
flutter-mcp-toolkit-setup and follow its troubleshooting section.flutter-mcp-toolkit-debug and read the error
envelope playbook.| 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 |
If the task spans more than one (e.g. "tap the button and show me what
changed"), load inspect AND control. Skills are additive.
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.
The core toolkit tools fall into these categories. The full list with parameter shapes lives in the task skills.
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,
connect_debug_app. → flutter-mcp-toolkit-inspect.tap_widget, long_press, enter_text,
fill_form, scroll, swipe, drag, hover, press_key, wait_for,
navigate, handle_dialog, hot_reload_flutter, hot_restart_flutter,
hot_reload_and_capture. → flutter-mcp-toolkit-control.get_recent_logs, evaluate_dart_expression. →
flutter-mcp-toolkit-debug.list_client_tools_and_resources, then client_tool /
client_resource — wire names as fmt_* when calling MCP. →
flutter-mcp-toolkit-custom-tools.If doctor is green but a tool call fails, read the returned error.code
and error.recovery fields. The full code → recovery table is in
flutter-mcp-toolkit-debug.
npx claudepluginhub arenukvern/mcp_flutter --plugin flutter-mcp-toolkitInspects, interacts with, and live-edits running Flutter apps via MCP toolkit server. Covers preflight checks, snapshots, taps, scrolls, hot-reloads, and error parsing.
Guides Flutter development for cross-platform iOS, Android, Web apps. Covers non-interactive CLI, project setup, state management, widgets, GoRouter navigation, platform channels, testing, CI/CD.
Provides expert guidance on Flutter 3.27+ and Dart 3.3+ for building/optimizing mobile/web/desktop apps, covering Riverpod/BLoC state, GoRouter navigation, Drift storage, Patrol testing, on-device AI.