dart-analyzeLABSCO SUMMARY
The Dart CLI becomes named calls carrying a path, an output and a list of flags.
Each tool takes an options list that passes flags straight through, so behaviour past the named parameters is whatever you send. The named parameters are where the useful control sits: dart-fix separates reporting from applying, dart-format's setExitIfChanged is the difference between a formatter and a check, and dart-compile takes the output format and destination directly rather than through a flag string.
What it is
A wrapper over the Dart command line, exposing analyze, compile, create, doc, fix, format, info, package, run and test as separate calls, each taking a path or working directory plus a pass-through options list.
What you get
- Static checks and cleanup: dart-analyze over a path, dart-fix to report the available fixes and apply them when asked, dart-format across several paths with setExitIfChanged for a check that can fail a build.
- Tests and scripts: dart-test runs the tests at a path from a working directory, dart-run executes a script with its arguments.
- Build outputs: dart-compile writes a chosen format to an output path, dart-doc generates documentation into an output directory.
- Project setup: dart-create scaffolds from a template into an output directory, dart-package runs a package command with its arguments, dart-info reports the installed toolchain.
Requirements
A Dart installation on the host, and a project directory for the tools that take a path or workingDir.
Setup effort
One command — npx -y @egyleader/dart-mcp-server
USE CASES
01
Standing up a new package and getting its dependencies in place
Scaffold the project from the template you want into a chosen directory, run the package commands it needs, and confirm which toolchain is answering.
02
Clearing the analyzer before the pull request goes up
Analyze the path, apply the fixes that can be applied automatically, and format with the exit-code option so the check can fail a build.
03
Running the suite and the script it exercises
Run the tests from the project's working directory, then run the script directly with the arguments that reproduce what failed.
04
Producing a build and the documentation that ships with it
Compile to the output format and destination you need, and generate the API documentation into its own directory.
10 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
dart-compiledart-createdart-docdart-fixdart-formatdart-infodart-packagedart-rundart-testBEFORE YOU INSTALL
What to know first
Tools you get
10 tools when we connected.
Requires
- npx on PATH
- Node.js 18 or later
CONTEXT COST
Light Standing cost
Rated by the size of the 10 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @egyleader/dart-mcp-serverMCP Clients
Windsurf
WINDSURF · JSON
{
"mcpServers": {
"dart": {
"command": "npx",
"args": [
"-y",
"@egyleader/dart-mcp-server"
]
}
}
}Claude Desktop
CLAUDE DESKTOP · TERMINAL
npx -y @smithery/cli install @egyleader/dart-mcp --client claude
