MCP server for managing long-running dev processes across Flutter, Next.js, Spring Boot, Vite and more
Server has 10 tools with explicit schemas and descriptions. Naming follows verb_noun convention (flutter_hot_reload, list_devices, start_process). Most tools have 1 - 7 parameters with type definitions and descriptions. Parameter descriptions vary widely, some lack detail on constraints (e.g., start_process 'custom_args' lacks format guidance). Output schemas are not documented in tool definitions. Error handling returns structured responses but lacks recovery guidance in most cases. No tool annotations (readOnlyHint, destructiveHint) despite clear risk levels. Overall: functional but below production baseline.
Clear the log buffer for a managed process
Trigger Flutter hot reload on a running flutter process. Uses Dart VM service if available, falls back to sending "r" to stdin.
Trigger Flutter hot restart (full widget tree rebuild) on a running flutter process. Uses Dart VM service if available, falls back to "R" stdin.
Get recent log output from a managed process (stdout + stderr)
List all available Flutter devices and emulators
List all managed dev processes with their status, uptime, PID and framework
Stop and restart a managed process with its original configuration
Output schemas not documented. Tools return structured responses (ok/err helpers) but LLMs cannot see what fields to expect. Breaks downstream tool chaining and forces parsing of unstructured text.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Tools are marked with Risk levels (READ_ONLY, WRITE, DESTRUCTIVE) in metadata but not exposed to LLM via schema annotations. LLM cannot infer safety properties.
Descriptions too brief for discovery. list_devices (11 chars), clear_logs (35 chars) fall below 50-char minimum. Baseline avg is 194 chars. LLMs struggle to decide when to call these tools.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 53 | 2026-07-28+ | v2 |
Send raw text to a process stdin. Useful for interactive prompts or manual commands.
Start a dev server process. Auto-detects the framework from the project directory.
Gracefully stop a managed dev process (SIGTERM, then SIGKILL after 5s)
Parameter descriptions lack constraint details. start_process 'custom_args' is 'Additional arguments appended to the run command', no format, no examples of valid args. 'env' object lacks guidance on which variables are safe to override.
Error responses lack recovery guidance. Errors return 'Error: <message>' but do not suggest next steps. E.g., 'Process not found' should suggest 'Call list_processes() to see available processes.'