flutter_searchLABSCO SUMMARY
Current Flutter docs, not 2021's.
The failure this targets is specific: an assistant confidently writing a Riverpod or provider pattern that was deprecated two versions ago. Fetching real docs on demand — and letting you pin an exact package version with pub.dev syntax — means the generated code tracks the API you are actually on. It reads your pubspec.yaml, so coverage matches your project, and the local SQLite cache makes everything after the first fetch fast. Note the two simplified tools are the recommended surface; the older five are kept only for backward compatibility.
What it is
A local MCP server that feeds an AI assistant current Flutter, Dart and pub.dev documentation, so it stops generating deprecated widgets and hallucinated APIs. It fetches docs on demand for any pub.dev package and caches them in local SQLite; everything runs on your machine.
What you get
- A universal search across Flutter classes, Dart libraries, pub packages and concepts with ranked results —
flutter_search - Documentation for any Flutter or Dart identifier with automatic type detection, an optional topic filter, and a token limit —
flutter_docs - Service health and cache statistics —
flutter_status - Version-specific docs requested with pub.dev-style syntax — an exact version, a range, or keywords like
latestandstable - Package detection from your
pubspec.yaml, so the assistant covers what your project actually uses - Local SQLite caching — first fetch pulls from pub.dev, later requests are served from cache
Requirements
No account and no key; it runs locally and your code never leaves the machine. Node.js 16+ for npm/npx, with Python 3.10+ auto-detected and used by the npm package. Run with npx flutter-mcp, or install globally with npm install -g flutter-mcp. In Claude Desktop, Claude Code, Cursor or Windsurf the entry is npx with the argument flutter-mcp. The npm-wrapper package.json names it flutter-mcp at 0.1.2, and the Python package flutter-mcp-server at 0.1.1. HTTP and SSE transports are available with --transport http or --transport sse for clients that need them.
Setup effort
One command — npx flutter-mcp
USE CASES
01
Stopping the assistant writing deprecated Flutter code
Have it fetch current documentation for the widget or package before it generates, so the output matches today's API.
02
Pinning docs to the version you are on
Request a specific package version or range in pub.dev syntax so the guidance matches your dependency, not the latest release.
03
Finding the right package for a job
Search across Flutter classes, Dart libraries and pub packages and pick from ranked options.
04
Checking the server and its cache
Read service health and cache statistics when something seems stale.
8 tools
Listed in project docs. Your client may show a different list.
flutter_docsflutter_statusget_flutter_docsget_pub_package_infosearch_flutter_docsprocess_flutter_mentionshealth_checkBEFORE YOU INSTALL
What to know first
Tools you get
8 tools named in the project's documentation.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx flutter-mcpMCP Clients
Claude Desktop, Claude Code, Cursor, Windsurf
JSON
{
"mcpServers": {
"flutter-docs": {
"command": "npx",
"args": [
"flutter-mcp"
]
}
}
}MCP SuperAssistant — HTTP
MCP SUPERASSISTANT — HTTP · TERMINAL
npx flutter-mcp --transport http --port 8000Continue
CONTINUE · JSON
{
"mcpServers": {
"flutter-docs": {
"command": "npx",
"args": [
"flutter-mcp"
]
}
}
}Save this as .continue/mcpServers/flutter-docs.json in your workspace; Continue picks up JSON MCP config files placed in that folder. MCP tools only work in Continue's agent mode.
