Blender integration through the Model Context Protocol
CatchUI is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
What is this UI element called? 50 curated UI patterns, names per platform, build prompts. EN/中文.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http catchui-mcp https://catchui.com/api/mcp
# 2 — ask your agent for something these tools do
# search_ui_patterns, get_ui_pattern, list_ui_patterns and 3 more
CatchUI costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http catchui-mcp https://catchui.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Finds the conventional name of a UI element or design pattern from a plain-language description, question or term — e.g. "the bar at the bottom of an app", "three horizontal lines icon", "the black bar at the top of iPhone", "汉堡菜单". Searches CatchUI's curated catalog of 50 patterns and returns names in English and Chinese, definitions, the best-matching Q&A and each entry's catalog URL. Use when s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Description, question, or name of a UI element, in English or Chinese. |
| limit | integer | no | Maximum number of matches to return. |
Returns the full CatchUI entry for one UI pattern by id (e.g. "tabbar", "bottomsheet"): definition in English and Chinese, pronunciation, aliases, how people describe it, component names per platform, an implementation prompt, real search questions with answers, related patterns and the catalog URL. Takes an id; search_ui_patterns finds ids from descriptions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | CatchUI pattern id, e.g. "tabbar". list_ui_patterns lists every id. |
Lists the 50 UI patterns in CatchUI's curated catalog — ids, English and Chinese names and one-line definitions — grouped by family, optionally filtered to one family (NAV, INPUT, ACTION, OVERLAY, FEEDBACK, CONTENT, DATA, SYSTEM).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| family | string | no | Only list patterns in this family. |
Explains how 2 to 4 easily confused UI patterns differ — e.g. toast vs snackbar, modal vs popover vs bottom sheet, tabs vs segmented control, Dynamic Island vs notch. Returns each definition side by side plus the catalog's written comparison when one exists. Accepts ids, names or short descriptions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| patterns | array | yes | 2 to 4 CatchUI pattern ids, names or short descriptions, e.g. ["modal", "popover"] or ["tabs", "segmented control"]. |
Returns what a UI pattern is called in code on each platform — SwiftUI, UIKit, Jetpack Compose, Android Views, Flutter, HTML/ARIA and, for system UI, AppKit, Win32 and Electron — or works backwards from a framework component (e.g. "UISegmentedControl", "ModalBottomSheet", "role=tablist") to the pattern and its equivalents elsewhere. Optionally filtered to one platform. Platforms without a native c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | A pattern id, name or description ("segmented control"), or a framework component name ("UISegmentedControl"). |
| platform | string | no | Optional platform filter, matched against the platform label: e.g. "SwiftUI", "UIKit", "Compose", "Android", "Flutter", "Web". |
Returns CatchUI's ready-to-use implementation instructions for 1 to 6 UI patterns — what to build, where it sits, its states and the accessibility it needs — in English or Chinese, for pasting into an AI coding tool such as Claude Code or Cursor. Accepts ids, names or short descriptions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| patterns | array | yes | 1 to 6 CatchUI pattern ids, names or short descriptions, e.g. ["tabs"] or ["search field", "filter chips", "pagination"]. |
| language | string | no | Language of the prompts: "en" (English) or "zh" (简体中文). |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install CatchUI or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish CatchUI can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.