Skip to main content
Glama

Server Details

React + Tailwind UI components and recipes your AI coding tool can search and install.

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-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 10 tools

Disambiguation4/5

Most tools occupy distinct resource+action slots: search_components/search_templates for discovery, get_component for metadata, get_component_code for source, get_installation for setup, check_access for permissions. The only friction is the cluster of get_component / get_component_code / get_installation / check_access, which all orbit the same entity, but the descriptions draw clear lines between metadata, source, install steps and entitlement.

Naming Consistency5/5

Consistent snake_case verb_noun pattern throughout: get_*, search_*, list_categories, check_access. The single 'check_' verb is a purposeful semantic difference (a boolean-ish query, not a fetch) and reads naturally alongside the rest.

Tool Count5/5

Ten tools is well-scoped for a component library: discovery, detail, source, install, theme, recipes, and access checking each earn their place. No redundant or trivial tools, and nothing clearly missing from the count.

Completeness3/5

The component lifecycle is fully covered end to end (search -> access -> detail -> code -> install -> theme -> recipe). However, templates are a dead end: search_templates and get_template exist, but get_template explicitly never returns files and there is no get_template_code equivalent, so an agent can never actually deliver template source. There is also no tool to enumerate all components/templates without a search query beyond the category listing.

Available Tools

10 tools
check_accessCheck Liro accessA
Read-onlyIdempotent
Inspect

Whether the caller can take a component or template, and why: free, subscriber, lifetime, purchased or unauthorized.

Inputs: slug (required).

get_componentGet a Liro componentA
Read-onlyIdempotent
Inspect

Everything about one component except its source: when to use it, props, variants, npm dependencies, the files it installs, a typechecked usage example with real props, how it sizes and scrolls (layout), the components it pairs with and the recipes it appears in.

Inputs: slug (required).

get_component_codeGet a Liro component's codeA
Read-onlyIdempotent
Inspect

The complete source for one component and every file it imports, ready to save at the paths given. Free components need a free Liro account's token; Pro components need the caller's Liro lifetime access. Install with the shadcn CLI instead when you can run commands (see get_installation).

Inputs: slug (required), include_dependencies.

get_installationInstall Liro componentsA
Read-onlyIdempotent
Inspect

Installation for one or more components: the one-time @liro registry setup for components.json, the shadcn CLI command (always @liro/, never a bare URL), a ready-to-run agent command with a 15-minute install token when this connection carries a CLI token, the npm packages still missing (pass installed_packages from package.json), the files and where they go, and the theme setup.

Inputs: slugs (required), mode, package_manager, installed_packages.

get_recipeGet a Liro recipeB
Read-onlyIdempotent
Inspect

Complete, runnable files that combine several Liro components the way they fit together: an AI chat app shell (Sidebar + Conversation History + AI Chat, with a phone drawer), a dashboard app and a billing page. Without a slug, lists the recipes. Every recipe typechecks against the components.

Inputs: slug.

get_templateGet a Liro templateA
Read-onlyIdempotent
Inspect

One template's details and whether the caller may download it. Never returns the template's files.

Inputs: slug (required).

get_themeGet the Liro themeA
Read-onlyIdempotent
Inspect

The theme's colour tokens (light and dark values, and what each one colours), how to restyle Liro to a brand from your own CSS without editing components, the type scale, and the cn() config for it.

Inputs: no named parameters.

list_categoriesList Liro categoriesB
Read-onlyIdempotent
Inspect

The categories in the Liro catalogue with the components in each, plus the library contract: stack, theme, access, install path, and the accessibility and responsive behaviour every component has.

Inputs: no named parameters.

search_componentsSearch Liro componentsA
Read-onlyIdempotent
Inspect

Find Liro React + Tailwind components by what they do. Returns the best matches first with slug, category, access (free or pro) and version. Start here, then call get_component for details.

Inputs: query (required), limit, category.

search_templatesSearch Liro templatesB
Read-onlyIdempotent
Inspect

Find complete Liro React / Next.js templates: what each is, its stack, a live preview and how it is licensed.

Inputs: limit, query.

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
      Not graded
      quality
      B
      maintenance
      Enables AI coding assistants to search, preview, and retrieve authentic production-ready React + Tailwind CSS bento grid components from 20 verified UI libraries and inject them into codebases.
      MIT
    • F
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to search a catalogue of plain HTML, CSS and JavaScript UI components and fetch each one's exact files, settings and framework integration instructions. Lets users add production-ready interface components by asking in natural language.
      2
      2
      1
      -
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources