Flutter Inspector MCP Server
MCP-Server + Flutter MCP-Toolkit
Für KI-gestützte Entwicklung
🔍 Model Context Protocol (MCP)-Server, der Ihre Flutter-Apps mit KI-Codierungsassistenten wie Cursor, Claude, Cline, Windsurf, RooCode oder jedem anderen KI-Assistenten verbindet, der MCP-Server unterstützt

📖 Dokumentation
[!NOTE] Das Flutter-Team entwickelt derzeit ein neues experimentelles Paket, das die Entwicklung von Dart-Tools ermöglicht.
Daher liegt mein aktueller Schwerpunkt auf
um Tools zu stabilisieren und zu verfeinern, die in der Entwicklung nützlich sind (so dass es mehr Plug & Play wäre, zum Beispiel: es gibt nicht nur die Fehler zurück, sondern fordert die KI auch auf, mit diesem Fehler umzugehen) . Weitere Informationen finden Sie in MCP_RPC_DESCRIPTION.md
Optimieren Sie den Prozess der Erstellung von MCP-Servertools, indem Sie ihn anpassbar machen.
Ich hoffe, es wird Ihnen nützlich sein.
Einen schönen Tag noch!
Related MCP server: flutter-dev-mcp
🎉 v2 veröffentlicht! 🎉
Jetzt funktioniert der Flutter MCP-Server ohne Weiterleitungsserver und Devtools-Erweiterung. Weitere Informationen finden Sie in CHANGELOG.md .
⚠️ WARNUNG
Dump-RPC-Methoden (wie dump_render_tree ) können zu einer enormen Token-Nutzung oder einer Kontextüberlastung führen. Daher sind sie standardmäßig deaktiviert, können aber über die Umgebungsvariable DUMPS_SUPPORTED=true aktiviert werden.
Weitere Einzelheiten zu Umgebungsvariablen finden Sie in .env.example .
🚀 Erste Schritte
(Experimentell) Sie können versuchen, den MCP-Server zu installieren und ihn mit Ihrem AI-Agenten zu konfigurieren. Verwenden Sie die folgende Eingabeaufforderung:
Please install MCP server using this link: https://github.com/Arenukvern/mcp_flutter/blob/main/llm_install.mdmit Cursor: https://www.youtube.com/watch?v=pyDHaI81uts
mit VSCode + Cline: Eingabeaufforderung verwenden
Please install MCP server using this link: https://github.com/Arenukvern/mcp_flutter/blob/main/llm_install.mdKonfigurationsoptionen sind in CONFIGURATION.md verfügbar
🎯 KI-Agenten-Tools
Fehleranalyse
get_app_errors[Ressource|Tool] – Ruft präzise und komprimierte Fehlerinformationen aus Ihrer Flutter-App ab. Verwendung :Verwendet nur eine kurze Beschreibung des Fehlers. Sollte doppelte Fehler filtern, um zu vermeiden, dass das Agenten-Kontextfenster mit denselben Fehlern überflutet wird.
Verwendet den Fehlermonitor, um Dart-VM-Fehler zu erfassen. Alle Fehler werden in der Flutter-App erfasst und sind dann auf Anfrage vom MCP-Server verfügbar.
Getestet auf : ✅ macOS, ✅ iOS Nicht getestet auf : 🚧 Android, 🤔 Windows, 🤔 Linux, ❌ Web Siehe Problem
Entwicklungstools
view_screenshot[Ressource|Tool] – Erstellt einen Screenshot der laufenden Anwendung. Konfiguration :Aktivieren mit dem Flag
--imagesoderIMAGES_SUPPORTED=trueVerwendet PNG-Komprimierung, um die Bildgröße zu optimieren.
get_view_details[Ressource|Tool] – Bildschirmgröße, Pixelverhältnis. Kann einem Agenten die Möglichkeit zur Widget-Auswahl freischalten.
Alle Tools verwenden standardmäßig Port 8181, wenn kein Port angegeben ist. Sie können dies durch die Angabe einer bestimmten Portnummer überschreiben.
📚 Weitere Informationen finden Sie in MCP_RPC_DESCRIPTION
🔒 Sicherheit
Da Sie den MCP-Server verwenden, um im Debug-Modus eine Verbindung zur Flutter-App herzustellen, sollte die Verwendung grundsätzlich sicher sein. Ich empfehle jedoch, die Funktionsweise in ARCHITECTURE.md zu überprüfen und zu erfahren, wie dies bei Bedarf zur Verbesserung der Sicherheit geändert werden kann.
Dieser MCP-Server wird von MseeP.ai verifiziert.
🔧 Fehlerbehebung
Verbindungsprobleme
Stellen Sie sicher, dass Ihre Flutter-App im Debug-Modus ausgeführt wird
Überprüfen Sie, ob die Ports sowohl in der Flutter-App als auch auf dem MCP-Server übereinstimmen.
Überprüfen Sie, ob der Port nicht von einem anderen Prozess verwendet wird
KI-Tool erkennt Inspector nicht
Starten Sie das KI-Tool nach Konfigurationsänderungen neu
Überprüfen der JSON-Konfigurationssyntax
Überprüfen Sie die Protokolle des Tools auf Verbindungsfehler
Der Flutter MCP-Server ist im Register von Smithery registriert, sodass er über eine standardisierte Schnittstelle von anderen KI-Tools gefunden und verwendet werden kann.
Integrationsarchitektur
┌─────────────────┐ ┌───────────────────────┐ ┌─────────────────┐
│ │ │ Flutter App with │ │ │
│ Flutter App │<--->│ mcp_toolkit (VM Svc. │<--->│ MCP Server │
│ (Debug Mode) │ │ Extensions) │ │ │
│ │ │ │ │ │
└─────────────────┘ └───────────────────────┘ └─────────────────┘🤝 Beitragen
Beiträge sind willkommen! Senden Sie gerne Pull Requests oder melden Sie Probleme im GitHub-Repository .
📖 Mehr erfahren
Sternengeschichte
📄 Lizenz
MIT – Nutzen Sie es gerne in Ihren Projekten!
Flutter und Dart sind Marken von Google LLC.
Available Tools
60 toolsdart_io_get_http_profile_requestC
RPC: Get details of a specific HTTP request from the profile
Inputs: requestId (required), port.
dart_io_get_open_file_by_idC
RPC: Get details of a specific open file by its ID
Inputs: fileId (required), port.
dart_io_get_open_filesC
RPC: Get list of currently open files in the Flutter app
Inputs: port.
dart_io_get_versionC
RPC: Get Flutter version information (ext.dart.io.getVersion)
Inputs: port.
dart_io_http_enable_timeline_loggingB
RPC: Enable or disable HTTP timeline logging. Connects to the default Flutter debug port (8181) unless specified otherwise.
Inputs: enabled (required), port.
dart_io_socket_profiling_enabledB
RPC: Enable or disable socket profiling. Connects to the default Flutter debug port (8181) unless specified otherwise.
Inputs: enabled (required), port.
debug_allow_bannerC
RPC: Toggle the debug banner in the Flutter app
Inputs: enabled (required), port.
debug_disable_clip_layersC
RPC: Toggle disabling of clip layers in the Flutter app
Inputs: enabled (required), port.
debug_disable_opacity_layersB
RPC: Toggle opacity layers debugging (ext.flutter.debugDisableOpacityLayers). Connects to the default Flutter debug port (8181) unless specified otherwise.
Inputs: enabled (required), port.
debug_disable_physical_shape_layersC
RPC: Toggle physical shape layers debugging (ext.flutter.debugDisablePhysicalShapeLayers)
Inputs: enabled (required), port.
debug_dump_focus_treeB
RPC: Dump the focus tree (ext.flutter.debugDumpFocusTree)
Inputs: port.
debug_dump_layer_treeB
RPC: Dump the layer tree (ext.flutter.debugDumpLayerTree). Connects to the default Flutter debug port (8181) unless specified otherwise.
Inputs: port.
debug_dump_render_treeB
RPC: Dump the render tree (ext.flutter.debugDumpRenderTree). Connects to the default Flutter debug port (8181) unless specified otherwise.
Inputs: port.
debug_dump_semantics_treeA
RPC: Dump the semantics tree (ext.flutter.debugDumpSemanticsTreeInTraversalOrder). Connects to the default Flutter debug port (8181) unless specified otherwise.
Inputs: port.
debug_dump_semantics_tree_inverseC
RPC: Dump the semantics tree in inverse hit test order (ext.flutter.debugDumpSemanticsTreeInInverseHitTestOrder)
Inputs: port.
debug_paint_baselines_enabledB
RPC: Toggle baseline paint debugging (ext.flutter.debugPaintBaselinesEnabled). Connects to the default Flutter debug port (8181) unless specified otherwise.
Inputs: enabled (required), port.
flutter_core_brightness_overrideC
RPC: Override the brightness for the Flutter app
Inputs: brightness (required), port.
flutter_core_did_send_first_frame_eventC
RPC: Check if the first frame event has been sent
Inputs: port.
flutter_core_did_send_first_frame_rasterized_eventC
RPC: Check if the first frame has been rasterized
Inputs: port.
flutter_core_evictC
RPC: Evict an asset from the Flutter app's cache
Inputs: asset (required), port.
flutter_core_invert_oversized_imagesB
RPC: Toggle inverting of oversized images for debugging
Inputs: enabled (required), port.
flutter_core_platform_overrideC
RPC: Override the platform for the Flutter app
Inputs: platform (required), port.
flutter_core_profile_platform_channelsB
RPC: Enable or disable profiling of platform channels
Inputs: enabled (required), port.
flutter_core_time_dilationB
RPC: Set the time dilation factor for animations in the Flutter app
Inputs: dilation (required), port.
get_active_portsA
Utility: Get list of ports where Flutter/Dart processes are listening. This is a local utility, not a Flutter RPC method.
Inputs: no named parameters.
get_extension_rpcsB
Utility: List all available extension RPCs in the Flutter app. This is a helper tool for discovering available methods.
Inputs: isRawResponse, isolateId, port.
get_supported_protocolsB
Utility: Get supported protocols from a Flutter app. This is a VM service method, not a Flutter RPC. Connects to the default Flutter debug port (8181) unless specified otherwise.
Inputs: port.
get_vm_infoB
Utility: Get VM information from a Flutter app. This is a VM service method, not a Flutter RPC. Connects to the default Flutter debug port (8181) unless specified otherwise.
Inputs: port.
inspector_add_pub_root_directoriesC
RPC: Add additional root directories for pub packages (ext.flutter.inspector.addPubRootDirectories)
Inputs: directories (required), port.
inspector_dispose_all_groupsA
RPC: Dispose all inspector groups to free up memory (ext.flutter.inspector.disposeAllGroups)
Inputs: port.
inspector_dispose_groupB
RPC: Dispose a specific inspector group to free up memory (ext.flutter.inspector.disposeGroup)
Inputs: groupId (required), port.
inspector_dispose_idB
RPC: Dispose a specific widget ID to free up memory (ext.flutter.inspector.disposeId)
Inputs: id (required), port.
inspector_get_children_details_subtreeC
RPC: Get the children details subtree for a widget (ext.flutter.inspector.getChildrenDetailsSubtree)
Inputs: objectId (required), port.
inspector_get_children_summary_treeB
RPC: Get the children summary tree for a widget (ext.flutter.inspector.getChildrenSummaryTree). Connects to the default Flutter debug port (8181) unless specified otherwise.
Inputs: objectId (required), port.
inspector_get_details_subtreeB
RPC: Get the details subtree for a widget. This provides detailed information about the widget and its descendants. Connects to the default Flutter debug port (8181) unless specified otherwise.
Inputs: objectId (required), port.
inspector_get_layout_explorer_nodeB
RPC: Get layout explorer information for a widget (ext.flutter.inspector.getLayoutExplorerNode). Connects to the default Flutter debug port (8181) unless specified otherwise.
Inputs: objectId (required), port.
inspector_get_parent_chainB
RPC: Get the parent chain for a widget (ext.flutter.inspector.getParentChain). Connects to the default Flutter debug port (8181) unless specified otherwise.
Inputs: objectId (required), port.
inspector_get_pub_root_directoriesB
RPC: Get the list of root directories for pub packages (ext.flutter.inspector.getPubRootDirectories)
Inputs: port.
inspector_get_root_widget_summary_treeC
RPC: Get the root widget summary tree (ext.flutter.inspector.getRootWidgetSummaryTree)
Inputs: port.
inspector_get_root_widget_summary_tree_with_previewsC
RPC: Get the root widget summary tree with previews from the Flutter app. This provides a hierarchical view of the widget tree with preview information.
Inputs: port.
inspector_get_selected_summary_widgetB
RPC: Get summary information about the currently selected widget in the Flutter app. Connects to the default Flutter debug port (8181) unless specified otherwise.
Inputs: port.
inspector_get_selected_widgetB
RPC: Get information about the currently selected widget in the Flutter app. Connects to the default Flutter debug port (8181) unless specified otherwise.
Inputs: port.
inspector_is_widget_creation_trackedB
RPC: Check if widget creation tracking is enabled in the Flutter app.
Inputs: port.
inspector_is_widget_tree_readyA
RPC: Check if the widget tree is ready for inspection (ext.flutter.inspector.isWidgetTreeReady)
Inputs: port.
inspector_remove_pub_root_directoriesB
RPC: Remove root directories from pub packages (ext.flutter.inspector.removePubRootDirectories)
Inputs: directories (required), port.
inspector_screenshotA
RPC: Take a screenshot of the Flutter app (ext.flutter.inspector.screenshot). Connects to the default Flutter debug port (8181) unless specified otherwise.
Inputs: port.
inspector_set_pub_root_directoriesC
RPC: Set the root directories for pub packages (ext.flutter.inspector.setPubRootDirectories)
Inputs: directories (required), port.
inspector_set_selection_by_idC
RPC: Set the selected widget by ID (ext.flutter.inspector.setSelectionById). Connects to the default Flutter debug port (8181) unless specified otherwise.
Inputs: selectionId (required), port.
inspector_showC
RPC: Show specific widget details in the Flutter app inspector.
Inputs: options (required), port.
inspector_structured_errorsB
RPC: Enable or disable structured error reporting in the Flutter app.
Inputs: enabled (required), port.
inspector_track_rebuild_dirty_widgetsB
RPC: Track widget rebuilds to identify performance issues (ext.flutter.inspector.trackRebuildDirtyWidgets). Connects to the default Flutter debug port (8181) unless specified otherwise.
Inputs: enabled (required), port.
inspector_track_repaint_widgetsB
RPC: Track widget repaints to identify rendering performance issues (ext.flutter.inspector.trackRepaintWidgets)
Inputs: enabled (required), port.
inspector_widget_location_id_mapB
RPC: Get a mapping of widget IDs to their source code locations (ext.flutter.inspector.widgetLocationIdMap)
Inputs: port.
layout_set_flex_factorC
RPC: Set the flex factor of a flex child widget (ext.flutter.inspector.setFlexFactor)
Inputs: factor (required), objectId (required), port.
layout_set_flex_fitB
RPC: Set the flex fit property of a flex child widget (ext.flutter.inspector.setFlexFit)
Inputs: fit (required), objectId (required), port.
layout_set_flex_propertiesC
RPC: Set multiple flex properties of a flex child widget (ext.flutter.inspector.setFlexProperties)
Inputs: objectId (required), properties (required), port.
performance_profile_render_object_layoutsC
RPC: Enable or disable profiling of render object layout operations (ext.flutter.profileRenderObjectLayouts)
Inputs: enabled (required), port.
performance_profile_render_object_paintsA
RPC: Enable or disable profiling of render object paint operations (ext.flutter.profileRenderObjectPaints)
Inputs: enabled (required), port.
repaint_rainbowC
RPC: Toggle repaint rainbow debugging (ext.flutter.repaintRainbow)
Inputs: enabled (required), port.
stream_listenA
RPC: Subscribe to a Flutter event stream. This is a VM service method for event monitoring. Connects to the default Flutter debug port (8181) unless specified otherwise.
Inputs: streamId (required), port.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 60 tools
Many tools are distinct, but there are confusingly similar pairs such as inspector_get_root_widget_summary_tree versus inspector_get_root_widget_summary_tree_with_previews, and multiple near-identical dump/toggle variants. With 60 tools, users need deep domain knowledge to pick the right one.
Naming mostly follows snake_case with clear prefixes (debug_, inspector_, dart_io_, flutter_core_). Minor inconsistencies exist (e.g., flutter_core_invert_oversized_images vs debug_paint_baselines_enabled), but overall patterns are recognizable.
60 tools is far beyond a coherent toolkit size for an inspector surface. Many are fine-grained toggles and getters that could be consolidated, making the set unwieldy.
Covers the major Flutter inspector workflows: tree dumps, selection, layout info, debug toggles, pub roots, and HTTP profiling. Some areas like hot reload/restart or broader VM service operations are absent, but within the inspector scope it is fairly complete.
Maintenance
Related MCP Connectors
MCP server to assist with JxBrowser development.
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
MCP server for AI dialogue using various LLM models via AceDataCloud
Related MCP Servers
- AlicenseCqualityDmaintenanceA distributable Model Context Protocol (MCP) server that exposes Dart SDK commands for AI-powered development. This server bridges the gap between AI coding assistants and Dart/Flutter development workflows by implementing the Model Context Protocol (MCP).106MIT
- AlicenseAqualityDmaintenanceAn MCP server that wraps Flutter CLI tools into structured, agent-friendly tools for AI coding agents, with features like two-phase test results, output capping, and managed app lifecycle.1515 npm4MIT
- AlicenseBqualityDmaintenanceAn MCP server that lets AI agents see, tap, type, scroll, and assert inside live Flutter apps — no pre-written tests required.28MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for FlutterFlow that uses a command-palette model to manage projects, inspect UI, and apply safe edits via transactional ChangeSets.10MIT