Skip to main content
Glama
Arenukvern

Flutter Inspector MCP Server

by Arenukvern
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Dart
Hybrid

Related Servers

Alternatives to Flutter Inspector MCP Server

No user-submitted related servers found.

    Related Servers

    • Dart MCP Server

      egyleader
      A
      license
      C
      quality
      D
      maintenance
      A 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).
      10
      12 npm
      6
      MIT

    • flutterflow-mcp

      jamesnocode
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for FlutterFlow that uses a command-palette model to manage projects, inspect UI, and apply safe edits via transactional ChangeSets.
      9 npm
      10
      MIT

    • Flutter Driver MCP

      funkyfunc
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that lets AI agents see, tap, type, scroll, and assert inside live Flutter apps — no pre-written tests required.
      28
      15 npm
      MIT

    • flutter-dev-mcp

      zafnz
      A
      license
      A
      quality
      D
      maintenance
      An 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.
      15
      15 npm
      4
      MIT

    • Soma Nexus MCP

      pablostefan
      F
      license
      B
      quality
      C
      maintenance
      MCP server that fetches Figma data (file trees, nodes, images, components, styles, variables) and serves as a foundation for Flutter code generation.
      13
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.8/5.0

    Scored across 60 tools

    Disambiguation2/5

    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 Consistency4/5

    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.

    Tool Count1/5

    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.

    Completeness4/5

    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

    ActivityActive
    ResponsivenessSlow

    Resources