Flutter MCP

# Flutter MCP Server Project - Complete Summary ## Background: MCP Server Configuration Journey ### Initial Setup - Three Main MCP Servers 1. **Firebase MCP** (Account-wide access) - Official Firebase CLI MCP server - Access to all Firebase projects - No `--dir` flag for unscoped access - Authentication via `firebase login` 2. **Supabase MCP** (Account-wide access) - Uses Personal Access Token (NOT project API keys) - Token from Account Settings → Access Tokens - `--read-only` flag recommended for safety - Access to all Supabase projects without `--project-ref` 3. **ZEN MCP Server** - Docker-based multi-AI orchestration - Connects Claude with Gemini, O3, GPT-4o - Enables AI-to-AI conversations - Already running as Docker container ### Configuration Files **Claude Desktop** (`~/Library/Application Support/Claude/claude_desktop_config.json`): ```json { "mcpServers": { "firebase-all": { "command": "npx", "args": ["-y", "firebase-tools@latest", "experimental:mcp"] }, "supabase-all": { "command": "npx", "args": [ "-y", "@supabase/mcp-server-supabase@latest", "--read-only" ], "env": { "SUPABASE_ACCESS_TOKEN": "sbp_YOUR_TOKEN_HERE" } }, "zen": { "command": "docker", "args": [ "exec", "-i", "zen-mcp-server", "python", "server.py" ] } } } ``` **Claude Code** (stored in `~/.claude.json`): ```bash # Add globally with user scope claude mcp add firebase-global -s user -- npx -y firebase-tools@latest experimental:mcp claude mcp add supabase-global -s user -e SUPABASE_ACCESS_TOKEN=your_token -- npx -y @supabase/mcp-server-supabase@latest --read-only claude mcp add zen -s user -- docker exec -i zen-mcp-server python server.py ``` ## Context7 and Deepwiki Research ### Context7 (by Upstash) - **Purpose**: Real-time library documentation - **Problem Solved**: Outdated API information in LLMs - **Coverage**: 50+ JavaScript/Python libraries - **Key Feature**: Dynamic documentation fetching - **Cost**: Completely FREE, no API keys needed - **Usage**: Add "use context7" to prompts - **Architecture**: Local Node.js execution ### Deepwiki (by Cognition Labs) - **Purpose**: GitHub repository understanding - **Problem Solved**: Quick codebase comprehension - **Coverage**: 50,000+ indexed repositories - **Key Feature**: AI-analyzed repository documentation - **Cost**: Free for public repos - **Architecture**: Remote SSE server ### Why They Don't Work for Flutter - Context7: Only supports JavaScript/Python libraries - Deepwiki: Works for Flutter repos but doesn't understand Dart/Flutter APIs specifically ## Flutter MCP Server Project Plan ### Vision Create a Context7-like MCP server specifically for Flutter/Dart ecosystem that provides: - Real-time Flutter/Dart API documentation - Pub.dev package documentation on-demand - Flutter cookbook and samples - Stack Overflow Flutter solutions ### Technical Decisions 1. **Inspiration**: Context7's approach (real-time docs > static knowledge) 2. **Language**: Python (easier for Claude Code to write) 3. **Architecture**: On-demand fetching (better for marketing "supports ALL pub.dev packages") 4. **Distribution**: Public GitHub/npm package ### Data Sources to Integrate - **Official APIs**: api.flutter.dev, api.dart.dev - **Package Registry**: pub.dev (on-demand fetching) - **Examples**: Flutter cookbook, official samples - **Community**: Stack Overflow Flutter tags ### MVP Scope - Start with official Flutter/Dart API documentation only - Estimated time: 2-4 hours with Claude Code - Focus on working prototype first ### Marketing Strategy - **Reddit Pitch**: "MCP server that gives Claude access to ALL pub.dev packages" - **Key Differentiator**: Always up-to-date Flutter/Dart documentation - **Target Audience**: Flutter developers using Claude/Cursor/VS Code ### Technical Requirements 1. MCP protocol implementation in Python 2. Web scraping/API integration for documentation sources 3. Caching mechanism for performance 4. Simple installation via npx/pip ### Development Approach 1. Use Claude Code to build the server 2. Start with minimal viable version 3. Test with personal projects 4. Expand to more sources 5. Release to community ## Next Steps 1. **Get MCP Documentation**: Need current MCP server development guide 2. **Create Project Structure**: Basic Python MCP server template 3. **MVP Features**: - Connect to api.flutter.dev - Parse and return documentation - Handle basic queries 4. **Test & Iterate**: Use with Claude Desktop/Code 5. **Expand**: Add pub.dev, cookbook, etc. 6. **Release**: GitHub + announcement on r/FlutterDev ## Resources Needed - Current MCP server development documentation - Python MCP SDK examples - Flutter/Dart API endpoints - Pub.dev API documentation - Testing environment setup guide ## Potential Challenges 1. **API Rate Limits**: Need caching strategy 2. **Documentation Parsing**: Flutter docs structure complexity 3. **Performance**: Fast response times for good UX 4. **Maintenance**: Keeping up with Flutter updates ## Success Metrics - Working MVP in 4 hours - <1 second response time - Covers 100% of official Flutter/Dart APIs - Positive reception on Reddit/Twitter - 100+ GitHub stars in first month --- *This document summarizes the entire conversation about MCP servers configuration and the Flutter MCP server project idea from [Date: 2025-06-20]*