Flocks MCP

io.github.jotapeconsultoriaPublished by GitHub account jotapeconsultoriav0.1.2Updated Oct 24, 2026

Servidor MCP que serve o catálogo de 131 componentes do Flocks (props, uso, a11y) a agentes.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Serves the Flocks Flutter design system's catalog of 131 components — props, usage and accessibility — to AI agents over MCP.

What you can do
  • Look up Flocks components in a catalog of 131 entries.
  • Read each component's props, usage guidance and accessibility notes.
  • Consult the design system's component reference while writing Flutter UI code.
  • No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when an assistant writes or reviews Flutter interfaces built on the Flocks design system and needs accurate component props, usage and accessibility details instead of guessing. Less relevant if you do not use Flocks.
Requirements
Runs as a local stdio process on the user's machine, distributed as an .mcpb bundle; desktop only, not web-executable. No authentication, environment variables or headers are declared. The README's development notes assume a Flutter/Dart workspace for working on the source.
Before you install
The manifest declares no credentials, so nothing secret is requested. The catalog is read-only reference data; no write, send or delete actions are described. The README's build and test commands are for contributors to the repository, not needed to use the server.

Installation

In SourceWeft

  1. Open Flocks MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Flocks

A Flutter design system built on widgets.dart — no Material, no Cupertino.

flocks.live

Six of the seven packages are published on pub.dev under the jotapeconsultoria.com.br verified publisher. The seventh is the demo, which is a showcase and not a library.

PackageWhat it is
flocks · pub.devThe design system: tokens, theme, white-label brand, and the components.
flocks_phosphor · pub.devPhosphor Icons as an AppIconProvider — six weights, shipped as fonts so the tree-shaker can prune them.
flocks_material · pub.devMaterial Design icons as an AppIconProvider. The reference implementation of the axis.
flocks_cupertino · pub.devThe cupertino_icons glyphs as an AppIconProvider — the iOS visual vocabulary, under MIT. Not Apple's SF Symbols.
flocks_lucide · pub.devLucide as an AppIconProvider — one stroke weight, shipped as a font so the tree-shaker can prune it.
flocks_mcp · pub.devThe component catalog served to agents over MCP. Also on the MCP Registry and as an .mcpb bundle in each release.
flocks_demo · flocks.live/demo · not published, by designThe white-label demo: your brand colour on a full dashboard and CRUD, and the configuration exported as Dart you can paste. It is a showcase, not a library.

No version numbers in that table on purpose: nothing here gates a hand-written one, and pub.dev already shows the current version of each.

Start at packages/flocks/README.md. The components are browsable at widgetbook.flocks.live.

Working on it

This repo is a pub workspace. Resolve from the root, always:

bash
flutter pub get

That is what makes the adapters and the MCP server resolve flocks against the local package instead of the published one, so a change to the core is felt by them in the same checkout. Each package carries resolution: workspace, so pub get run inside one of them will fail — it is not a broken checkout.

bash
dart format --output=none --set-exit-if-changed .   # formataçãodart analyze                                        # os três pacotescd packages/flocks && flutter test --exclude-tags goldencd packages/flocks && dart run tool/validate_components.dart

Goldens compare pixels and their baselines were generated on macOS arm64, so they run apart, and only there:

bash
cd packages/flocks && flutter test --tags golden

License

MIT — see LICENSE. Bundled third-party assets keep their own licenses: the fonts are SIL Open Font License 1.1, Phosphor Icons is MIT, Lucide is ISC (with the part derived from Feather under its own MIT), and cupertino_icons — a dependency, not a vendored asset — is MIT. Each license text ships beside the files it covers (OFL.txt, assets/icons/LICENSE, assets/fonts/LICENSE-phosphor-*, packages/flocks_lucide/assets/fonts/LICENSE-lucide), and each package's README says which apply to it.

Source: README.md at commit a09ad0f

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts