Skip to main content
Glama
Sign In
UI Kit Aggregator MCP

UI Kit Aggregator MCP

by Faixiang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get license terms

get_license
Read-only

Read a source's license name, URL, attribution, and notice without fetching component or prompt content, so you can verify terms before copying UI code.

Instructions

Read the license name, URL, attribution, and notice for a source without fetching component or prompt source. Specialties: 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. Use this before copying anything into a repository. If a listed item would need a token that is not configured, sourceAccess is "needs_token" and asks configure-or-skip; Magic UI Pro and similar unsupported catalogs stay blocked. 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>"
    },
    "name": "get_license"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemIdNoOptional item id. Pro/starter ids select the paid license text.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint, so the description carries the rest and does so substantively: it explains that missing tokens yield status 'needs_token' rather than 'blocked'/'allowed', that hard compliance blocks omit the body, that the server never collects the secret, and that there is no skip_license_check. Minor inconsistency ('sourceAccess is needs_token' vs 'result status is needs_token') muddies which field is returned.

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 purpose is correctly front-loaded, but roughly two-thirds of the text is per-source marketing prose that repeats the enum descriptions in the schema. The token-handling guidance is valuable yet buried in a wall of undifferentiated sentences with no structure or bullets.

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 two-parameter read-only tool with full schema coverage and no output schema, the description covers what is returned (name, URL, attribution, notice), the token/compliance status semantics, and the caller's expected next action. Nothing an agent needs to call it correctly is missing.

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 description coverage is 100% and the schema already documents both `source` (with per-enum meaning) and `itemId` ('Pro/starter ids select the paid license text'). The description's long catalog of specialty descriptions largely duplicates the enum descriptions rather than adding new meaning, so the baseline 3 applies.

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

Purpose4/5

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

The opening sentence gives a specific verb and resource ('Read the license name, URL, attribution, and notice for a source') and adds scope ('without fetching component or prompt source'), which implicitly separates it from get_item. The remaining bulk is a source catalog that restates the enum rather than sharpening the tool's own purpose.

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?

It states a concrete use point ('Use this before copying anything into a repository') and gives detailed when-to-proceed guidance for the needs_token path (ask the user, configure or skip, do not retry until confirmed). It does not explicitly name sibling alternatives such as check_compliance or get_item, only alluding to them via 'without fetching component or prompt source'.

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