LLM Installation Guide: MCP Flutter Inspector
May 19, 2026 · View on GitHub
This is the canonical agent-facing install runbook for MCP Flutter.
New Documentation Structure
- AI agent docs hub (includes
flutter-mcp-toolkit init <agent>wiring): docs/ai_agents/overview.mdx - Agent execution playbook: docs/ai_agents/execution_playbook.mdx
- AI troubleshooting: docs/ai_agents/troubleshooting.mdx
- CLI vs MCP decision guide: docs/start_here/cli_vs_mcp.mdx
0. AI Agent Instructions
Your role:
- Collect required paths from the user before making changes.
- Build the server, instrument the Flutter app, and configure the client safely.
- Validate tool execution.
1. Required Inputs
Ask for and confirm both absolute paths:
[MCP_SERVER_BASE_PATH]: folder wheremcp_fluttershould be cloned.[FLUTTER_APP_PATH]: target Flutter app to instrument.
Do not proceed until both are known.
2. Clone And Build
cd [MCP_SERVER_BASE_PATH]
git clone https://github.com/Arenukvern/mcp_flutter
cd mcp_flutter
make install
Expected binary:
[MCP_SERVER_BASE_PATH]/mcp_flutter/mcp_server_dart/build/flutter-mcp-toolkit-server
v2 → v3 (MCP fmt_* names, mcpServers keys): docs/start_here/migration_v2_to_v3.mdx.
3. Add Toolkit To Flutter App
cd [FLUTTER_APP_PATH]
flutter pub add mcp_toolkit
flutter pub get
Ensure app initialization includes:
MCPToolkitBinding.instance
..initialize()
..initializeFlutterToolkit();
MCPToolkitBinding.instance.handleZoneError(error, stack);
4. Run Flutter In Debug Mode
flutter run --debug --machine --host-vmservice-port=8181 -d macos
(Adjust -d for your device; use app.debugPort.wsUri from machine output for explicit MCP connections.)
5. Configure The AI Client
Preferred: install skills + MCP wiring in one step:
flutter-mcp-toolkit init claude-code # or: cursor | codex | cline | agents-skills
Skills only (open ecosystem — add MCP config separately):
npx skills add Arenukvern/mcp_flutter -a cursor -y
Full install matrix: docs/ai_agents/overview.mdx.
Manual fallback: merge a flutter-mcp-toolkit server entry under mcpServers (do not delete existing servers). The legacy key flutter-inspector still works if your config predates the rename.
IDs:
flutter-inspectorinmcpServersis only the legacy registry key for this server. The optional Claude Code subagent shipped in the repo plugin isflutter-mcp-toolkit-runtime(plugin/agents/flutter-mcp-toolkit-runtime.md) — notflutter-inspector.
6. Validate
Run these checks in the assistant:
- List tools from
flutter-mcp-toolkit(orflutter-inspectorif that is your registry key) - Get extension RPCs and verify:
ext.mcp.toolkit.app_errorsext.mcp.toolkit.view_detailsext.mcp.toolkit.view_screenshots
- Take a screenshot
- Get view details (layout metadata)
- Get app errors
If response is connection_selection_required, retry with arguments.connection.targetId from availableTargets.
If toolkit extension RPCs are missing, do not claim app-level inspection success:
- Ensure
mcp_toolkitis installed and initialized in app startup. - Restart debug app and retry
get_extension_rpcs. - If app cannot be modified, report that Flutter MCP cannot plug into this app for screenshots/layout/errors.
7. Escalation
If setup fails, use: