Flutter MCP
Related Servers
Alternatives to Flutter MCP
No user-submitted related servers found.
Related Servers
- FlicenseBqualityBmaintenanceProvides Flutter and Dart reference data, code generation, live API lookups, and a verified sample corpus for AI coding assistants, enabling efficient Flutter development with accurate guidance and boilerplate generation.14-
- AlicenseAqualityDmaintenanceIntegrates the Pub.dev API with AI assistants to provide real-time Flutter package information, documentation, and trend analysis. It enables users to search for packages, compare versions, and evaluate quality scores through natural language commands.6MIT
- FlicenseNot gradedqualityCmaintenanceProvides AI assistants with live, searchable documentation for any programming library, eliminating hallucinated APIs by returning current, structured API references.-
- AlicenseNot gradedqualityDmaintenanceA sophisticated server that enables AI assistants to automatically analyze codebases and generate comprehensive, professional documentation.2MIT
- AlicenseAqualityDmaintenanceProvides AI assistants with up-to-date documentation for popular libraries and frameworks, enabling them to generate more accurate code using less common or newly released libraries.513 npm36MIT
- AlicenseAqualityCmaintenanceProvides LLMs with real-time access to up-to-date documentation from PyPI, npm, crates.io, GoDocs, DockerHub, GitHub, and GCP, preventing outdated code generation and API hallucinations.2768 PyPI14MIT
TDQS
Scored across 8 tools
The tool set has significant overlap and redundancy, with deprecated tools that duplicate the functionality of newer unified tools. For example, flutter_docs, get_flutter_docs, get_pub_package_info, and process_flutter_mentions all serve similar documentation lookup purposes, which could confuse an agent. However, the descriptions clearly indicate which tools are deprecated, helping to mitigate confusion.
The naming is mixed, with some tools using a consistent verb_noun pattern (e.g., flutter_docs, flutter_search, flutter_status) and others using different conventions (e.g., get_flutter_docs, get_pub_package_info, health_check, process_flutter_mentions, search_flutter_docs). This inconsistency makes the set less predictable, though the names are still generally readable.
With 8 tools, the count is reasonable for a documentation-focused server. However, 3 of the tools are deprecated, effectively reducing the active tool set to 5, which feels slightly thin but still adequate for the domain. The number is not excessive, but the inclusion of deprecated tools adds unnecessary bulk.
The server covers core documentation needs for Flutter/Dart, including lookup, search, and health checks, with no major gaps in functionality. The unified tools (flutter_docs, flutter_search, flutter_status) provide a complete surface for the domain. The deprecated tools do not create gaps but rather redundancy, which does not hinder coverage.