Labsco
MCP SERVER

Dart MCP Server

by egyleader ↗

Run the Dart toolchain from the model: analyze a path, apply the available fixes, format with a CI-style exit code, run tests and scripts, compile, generate docs, and scaffold a project from a template.

Build Systems & CI/CD✓ Verified
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