flutter-docs-mcp
Related Servers
Alternatives to flutter-docs-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to retrieve live CPython standard-library documentation and PyPI package metadata as clean markdown, with cached, throttled, robots-aware requests and local module search.MIT
- AlicenseAqualityFmaintenanceA real-time server that provides Flutter/Dart documentation and pub.dev package information to AI assistants, ensuring they generate accurate and up-to-date Flutter code.874MIT
- 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-
- AlicenseAqualityBmaintenanceEnables AI coding agents to fetch live MDN Web Docs pages, TypeScript handbook content, and npm package metadata as clean markdown, with local search, caching, and polite throttling.5MIT
- FlicenseAqualityDmaintenanceProvides AI models with direct access to documentation for over 600 technologies from DevDocs.io, including popular languages, frameworks, and tools. It enables comprehensive searching, content retrieval, and offline access via an intelligent local caching system.122-
- 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.2714MIT
TDQS
Scored across 6 tools
Two real overlaps exist: health_check and flutter_status are both described as health checks (up/version vs. index/cache/API probes), and flutter_docs accepts a 'pub:' form that fetches package description+README, duplicating pub_package's core output. Descriptions do clarify the differences (metadata vs. README, version vs. diagnostics), so it's workable but an agent could reasonably pick the wrong one.
All names are consistently snake_case with no verbs, but the prefixes vary by family (flutter_*, pub_*, plain health_check), which is defensible but not a single predictable pattern. Still readable and mostly uniform.
Six tools is well within a healthy scope for a docs server, and each maps to a distinct capability: discovery (flutter_search), fetch (flutter_docs, pub_package), batch resolution (flutter_mentions), and diagnostics (health_check, flutter_status).
The search-then-fetch workflow, package metadata, and batch mention resolution cover the core docs-retrieval lifecycle well. Minor gaps: no tool to rebuild/refresh the search index or clear the cache despite exposing index_stale and cache state.