Flutter Inspector MCP Server - MCP Server

Flutter Inspector MCP Server for AI-Powered Development

smithery badge

🔍 A powerful Model Context Protocol (MCP) server that connects your Flutter apps with AI coding assistants like Cursor, Claude, and Cline.

⚠️ This project is a work in progress and not all methods (mostly Flutter Inspector related) are implemented yet.

Currently Flutter works with MCP server via forwarding server. Please see Architecture for more details.

Some of other methods are not tested - they may work or not. Please use with caution. It is possible that the most methods will be removed from the MCP server later to focus solely on Flutter applications and maybe Jaspr.

⚠️ WARNING ⚠️

Debug methods, which may use huge amount of tokens and therefore overload context now placed under "debug-tools" parameter. In production, any debug methods are disabled by default.

🚀 Getting Started

Quick Start is available in QUICK_START.md
Configuration options are available in CONFIGURATION.md

🎯 What Agent can call:

[Resource|Tool] Analyse errors: get precise and condensed errors of your app. Why it is better then console message: it contains precisely only what Agent need, not the whole list of traced widgets and duplicate information. This works best to give Agent understanding of the error.
[Resource|Tool] Screenshot: get screenshot of the app. Works only with Claude (untested). Cursor and Cline doesn't support image type in the response.

Will be implemented:

[Resource|Tool] App info: size of screen, pixel ratio. Unlocks ability for an Agent to use widget selection.
Hot reload & Hot restart
[Resource|Tool] Selection tool: Current idea:
1. Enable widget selection in Flutter Inspector.
2. Select widget by logical pixel position.
3. Get detailed information about your Flutter app's structure based on logical pixel position.

In research:

Inspect Current Route: See current navigation state
Extensions: Flutter Provider/Riverpod states: Get state of Provider/Riverpod instances.
Extensions: Jaspr: ?
Extensions: Jaspr Provider: ?
Extensions: Flame: ?

📚 Available Tools

All tools default to using port 8181 if no port is specified. You can override this by providing a specific port number.

Most tools described in TOOLS.md

todo: add more details about useful methods

🔧 Troubleshooting

Make sure you:

Verify that forwarding server is running.
Opened Devtools in Browser.
Have added MCP extension to your Flutter app dev dependencies and enabled it in Devtools.
Connection Issues
- Ensure your Flutter app is running in debug mode
- Verify the port matches in both Flutter app and inspector
- Check if the port is not being used by another process
AI Tool Not Detecting Inspector
- Restart the AI tool after configuration changes
- Verify the configuration JSON syntax
- Check the tool's logs for connection errors

🚧 Smithery Integration 🚧 (work in progress)

The Flutter Inspector is registered with Smithery's registry, making it discoverable and usable by other AI tools through a standardized interface.

Integration Architecture

┌─────────────────┐     ┌──────────────┐     ┌──────────────┐     ┌─────────────────┐     ┌─────────────┐
│                 │     │              │     │              │     │                 │     │             │
│  Flutter App    │<--->│  DevTools    │<--->│  Forwarding  │<--->│   MCP Server   │<--->│  Smithery   │
│  (Debug Mode)   │     │  Extension   │     │  Server      │     │   (Registered) │     │  Registry   │
│                 │     │              │     │              │     │                 │     │             │
└─────────────────┘     └──────────────┘     └──────────────┘     └─────────────────┘     └─────────────┘

🤝 Contributing

Contributions are welcome! Please feel free to submit pull requests or report issues on the GitHub repository.

📖 Learn More

📄 License

MIT - Feel free to use in your projects!

Flutter and Dart are trademarks of Google LLC.