Skip to main content
Glama
Sign In
UI Kit Aggregator MCP

UI Kit Aggregator MCP

by Faixiang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get one gated item

get_item
Read-only

Fetch one approved doc excerpt, example, or component source for a selected UI kit item by source and ID, with license gating applied.

Instructions

Fetch one official doc excerpt, example, or component source after the license gate. Choose the 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. If the required token or key is already configured, the fetch proceeds when the license otherwise allows it. If the item requires a token or key that is not configured, status is "needs_token" (not "blocked"): the body is omitted and you must tell the user this content needs a token, name the product and env var, and ask whether to configure/add the token or skip the item. Only retry after the user confirms and the token is in place; if they skip, stop and do not fetch. Hard license 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. Magic UI Pro is not a missing-token case — do not offer to add a token. Pass intendedUse when the use might be redistribution rather than an end product. 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": {
      "source": "<source>",
      "id": "<id>"
    },
    "name": "get_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesItem id from search_ui_kits.
sourceYesLimit 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 variant override.
intendedUseNoExample: 'client marketing site' or 'republish as a component library'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial behavior an agent could not otherwise know: the license gate, the distinction between "needs_token" and "blocked", that the body is omitted in both cases, that the server never collects secrets in the call, that Magic UI Pro must not be treated as an add-a-token case, and that retries must wait for user confirmation. This directly governs correct multi-turn behavior.

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

Conciseness2/5

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

The needs_token/blocked policy is stated twice in near-verbatim blocks ("When a source or item requires a token..." repeats "If the item requires a token..."); the source catalog is likewise duplicated against the schema enum text. The core guidance is front-loaded, but the volume is roughly double what is needed and buries the unique rules.

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?

For a gated fetch tool with no output schema, the description supplies everything an agent needs: what comes back, the status vocabulary, what to tell the user on each status, and the hard-block taxonomy. No significant behavioral question is left open.

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

Parameters4/5

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

Schema coverage is 100%, so source/variant/id semantics are already documented and the description's source blurbs largely duplicate the enum descriptions. It does add meaning the schema lacks: route intendedUse specifically to redistribution scenarios, and implies `id` comes from search results.

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+resource+scope: "Fetch one official doc excerpt, example, or component source after the license gate." It then disambiguates all eight source values with what each contains and an explicit "choose this for X, not Y" clause, so an agent can pick the right source without opening the schema.

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

Usage Guidelines4/5

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

Gives clear conditional routing: which source to choose for full-page prompts vs drop-in components vs animation engines, and instructs passing intendedUse for redistribution cases. What it lacks is explicit framing relative to siblings — e.g. it never says to obtain ids via search_ui_kits (that hint only appears in the schema parameter description) or when to prefer get_license/check_compliance instead.

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