Live · hosted, nothing to install

syxUI, but for
your agent.

Ask for a now-playing card and your agent writes the real file into your project. It reads the same registry this site does — so it can never offer you a component that is not here, and it never scrapes a page to find one.

694: components
94: both frameworks
61: customizable
30: interactive

One command

The server runs here. Nothing to clone, nothing to build, no key and no account — every tool is a read.

Rather run it yourself? The last tab does that, and reads components straight off your disk.

claude mcp add --transport http syxui https://syxui.dev/api/mcp

Add --scope user to have it in every project. Then run /mcp, or restart, so the client picks up the tool list.

Then just ask

No slug to remember, no docs to open. Say it the way you would to a person.

You — I need a background for the onboarding screen that reacts when you tap it. Flutter, in our blue.

→search_components(query: “background that ripples when tapped”, framework: “flutter”)

←ripple-field · spring-lattice · tile-wave · gooey-blobs

→get_component(slug: “ripple-field”, framework: “flutter”, customize: { color: “#5B8CFF” })

←ripple_field.dart · Flutter 3.27 · no dependencies · your colour already in it

customize is the part worth knowing about. Every component declares its own params, and the server substitutes your values into the real properties — so what lands in your project already has your colours in it and still compiles.

Five tools

search_componentsquery · category · kind · framework · interactive · limit: Describe what you need in plain words. When nothing matches every word it matches part of it instead, and says so — a component never goes missing just because your sentence used a word no tag contains.
get_componentslug · framework · customize: The complete source, plus version floor, dependencies and notes. framework accepts "both" for one round trip. Pass customize and your colours and sizes are substituted into the real properties, so what comes back still compiles.
about_syxui—: What the catalog is, how big it is right now, and its honest limits. For when someone asks a question about component libraries rather than for a component.
list_categories—: Every category with a live count, and the totals per kind.
get_component_assetsslug: The files a component expects, and where each one goes in a SwiftUI or a Flutter project.

Plus a syxui://catalog resource — the whole index, one entry per component.

What it will not do

Invent a missing half
Ask for a framework a component does not have and it says so, and tells the agent not to port the other one. The two implementations are written independently, never translated.
Rewrite the source
What the agent receives is the file on disk, byte for byte, with the same two-line notice the code on this site carries.
Scrape this website
The site and both transports import the same query functions from one package, so they cannot disagree about what exists.

No MCP? Use the button.

Every component page has a Copy for AI button. It puts the whole component on your clipboard wrapped in an instruction, and asks the agent to write a note into your project’s own rules file — so you do not have to explain the library again next session.

See the interactive ones

Serving right now