Skip to main content
Glama

Server Details

Search shadcn registry items, read props and get exact install commands for React components.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
Repository
productapp264/tealmac-ui
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 11 tools

Disambiguation4/5

Each tool has a clearly different retrieval purpose (compose, search, list, item detail, examples, tests, setup, quality rules, changes), and descriptions state when to use each. The main overlap is that get_item already returns an install command and usage example, which duplicates part of get_install_command and get_examples, so an agent may wonder which to call first.

Naming Consistency5/5

All 11 tools follow a strict snake_case verb_noun pattern (get_*, list_*, search_*, compose_page), with no camelCase or bare-noun outliers. The prefixes map cleanly to intent: get_ for single-item retrieval, list_/search_ for discovery.

Tool Count5/5

Eleven tools sit comfortably in the well-scoped 3-15 range for a UI component registry reference server. Each tool covers a distinct facet (setup, rules, discovery, item detail, examples, tests, changes, CLI command, composition) with no obvious filler.

Completeness4/5

The surface covers the full read-only lifecycle: discover (list/search/categories), inspect (item, examples, tests, quality rules, changes), and integrate (setup, install command, compose page). Minor gaps exist, such as no explicit tool for comparing alternatives or resolving a Pro/free registry entry beyond what get_setup and get_item mention.

Available Tools

11 tools
compose_pageCompose a pageA
Read-only
Inspect

Plan a page from blocks for an intent such as 'SaaS landing page with pricing and FAQ' or 'login screen'. Returns one block per section in page order, the install command, a page.tsx scaffold that renders them, and whole templates that already fit. Free blocks only unless includePro is true.

Inputs: intent (required), includePro, packageManager.

get_changesGet changesA
Read-only
Inspect

When an item was added and last changed, and the library releases since a date or version you pass. Call it before updating an installed item: since is when the user installed it (YYYY-MM-DD) or the library version they have.

Inputs: name (required), type, since.

get_examplesGet examplesB
Read-only
Inspect

Working example code for an item: the demos shown on its page, with imports pointing where the CLI installs the item. Use it to wire an item up the way it is meant to be used.

Inputs: name (required), type.

get_install_commandGet install commandA
Read-only
Inspect

The exact shadcn CLI command that installs an item, for npm, pnpm, yarn or bun. Run it in the project's root.

Inputs: name (required), type, packageManager.

get_itemGet itemA
Read-only
Inspect

Everything about one item: description, props, a usage example, dependencies, accessibility notes, quality checks, docs URL, registry JSON URL and install command.

Inputs: name (required), type.

get_quality_rulesGet quality rulesA
Read-only
Inspect

The accessibility, motion, theming and SSR rules every item follows, with why each matters and how to meet it. Read them before writing UI so the first draft already passes.

Inputs: no named parameters.

get_setupGet setupB
Read-only
Inspect

How to prepare a project for this library: requirements, shadcn init, where files land, themes, dark mode and the Pro registry entry.

Inputs: packageManager.

get_testsGet testsA
Read-only
Inspect

The Vitest and Testing Library tests that ship with an item (keyboard use, states, ARIA), with the packages they need. Use them to check an item still works after you or the user changed it. Returns shipped: false when the item has no tests.

Inputs: name (required), type, packageManager.

list_categoriesList categoriesA
Read-only
Inspect

How many components, charts, blocks, templates, patterns and hooks exist, and the categories each is grouped into, with counts. Use a category name as the filter of list_items.

Inputs: no named parameters.

list_itemsList itemsB
Read-only
Inspect

List items, optionally filtered by category (a name from list_categories) and type.

Inputs: type, category.

search_itemsSearch itemsA
Read-only
Inspect

Search components, charts, blocks, templates, patterns and hooks by what you need, for example 'date picker', 'pricing section', 'stacked bar chart', 'modal', 'confirm before delete' or 'debounce'. Common synonyms are understood. Returns the best matches with install commands.

Inputs: query (required), type, limit.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Provides coding agents live access to shadcn-style component registries, enabling them to search, compare, and fetch real component source code for UI composition.
      5
      72 npm
      6
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Lets AI agents search roughly 105,000 shadcn registry components and blocks by meaning across 320+ registries, returning each match's licence and the exact npx shadcn add install command. It also exposes themes, curated blocks, facets, screenshots and ranked registry listings over stdio or HTTP MCP transport.
      2
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.