flutter-dev-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| flutter_testA | Run flutter tests and return a summary of failed tests. Use flutter_get_result to get full error details for specific test IDs. |
| flutter_get_resultA | Get full error details for specific test IDs from a previous flutter_test run. Output is capped at 24KB. |
| flutter_runA | Start a Flutter app. Returns a run_id for use with hot_reload, hot_restart, and logs tools. |
| flutter_hot_reloadB | Trigger a hot reload on a running Flutter app. |
| flutter_hot_restartC | Trigger a hot restart on a running Flutter app. |
| flutter_killA | Kill a running Flutter app. |
| flutter_logsA | Get logs from a running Flutter app. Returns the most recent logs, capped at 24KB. |
| flutter_analyzeA | Run static analysis on a Flutter project. Returns all errors, warnings, and info-level issues with file locations and rule names. |
| flutter_devicesA | List available Flutter devices (simulators, emulators, physical devices). |
| flutter_cleanA | Run flutter clean to delete build artifacts. Useful when builds get into a bad state. |
| flutter_pub_getB | Run flutter pub get to resolve and download dependencies. |
| flutter_pub_addB | Add one or more packages to the project's dependencies. |
| flutter_gen_l10nB | Generate localization files from ARB files. |
| flutter_build_runnerA | Run build_runner to generate code (freezed, json_serializable, drift, etc.). |
| flutter_buildB | Build a Flutter app for a target platform (e.g. apk, ios, web, macos). Can take a long time. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Every tool targets a distinct Flutter workflow action: testing, result retrieval, running, hot reload/restart, killing, logs, analysis, devices, cleaning, pub operations, localization generation, code generation, and building. The complementary relationship between flutter_test and flutter_get_result is clearly described and should not cause confusion. No two tools appear to do the same thing.
All tools follow a consistent flutter_ prefix with lowercase snake_case naming. Most tools use an imperative verb or a recognizable Flutter CLI command, making the pattern predictable and easy to navigate. Even noun-style names like flutter_logs and flutter_devices fit the overall flutter_<command> convention.
Fifteen tools is at the upper end of the ideal range but every tool corresponds to a meaningful, non-redundant Flutter development capability. The count is well-scoped for a comprehensive Flutter development server without feeling bloated. Each tool earns its place by covering a distinct phase of the development workflow.
The tool surface covers the main Flutter lifecycle well: testing, running, hot reload/restart, logs, analysis, dependency management, code generation, localization, and building. Minor gaps exist such as no flutter_pub_remove, flutter_clean_list, or project scaffolding tool, but these are unlikely to block common agent workflows. The core development loop is fully supported.