flutter ilot

Flutter MCP Server is a project-aware, modular backend assistant designed to work with Flutter projects. It provides a suite of specialized MCP commands across environment management, code generation, analysis, testing, documentation, packaging, and file-system operations. By leveraging its modular handlers, it can generate Dart classes, Cubits, API services, and theme modules; migrate navigation systems to GoRouter; perform code reviews and complexity analysis; generate unit tests using blocTest patterns; search Flutter docs and pub.dev packages; and safely perform file operations with path traversal protection. The server speaks the MCP protocol over REST, JSON-RPC 2.0, and MCP endpoints, enabling clients to interact through standard interfaces and tooling. When you run it, the server maintains context about your project, learns from past decisions, and offers explanations for why certain architectural choices or code patterns are suggested, not just what to do next.

Prerequisites:

• .NET 7+ installed on your machine
• Git installed
• A Flutter project (optional, for testing with project context)

1. Clone the repository

• git clone https://github.com/your-org/flutter-mcp-server.git
• cd flutter-mcp-server

2. Restore and run the server

• dotnet restore
• dotnet run

3. Verify the server is running

• Access the MCP API endpoints via the configured port (default typical port of the project) and test a few commands like migrateNavigationSystem or generateDartClass using an MCP client.

4. Optional: configure environment variables (if needed by your deployment)

• Create an environment file or set variables in your hosting environment as required by your deployment scenario.

Tips and considerations:

• The server uses a modular CommandHandler architecture with dedicated handlers for Environment, CodeGeneration, Analysis, Testing, Documentation, Package, and FileSystem tasks. You can extend it by adding new handlers under the Handlers/ directory.
• Enable dry-run mode in your MCP client to preview changes before they are written. This helps in safe experimentation.
• Review the project log at project_log.txt to understand command telemetry and performance insights.
• Ensure your Flutter project structure is compatible with the generated outputs (e.g., Dart class templates, Cubit boilerplate, and API service patterns).
• When migrating navigation or refactoring architecture, verify that the generated code adheres to recommended Flutter best practices and the GoRouter migration patterns supported by the server.
• If you customize MCP capabilities, maintain the mcp-capabilities.json template in Config to reflect available commands and categories.