get_diagnosticsLABSCO SUMMARY
The analyzer's answer, not the model's.
It keeps an assistant honest about Dart: the diagnostics come from the SDK and the fixes are the SDK's own, so a suggested change is one the toolchain already endorses.
What it is
A two-tool bridge to the Flutter SDK. One returns the Dart and Flutter diagnostics for a file you name; the other applies the SDK's own fix suggestions to it.
What you get
- Dart and Flutter diagnostics for a single file, read from the SDK rather than inferred
- The SDK's own fix suggestions applied to that file
- Both tools take a file path and nothing else
Requirements
The Flutter SDK installed and available on your PATH, plus Node.js and a local build. The tools operate on one file at a time.
Setup effort
Build from source — git clone https://github.com/dkpoulsen/flutter-tools.git
USE CASES
01
Finding out what is actually wrong with a Dart file
The analyzer's diagnostics, rather than a guess from reading the source.
02
Clearing the mechanical analyzer complaints
The SDK's fix suggestions applied in one step, leaving only the ones that need judgement.
03
Checking a file after an edit
Run diagnostics again to confirm the change closed the problem and did not open another.
2 tools
Listed in project docs. Your client may show a different list.
apply_fixesBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/dkpoulsen/flutter-tools.git
cd flutter-tools
npm install
npm run buildMCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"flutter-tools": {
"command": "node",
"args": [
"<YOUR_PATH_TO_FLUTTER_TOOLS>/build/index.js"
],
"env": {}
}
}
}
