mcp_flutter MCP — Сценарии использования, Установка & Живое демо

Зачем использовать

Ключевые функции

get_app_errors — condensed error info from the running app
view_screenshot — real screenshots (enable with --images)
get_view_details — screen size, pixel ratio, widget info
Dynamic tool registration — your app registers bespoke tools at runtime
Works with Cursor, Claude (Desktop/Code), Cline, Windsurf via stdio

Живое демо

Как выглядит на практике

flutter.replay ▶ готово

0/0

Установка

Выберите клиент

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "flutter": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/Arenukvern/mcp_flutter"
      ],
      "_inferred": true
    }
  }
}

Откройте Claude Desktop → Settings → Developer → Edit Config. Перезапустите после сохранения.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "flutter": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/Arenukvern/mcp_flutter"
      ],
      "_inferred": true
    }
  }
}

Cursor использует ту же схему mcpServers, что и Claude Desktop. Конфиг проекта приоритетнее глобального.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "flutter": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/Arenukvern/mcp_flutter"
      ],
      "_inferred": true
    }
  }
}

Щёлкните значок MCP Servers на боковой панели Cline, затем "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "flutter": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/Arenukvern/mcp_flutter"
      ],
      "_inferred": true
    }
  }
}

Тот же формат, что и Claude Desktop. Перезапустите Windsurf для применения.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "flutter",
      "command": "TODO",
      "args": [
        "See README: https://github.com/Arenukvern/mcp_flutter"
      ]
    }
  ]
}

Continue использует массив объектов серверов, а не map.

~/.config/zed/settings.json

{
  "context_servers": {
    "flutter": {
      "command": {
        "path": "TODO",
        "args": [
          "See README: https://github.com/Arenukvern/mcp_flutter"
        ]
      }
    }
  }
}

Добавьте в context_servers. Zed перезагружается автоматически.

claude mcp add flutter -- TODO 'See README: https://github.com/Arenukvern/mcp_flutter'

Однострочная команда. Проверить: claude mcp list. Удалить: claude mcp remove.

Сценарии использования

Реальные сценарии: mcp_flutter

Debug a Flutter render error with AI eyes on the running app

👤 Flutter devs ⏱ ~15 min intermediate

Когда использовать: You're iterating on UI and something broke. Instead of describing it, let the AI see the screenshot + errors.

Предварительные требования

Flutter app with mcp_toolkit package — Add to pubspec.yaml and initialize in main()
Running in debug mode — flutter run — the server connects to Dart VM service

Поток

Connect

Connect to my running Flutter app (VM port 8181) via mcp_flutter.✓ Скопировано

→ Tools list now includes get_app_errors, view_screenshot
Capture state

Take a screenshot of the current view. Also pull any errors from the last 60 seconds.✓ Скопировано

→ Screenshot + error log
Suggest fix

Based on this error and screenshot, what's wrong and how do I fix it?✓ Скопировано

→ Code diff proposal

Итог: Tight debug loop where the AI can verify each fix by looking at the next screenshot.

Подводные камни

Screenshot tool disabled by default — Start the server with --images flag
VM port conflicts when running multiple apps — Specify --vm-service-port per app; default 8181

Expose your app's test harness as MCP tools

👤 Flutter devs building QA workflows ⏱ ~30 min intermediate

Когда использовать: Your app has debug-only seeders / state toggles you want AI to call during dev.

Поток

Register tools in Dart

Using mcp_toolkit, register tools seed_users(count: int) and set_feature_flag(name: str, value: bool) in my app's debug initializer.✓ Скопировано

→ Dart snippet registering tools
Drive from Claude

Seed 10 users, flip feature flag 'new_checkout' to true, take screenshot of checkout screen.✓ Скопировано

→ Multi-step tool call sequence with final screenshot

Итог: Faster manual QA via chat-driven state manipulation.

Подводные камни

Tools shipped to release mode accidentally — Gate registration with kDebugMode — release builds don't see them

Understand a confusing widget tree

👤 Flutter devs inheriting someone else's code ⏱ ~20 min intermediate

Когда использовать: You're trying to understand why a screen renders a certain way and the code has 8 levels of nested Builders.

Поток

Get view details

get_view_details for the current screen and summarize the widget hierarchy.✓ Скопировано

→ Widget tree summary
Ask why

Why does this text overflow? Reference specific widgets in the tree.✓ Скопировано

→ Layout reasoning grounded in actual tree

Итог: Faster onboarding to unfamiliar Flutter code.

Подводные камни

Big widget trees blow up token budget — Ask for a depth-limited summary first, then drill in

Комбинации

Сочетайте с другими MCP — эффект x10

flutter + git-2

Debug → fix → commit loop

Screenshot, diagnose, have me apply the fix, then git_commit with message describing the fix.✓ Скопировано

Инструменты

Что предоставляет этот MCP

Инструмент	Входные данные	Когда вызывать	Стоимость
get_app_errors	since?: int (seconds)	After triggering a bug in the running app	free
view_screenshot		Visual verification; requires --images flag	tokens per image
get_view_details		Understand layout / screen geometry	free
<custom>	Varies per app registration	Whatever you register via mcp_toolkit	free

Стоимость и лимиты

Во что обходится

Квота API: None
Токенов на вызов: Screenshots are large (~1-3k vision tokens); widget trees 500-5k
Деньги: Free, MIT
Совет: Disable screenshots (remove --images) when debugging non-visual issues — widget tree + errors are much cheaper.

Безопасность

Права, секреты, радиус поражения

Хранение учётных данных: None — connects to local Dart VM service

Исходящий трафик: Local only in typical use; screenshots go to your LLM provider

Никогда не давайте: Expose VM service port to the network in release builds

Only works in debug/profile mode — release builds lock down the VM service.
Tested on macOS/iOS; Android and desktop support is marked 'not tested' in the README.

Устранение неполадок

Частые ошибки и исправления

Cannot connect to Dart VM

Start your Flutter app first, then the MCP server. Confirm VM port (usually 8181) matches config.

Проверить: curl http://127.0.0.1:8181/

Screenshots return 404

Server started without --images flag. Restart with the flag.

Custom tools not showing up

mcp_toolkit must be initialized after runApp; verify kDebugMode gate isn't false in your build.

Альтернативы

mcp_flutter в сравнении

Альтернатива	Когда использовать	Компромисс
Flutter DevTools MCP	You want the official Flutter tooling	Doesn't exist yet as an MCP; this is the closest

Ещё

Ресурсы

📖 Читать официальный README на GitHub

🐙 Открытые задачи

🔍 Все 400+ MCP-серверов и Skills