A
licenseNot graded
qualityA
maintenanceLocal-first MCP server for querying multi-repo engineering documentation artifacts from a SQLite corpus.
5 npm
AGPL 3.0
Flutter Analysis Engine (MCP)
by Saad0149
Related Servers
Alternatives to Flutter Analysis Engine (MCP)
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenancePrivate, local-first code intelligence MCP server that builds a static graph of repositories and exposes search, architecture, impact analysis, and review tools via MCP.MIT
- AlicenseCqualityDmaintenanceA distributable Model Context Protocol (MCP) server that exposes Dart SDK commands for AI-powered development. This server bridges the gap between AI coding assistants and Dart/Flutter development workflows by implementing the Model Context Protocol (MCP).1031 npm6MIT
Vibgrate AI Contextofficial
AlicenseNot gradedqualityBmaintenanceLocal-first MCP server that gives AI assistants codebase intelligence—code graph, drift analysis, vulnerability attribution, and version-correct library docs—all from the user's machine.1,491 npm3Apache 2.0- AlicenseNot gradedqualityAmaintenanceLocal-first MCP server that scans a repository once and answers architecture questions from an evidence-backed graph, enabling dependency analysis, impact analysis, and codebase exploration without re-reading the source tree.3MIT
- AlicenseNot gradedqualityAmaintenanceLocal-first MCP server that provides project context, verification gates, and structured tools for coding agents to discover knowledge, run diagnostics, and execute allowlisted commands within a repository.24 npmMIT
TDQS
B3.1/5.0
Scored across 24 tools
Disambiguation4/5
Most tools are clearly distinct by purpose: find_* tools target different content types (examples, tests, widgets, best practices, intended behavior) and analyze_* tools target distinct analysis dimensions (architecture, complexity, documentation, testing, dependencies, performance, accessibility). There is some overlap between find_examples and find_best_practice, and between explain_widget and trace_widget, but descriptions help delineate. The find_widget/explain_widget/trace_widget trio has somewhat blurry boundaries.
Naming Consistency4/5
The naming follows a strong verb_noun snake_case pattern throughout (find_*, analyze_*, explain_*, explore_*, search_*, update_*, reindex, trace_widget, repository_status). This is highly consistent. Minor deviations: review_project and repository_status are noun_verb/noun style rather than verb_noun, and analyze_* uses adjectival suffixes (analyze_code_quality) inconsistently across the set.
Tool Count3/5
24 tools is near the heavy end of the appropriate range for a Flutter analysis engine server, which legitimately spans project review, knowledge indexing, code search, and widget explanations. At 24 it's bordering on 'too many' but the scope is broad enough to justify it. The large number of near-parallel analyze_* tools inflates the count.
Completeness4/5
The server covers a comprehensive project analysis workflow: review_project initiates, then eight analyze_* dimensions cover architecture, complexity, docs, testing, dependencies, performance, accessibility, and state management, with follow-up exploration via explain_finding and explore_finding. Knowledge management (find/reindex/repository) is covered. Minor gaps include a missing analyze_security dimension and no tool for viewing project configuration.
Maintenance
ActivityMaintained
ResponsivenessNo issues