Compose Preview Catalogs
Browse, inspect and render Jetpack Compose Material 3 and Wear component catalogs
Reviews
No review yet. Used Compose Preview Catalogs? Be the first to help others choose.What it does
Compose Preview Catalogs is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)Hosted endpoint
https://preview.coo.ee/mcpstreamable-http
In Claude Code: claude mcp add --transport http compose-preview-catalogs https://preview.coo.ee/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"compose-preview-catalogs": {
"url": "https://preview.coo.ee/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 1d agoONLINE Compose Preview Catalogs answered an MCP connection on 16 Nov 2026 and introduced itself as compose-preview-catalog 3.164.0 (MCP protocol 2025-06-18).
71 tools offered to AI assistants
request_access· Ask a human for access to this server. Returns an approveUrl and a userCode: show BOTH to the person you are working with, ask them to open the link and check that the code on the page matches, then call poll_access. When the client supportpoll_access· Collect the outcome of a request_access, proving possession of its deviceSecret. It HOLDS THE CALL OPEN and answers the moment the human decides — one call instead of a dozen, since each poll here costs a whole round trip through you. It wastatus· Report readiness, the aggregate catalog set, and which host this is: `origin`, the canonical origin designs here are homed at, and `originAliases`, other hostnames that reach this same server.catalog_list_projects· List every remote catalog with its stable id and preview count. Call this first: catalog_list_previews and catalog_list_data_products take one of these ids as 'catalog'.catalog_library· Open the hosted preview catalog browser app. With no arguments it lists every catalog with its preview count only; pass projectId to list one catalog's previews. To find previews without the app, call catalog_list_projects, then catalog_lisui_builder_open· Open the UI Builder's design list: pick a design to see it as the editor draws it. Takes no arguments. Also opens from the ChatGPT/Codex sidebar, and a deep link to /design/<id> opens one design.catalog_list_previews· List the Compose previews and published metadata of one hosted catalog. 'catalog' is required (ids from catalog_list_projects). Pass 'query' (a component name such as EdgeButton) to narrow by id or label; results are paged (100 by default,catalog_render_preview· Render one preview. Like local compose-ai-tools, the default semantics observation is token-frugal; request observe=png for pixels, observe=svg for the compose/figma-svg vector export as SVG source, or observe=scroll-png / observe=scroll-svcatalog_render_matrix· Render one preview across the cross-product of the given override 'axes' (or an explicit list of watch-face 'scenarios') in a single call, returning a hash/size observation per cell (observe=png adds the pixels). Prefer this over a catalog_catalog_list_devices· List the `@Preview(device = ...)` ids this server's render lane recognises, with each one's dp size and density. The `device` override takes one of these ids; an unrecognised name renders the default frame rather than failing, so check herecatalog_diff_semantics· Compare two previews' semantics by testTag: which tags are only in one side, which moved, and which changed occupancy count. Identity is the authored testTag, not a positional ref, so a tag that stops resolving is reported rather than silencatalog_history_list· The render timeline for one preview: which versions of its rendered bytes exist, when each appeared, and whether the preview is unstable (re-renders differently on every publish) rather than genuinely changing. Where this server holds the t
Show 59 more
catalog_history_diff· Compare two of a preview's recorded renders. Defaults to the two newest — did the last publish move this preview? A metadata comparison: the timeline's versions are already collapsed distinct renders, so whether the bytes changed is answerecatalog_history_read· Fetch one historical render's pixels through this server, by `commit` or `blob` (a prefix is enough). Use when an agent cannot reach the delivery branch itself, or wants the bytes rather than the timeline.ui_builder_list_catalogs· List the component catalogs a UI-builder design can pin to. Start here: a design's `catalogPin` must name a revision this server actually serves, and each catalog's `catalogPin` here is exactly that. By default a summary of what authoring nui_builder_search_components· Find catalog components by id, display name, Compose symbol, role or trait, e.g. `TextField`, `text field`, `OutlinedTextField`, `Button`, `Card`. Case, spaces, hyphens, underscores, slashes and camelCase are ignored, and the components theui_builder_list_designs· List the UI-builder designs on this server, newest first, with the cursor to continue.ui_builder_get_design· Read one design: its whole document — nodes, slots, properties, modifiers, state variables and catalog pin — plus the revision to quote as `baseRevision` when editing it. The catalog the design pins is left out unless `includeCatalog` is trui_builder_preview_catalog_recovery· Dry-run recovery of a design whose stored catalog pin no longer resolves. The server selects the exact currently served pin for the same catalog system and returns a CatalogUpgradePreviewV1 with changes, issues and the hashes required by aui_builder_await_design· Wait for somebody else to change a design and return what they changed, rather than asking again whether they have. Returns the moment a designer in the browser or another agent commits an edit, as the same update frame the browser's own liui_builder_create_design· Create a design, either from a whole `document` you supply or by copying an existing design named by `fromDesignId`. Copying is usually right: a document's `catalogPin` must match a catalog revision this server serves, and a copy carries onui_builder_apply· Apply design mutations — insertNode, setProperty, deleteNode, moveNode and the rest of DesignMutationV1 — as one operation. `baseRevision` is the revision you read; the outcome reports conflicts or rejected edits. This is how an agent addsui_builder_move_design_home· Move a design's canonical home between this server and a repository checkout. This changes real authoritative state: quote the exact `baseRevision` and current `sourceHome` from ui_builder_get_design, provide a stable `operationId`, and namui_builder_replace_design_document· Replace one stored design from a complete DesignDocumentV1 copy — the authoritative save-back and re-import operation. The document must name the same design and the same canonical home you read from ui_builder_get_design; `baseRevision` muui_builder_export· Export a design. `compose` returns the Kotlin the generator writes, or — when the design holds something it cannot express — diagnostics naming each reason. This is the same gate the browser's code pane shows, so an agent and a designer getui_builder_validate· Check a design without saving it: a whole `document`, a stored design by `designId`, or `operations` against a stored design exactly as ui_builder_apply would apply them. Runs the same checks the real call does — document shape, catalog pinui_builder_put_asset· Put a picture behind an `assetKey`, so an `asset/image` node naming that key draws it instead of a placeholder. Send the PNG, JPEG, GIF or WebP bytes base64-encoded in `imageBase64`; the server stores them by content digest and pins {mediaTui_builder_design_access· Read who can open a design: its owner, and every actor it has been shared with, each with the role and the actions that grant carries. Only the owner may ask — this is the answer to "who else is in here" and to "what is the id I must name wui_builder_share_design· Share a design with somebody else, or take that sharing back. `actorId` is the other party's actor id as this server spells it — `github:<login>` for a signed-in person, `operator` for the token holder, `agent:<fingerprint>` for another ageui_builder_get_links· Read what a design is **for**: the `issue` it was drawn for, the `reference` frame in the design tool it reproduces, the `pr` that implemented it, the `thread` it is being discussed in, and the `previous` design it continues. Start a sessioui_builder_set_links· Say what a design is for. **Replaces the whole record**: send every link you want kept, and omit one to clear it — so read ui_builder_get_links first if you are adding to what is already there. `issue`, `reference`, `pr` and `thread` are abui_builder_rename_design· Give a design a new title. The title is the one thing about a design nothing else could change: it is set at creation, shown in every listing and the editor, and not part of any mutation. Anybody who may write the design may rename it. Theui_builder_delete_design· Delete a design: it moves to the trash with its history, access list, overlay and discussion, and is gone from every listing and tool until ui_builder_restore_design brings it back, which works until `restorableUntilEpochMillis` in the replui_builder_list_trash· The designs in the trash that you could restore — ones you deleted, or ones you own — most recently deleted first, each with who deleted it and its `restorableUntilEpochMillis`. Use it to undo a ui_builder_delete_design you regret, or to chui_builder_restore_design· Bring a deleted design back out of the trash exactly as it was: the same revision, history, access list, overlay and discussion. Allowed to whoever could have deleted it, until its `restorableUntilEpochMillis`; after that it is not found. Tui_builder_list_comments· Read the discussion on a design: every thread, where each is pinned — a markup stroke, a design node, or a point on the frame — whether it is resolved, and every reply under it. `sequence` rises on each change and is the cursor to quote toui_builder_post_comment· Say something on a design — a reply into `threadId`, or a new thread when it is omitted. Pin a new thread with `markId` (a stroke on the reference overlay), `nodeId` (a node in the design), or `x`/`y` in frame fractions, so the person readiui_builder_resolve_comment_thread· Close a comment thread once it is answered, or reopen one by passing `resolved: false`. The resolution is attributed to you and is reversible.ui_builder_acknowledge_comment· Say that you have read a comment thread — which is **not** the same as resolving it. Resolving claims the question is settled; acknowledging claims only that you have seen it, which is the honest thing to say while you are still working onui_builder_react_to_comment· React to one comment with an emoji, or take the reaction back with `on: false`. The lightest thing you can say: 👀 on a comment you have just picked up, 👍 on a fix somebody made, where a reply would be noise in a thread a person has to read.ui_builder_await_comments· Wait for the discussion to move past `afterSequence` and return it, rather than polling for it. Returns as soon as anybody — a designer in the browser or another agent — posts, resolves or deletes; returns a `timedOut` reply if nothing happui_builder_render_native· Compile a design and render it with real Compose on this host, rather than in the browser's Wasm canvas — the way to see what a design looks like on Android. Returns the first frame, the token the live frame stream is opened with, and the dui_builder_view· See a design the way a person in the editor sees it: a PNG of the canvas with the overlays drawn on — the `selection` outline, the `reference` picture when one is attached, the discussion's `comments` pins, and the layout `bounds` — and besui_builder_check_design· Check a design before you show it to anybody — one call instead of validate, view and an accessibility pass. Runs `schema` (document shape), `catalog` (the pinned catalog's validation, the mutation reducer and the Compose export gate — whatui_builder_simulate_action· Run a stored design's host logic — the JavaScript in its `hostLogic` that stands in for the host feeding it, answering host actions by setting host inputs — headless, without a browser: `init`, then each of `actions` in order, as the editorui_builder_guidelines_prompt· Read the exact prompt a design-guidelines model is given for a design, before anybody spends a key on it: the rules for the design's platform (Android design guidance from developer.android.com, each with its source), the fixed system prompui_builder_get_guidelines· Read a design's latest design-guidelines result, whoever ran it — a person in the editor on their own key, ui_builder_check_design on this host's key, or an agent that recorded verdicts with ui_builder_record_guidelines. Returns the recordui_builder_record_guidelines· Record your own model's verdicts on ui_builder_guidelines_prompt as the design's latest design-guidelines result, so the editor's Issues panel and other agents show them. Pass the `revision` and rule ids the prompt asked (`rules.asked[].id`ui_builder_render_design_matrix· See one design on several devices in ONE picture: a contact sheet with a captioned cell per device × theme × font scale, plus each cell's device, size and box on the sheet. Nothing is saved — the design's environment is swapped on a scratchui_builder_record_decision· Record a review verdict — `approve` or `reject` — on one revision of a design, with an optional note. Kept beside the design, like comments: it never moves the revision. Recorded as an agent's decision, so a person waiting with ui_builder_aui_builder_await_decision· Wait for somebody to approve or reject a design, rather than asking again whether they have. Returns as soon as a decision lands after `afterSequence` — by default only a person's (`from: "human"`), on any revision unless you name one — orui_builder_set_implementation· Record the pull request that implements a design: its URL, its `status` (draft, open, merged, closed), the design `revision` it implements, and — once you have compared the PR's rendered previews with the design — `previewMatch` {status: maui_builder_implementation_status· Everything the code side needs to implement a design, in one call: the revision, its links (issue, reference, PR, thread), the implementation PR with its status and whether its previews were found to match, the latest verdict on this revisiui_builder_find_design_for_pr· From a pull request back to the design(s) it implements: every design you can read whose implementation record or links name `pr`, with the implementation status and revision. Then call ui_builder_implementation_status for what the design eui_builder_set_reference· Attach the picture a design is being built against — a Figma frame, a screenshot of a shipped screen, a mock — as its reference overlay, or `clear` it. The same overlay the browser editor's Frame, density and reference panel shows, so a perui_builder_compare_reference· Measure a design against its reference overlay (attach one with ui_builder_set_reference). Returns what the picture is against the frame and whether a pixel comparison means anything (`facts.pixelComparable` — a 328×56 dp crop stretched oveui_builder_list_revisions· A design's retained revisions, newest first: each one's number, who made it, when, the operation that produced it (`setProperty ×2, insertNode`, `undo`, `restored r3`) and its document digest. `retention` says how far back the history stillui_builder_diff_designs· Compare two designs, or two retained revisions of one: nodes added, removed and moved, and properties, modifiers and other fields changed, each with its node id and path (`root/slot[index]/node`), plus changed document fields (title, enviroui_builder_restore_revision· Make a retained revision the design's current content again, **forward**: it is committed as a new revision and nothing after it is lost, so a restore is undone by restoring again. `baseRevision` must be the current revision (a restore thatui_builder_fork_design· Make a new design from one revision of another — yours to edit, owned by you, with its parent recorded: the fork's `forkedFrom` (design, revision, document digest) and the parent's `forks` both show in ui_builder_get_links. A fork is not aui_builder_branch_design· Fork a design at a revision into a **branch** to explore an alternative, or to change it without trampling somebody editing it live. A branch is a design with its own id: edit it with ui_builder_apply, look at it with ui_builder_view or ui_ui_builder_list_branches· A design's branches, newest first: each one's id, name, owner, status (open, merged, archived), fork revision, head revision and the number of commands a merge would replay; for a merged one the parent revision it landed at, for an archivedui_builder_merge_branch· Replay a branch's edits onto its parent's current revision through the same reducer every edit goes through — all or nothing. The reply reports every command: `applied` with the revision it landed at and any `STALE_*` notice of what it overui_builder_archive_branch· Close a branch without merging it: it stays readable and listed, and can no longer be edited or merged. Needs write access to the parent, or to have made the branch.ui_builder_compare_branches· Put a design's alternatives side by side in one call: the parent's head and each open branch (or the `branchIds` named) rendered into ONE picture — a short-lived signed https link, numbered by caption — plus, per branch, what it changes agaui_builder_pick_branch· Ask the person which alternative (open branch) of a design to keep, and return their choice. In ChatGPT or Codex it is a thumbnail picker, one option per branch; with plain form elicitation it is a single-choice form; otherwise — and in chacatalog_list_data_products· List the structured data-product kinds of one catalog, optionally one preview. Name the catalog with 'catalog' (ids from catalog_list_projects) or a preview 'uri'.catalog_get_preview_data· Fetch the merged accessibility, annotation, or watchface/complications product for a preview. This lane requires live grant scope.list-all-documentation· Storybook-MCP-compatible alias that lists every preview as a story.get-documentation-for-story· Storybook-MCP-compatible preview metadata lookup.preview-stories· Storybook-MCP-compatible rendering of one or more story ids. Requires live scope.
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Version | 3.165.0 | DECLARED | SRC-001 Official MCP Registry | 4h ago |
| Hosted endpoint | https://preview.coo.ee/mcp | DECLARED | SRC-001 Official MCP Registry | 4h ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 4h ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 4h ago |
| Repository | https://github.com/yschimke/compose-preview-server | DECLARED | SRC-001 Official MCP Registry | 4h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 4h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 4h ago |
Change history
- VERSION17 Nov 20263.163.0 → 3.165.0
- VERSION16 Nov 20263.161.0 → 3.163.0
- VERSION15 Nov 20263.159.0 → 3.161.0
- VERSION10 Nov 20263.158.0 → 3.159.0
- VERSION08 Nov 20263.156.0 → 3.158.0
- VERSION06 Nov 20263.155.0 → 3.156.0
- VERSION03 Nov 20263.154.0 → 3.155.0
- VERSION02 Nov 20263.153.0 → 3.154.0
- VERSION31 Oct 20263.152.0 → 3.153.0
- VERSION30 Oct 20263.151.0 → 3.152.0
- VERSION28 Oct 20263.150.0 → 3.151.0
- VERSION25 Oct 20263.148.0 → 3.150.0
- VERSION24 Oct 20263.147.0 → 3.148.0
- VERSION22 Oct 20263.146.0 → 3.147.0
- VERSION20 Oct 20263.145.0 → 3.146.0
- VERSION19 Oct 20263.143.0 → 3.145.0
- VERSION18 Oct 20263.141.0 → 3.143.0
- VERSION16 Oct 20263.139.0 → 3.141.0
- VERSION15 Oct 20263.138.0 → 3.139.0
- VERSION14 Oct 20263.135.0 → 3.138.0
- VERSION13 Oct 20263.129.0 → 3.135.0
- VERSION12 Oct 20263.122.0 → 3.129.0
- VERSION11 Oct 20263.117.0 → 3.122.0
- VERSION10 Oct 20263.113.0 → 3.117.0
- VERSION09 Oct 20263.110.0 → 3.113.0
- VERSION08 Oct 20263.106.0 → 3.110.0
- VERSION07 Oct 20263.104.0 → 3.106.0
- VERSION06 Oct 20263.103.0 → 3.104.0
- VERSION05 Oct 20263.100.0 → 3.103.0
- VERSION04 Oct 20263.97.0 → 3.100.0
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Compose Preview Catalogs still online?
Free alerts · no account▲ 0Do you run Compose Preview Catalogs? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about Compose Preview Catalogs
How do I connect Compose Preview Catalogs?
Use the hosted endpoint https://preview.coo.ee/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does Compose Preview Catalogs offer?
When Electra Index connected on 16 Nov 2026, it listed 71 tools: request_access, poll_access, status, catalog_list_projects, catalog_library, ui_builder_open, catalog_list_previews, catalog_render_preview and more. The full list is in "Live check" above.
Is Compose Preview Catalogs online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.