Skip to main content
Glama
Sign In
UI Kit Aggregator MCP

UI Kit Aggregator MCP

by Faixiang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search UI kits

search_ui_kits
Read-only

Search eight UI and motion component catalogs in one query, filter by source, and get license-checked results with official links and install instructions.

Instructions

One-shot search across MotionSites, React Bits, Uiverse, Anime.js, Aceternity UI, Motion Prompt, Cult UI, and Magic UI. Pick a source by specialty: MotionSites (motionsites): AI website prompt library for conceptual sites such as landing pages, SaaS marketing pages, and portfolios. Choose this for full-page design prompts, not drop-in components. React Bits (react-bits): React animation components: text effects, backgrounds, and UI micro-interactions, in JavaScript or TypeScript with CSS or Tailwind. Choose this for copy-and-paste React components. Uiverse (uiverse): Community HTML, CSS, Tailwind, and React snippets, including hover effects, buttons, and cards. Choose this for small, standalone UI widgets. Anime.js (anime): Lightweight JavaScript animation engine for timelines, easing, and animating DOM, CSS, or SVG elements. Choose this when you need an animation library or its official docs and examples, not a component kit. Aceternity UI (aceternity): React and Tailwind component library with advanced visual effects, including 3D, parallax, spotlight, aurora, glow, and shader-based visuals. Choose this for polished, cinematic UI blocks. Motion Prompt (motion-prompt): Motion vocabulary and prompt library for describing animations, camera moves, and page transitions to AI. Choose this for named effect terms, copyable prompts, and motion demos, not drop-in UI components. Cult UI (cult-ui): Distinctive React / shadcn-style UI components from the official Cult UI registry. Choose this for copy-and-paste Cult components, not a general animation engine. Magic UI (magic-ui): Free React and Tailwind animated components (official free / MIT catalog only). Choose this for copy-and-paste Magic UI free blocks; do not use this source for Magic UI Pro. Each hit already passed the license gate and includes compliance, a short blurb, the official URL, and install/use instructions. Filter with sources. This does not return full source; call get_item for one allowed item. When a source or item requires a token or license key that is not configured, the result status is "needs_token" (not "blocked" and not "allowed"). Do not treat that as a quiet failure. Tell the user that this specific content needs a token, name the product (for example Aceternity All-Access or React Bits Pro) and the environment variable (for example ACETERNITY_PRO_TOKEN or REACTBITS_LICENSE_KEY), point them to the official register URLs in the result, and ask whether to configure/add the token or skip this item. Only retry or fetch after the user confirms and the token is in place; if they skip, stop and do not fetch. This server does not collect the secret in the tool call. If the required token is already configured, fetch proceeds when the license otherwise allows it. Hard compliance blocks stay "blocked" with the body omitted: unclear licenses, disallowed scrape or prompt types, MotionSites prompt bodies, Magic UI Pro and other paid catalogs this server does not support, and redistribution the license forbids. Magic UI Pro is not a missing-token case and must not be offered as "add a token". There is no skip_license_check.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_ui_kits"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum hits per source. Default 5.
queryYesWhat you are building or the component you need, in plain language.
sourcesNoLimit to these source ids. Default: all eight. motionsites: AI website prompts for landing pages, SaaS, and portfolios; react-bits: React animation components, text effects, and micro-interactions; uiverse: community HTML/CSS/Tailwind/React snippets such as hover effects, buttons, and cards; anime: lightweight JS animation engine for timelines, easing, and any-element animation; aceternity: React/Tailwind components with advanced 3D, parallax, spotlight, aurora, glow, and shader effects; motion-prompt: motion vocabulary and copyable prompts for describing animations, camera moves, and page transitions to AI, not drop-in UI components; cult-ui: distinctive React / shadcn-style UI components from the official Cult UI registry, for copy-and-paste Cult components, not a general animation engine; magic-ui: free React and Tailwind animated components from the official Magic UI MIT catalog only, not Magic UI Pro.
variantNoReact Bits code variant. Default prefers TS-TW.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare readOnlyHint and openWorldHint, so the description carries the real burden and does: hits are license-gated and include compliance, blurb, URL, and install instructions; "needs_token" is a distinct third status from "allowed"/"blocked"; hard compliance blocks omit the body; the server never collects the secret. This is materially more than the annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded correctly with purpose, license gate, and status semantics in the first sentences. However, the eight-source roster is repeated almost verbatim from the schema's enum descriptions, and the token-handling instructions run long enough to bury the operational essentials.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description supplies what is needed: what each hit contains, the three possible statuses, and the exact user-facing procedure for a needs_token result. For a read-only, multi-source search tool, an agent has everything required to call it and interpret the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the enum descriptions already define every source id, so most of the per-source text here restates the schema rather than adding meaning. It does add one behavioral note, "Filter with sources," but that is implied by the parameter name; baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource: "One-shot search across MotionSites, React Bits, Uiverse, Anime.js, Aceternity UI, Motion Prompt, Cult UI, and Magic UI." It also explicitly bounds the scope ("This does not return full source; call get_item for one allowed item"), which distinguishes it from the get_item sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives per-source selection guidance with both positive and negative routing ("Choose this for full-page design prompts, not drop-in components"; "not a general animation engine"; "do not use this source for Magic UI Pro"). It also spells out the escalation path to get_item and the exact response protocol when a token is missing, including when not to retry.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools