The Flocks catalog, served to agents

An MCP server with the real contract of all 131 components — props, usage rules, accessibility notes, runnable examples, in English and Portuguese. Local, over stdio, no network: the catalog travels inside the binary.

Download for Claude Desktop (.mcpb) View on GitHub

Why an agent needs it

Flocks is built directly on widgets.dart — no Material, no Cupertino. That is the point of the system, and it is also what makes a model guess wrong: asked to write a screen, it reaches for Material's parameter names, because that is what Flutter looks like everywhere else, and the result does not compile. This server hands it the real prop list instead, from the same sources the site and the Widgetbook are generated from.

Three tools

Every tool takes lang (en or pt) — the catalog is bilingual at the source, field by field, not translated.

Tool	Input	Returns
`list_components`	`category?` (atom · molecule · organism)	id, name and summary of every component
`get_component`	`id`	the full record: props, when to use and when not to, do/don't, accessibility, examples, related
`search_components`	`query`	every match across names, summaries and descriptions — case- and accent-insensitive

Install

Claude Desktop — the bundle

Download flocks-mcp.mcpb and open it with Claude Desktop — double-click, or Settings → Extensions. The bundle carries native executables for macOS (arm64/x64), Linux (x64) and Windows (x64) and picks the right one at launch; no Dart SDK involved. Each release publishes the bundle's SHA-256 next to the file.

Claude Code

claude mcp add flocks -- flocks_mcp

Assumes the flocks_mcp command is on your PATH — that is what the activation below provides.

With the Dart SDK

dart pub global activate flocks_mcp