FlutterSDK Artisan MCP server
CLI framework and stdio MCP server for Flutter: scaffolding, hot reload, REPL, codegen.
2 stars
Reviews
Write oneNobody has reviewed FlutterSDK Artisan yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
FlutterSDK Artisan tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-03 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualityno auth information5/15
- Maintenancelast push 4 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
How FlutterSDK Artisan compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 73/100
- higher than 39% of 48,255 servers
- GitHub stars
- 2
- more than 75% of 28,688 servers
Install FlutterSDK Artisan in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the FlutterSDK Artisan repository's README, as published. We do not edit it. Read it on GitHub
Artisan
Composable CLI framework and stdio MCP server for Flutter and Dart. Scaffolding, code generation, transactional plugin installs, hot reload orchestration, REPL, and AI agent tool surfaces in one binary.
Documentation · pub.dev · Issues
Why Artisan?
Dart's CLI surface is fragmented. Every package invents its own install ritual, its own scaffold script, its own hand-edited entry point. A team that adopts five tools ends up with five bin/*.dart wrappers, five README install sections, and five chances for a bad merge to silently break the build. AI agents that want to drive the running app reach for ad hoc shell scripts because there is no shared tool surface.
Artisan fixes this. One binary registers every command, one protocol describes every plugin install, and one stdio MCP server exposes the whole stack to AI agents.
# Before, the painful manual setup ritual
edit pubspec.yaml # add the plugin dependency
edit bin/<custom>.dart # wire the provider
edit lib/main.dart # register the config factory
edit android/app/src/AndroidManifest.xml # add the permission
edit ios/Runner/Info.plist # add the entry
write .env stub # remember which keys
restart the app and hope nothing collided# After, the Artisan way
dart pub add fluttersdk_artisan
dart run fluttersdk_artisan install
dart run fluttersdk_artisan plugin:install <name>If you know php artisan, you already know the verb shape. The implementation is pure Dart 3.4+, no Flutter runtime dependency in the framework core.
Features
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
FlutterSDK Artisan: common questions
- Is FlutterSDK Artisan MCP server safe?
- Mostly: it is graded B (73/100). Read the FlutterSDK Artisan safety report
- Does FlutterSDK Artisan need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is FlutterSDK Artisan maintained?
- The last commit was 36 days ago (2026-09-29). The latest release is v0.0.15.
- How does FlutterSDK Artisan compare with other MCP servers?
- safety score 73/100 (higher than 39% of 48,255 servers); github stars 2 (more than 75% of 28,688 servers). Full comparison.