Flutter Inspector MCP Server
Related Servers
Alternatives to Flutter Inspector MCP Server
No user-submitted related servers found.
Related 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).1018 npm6MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for FlutterFlow that uses a command-palette model to manage projects, inspect UI, and apply safe edits via transactional ChangeSets.18 npm10MIT
- AlicenseNot gradedqualityBmaintenanceA local-first MCP server that enables AI agents to inspect and debug Android apps and devices through typed tools for UI interaction, logcat, Java/Kotlin and native/Flutter debugging, performance traces, heap dumps, artifacts, and evidence-based diagnostics.1Apache 2.0
- AlicenseBqualityDmaintenanceAn MCP server that lets AI agents see, tap, type, scroll, and assert inside live Flutter apps — no pre-written tests required.2818 npmMIT
- AlicenseBqualityCmaintenanceLocal-first MCP server providing deterministic Flutter/Dart static analysis, knowledge search, and project review with structured insights and confidence-based findings over an indexed SQLite store of official repositories.2424 npmMIT
- 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.1517 npm4MIT
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.