tealmac UI is an MCP server published by com.tealmac, hosted at ui.tealmac.com. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 11 tools, including list_categories, search_items, list_items, get_item, get_install_command.
Search shadcn registry items, read props and get exact install commands for React components.
Nothing else in the archive shares these values.
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.
No parameters.
{
"name": "list_categories",
"title": "List categories",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false
}
}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.
None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
| Parameter | Type | Description |
|---|---|---|
| type | string | Only return this kind of item: component, chart, block (a page section), template (a whole page), pattern (a scenario built from components, such as a confirm-delete flow) or hook (a React hook). |
| limit | integer | |
| query * | string | What to find. |
{
"name": "search_items",
"title": "Search items",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"query"
],
"properties": {
"type": {
"enum": [
"component",
"chart",
"block",
"template",
"pattern",
"hook"
],
"type": "string",
"description": "Only return this kind of item: component, chart, block (a page section), template (a whole page), pattern (a scenario built from components, such as a confirm-delete flow) or hook (a React hook)."
},
"limit": {
"type": "integer",
"default": 10,
"maximum": 50,
"minimum": 1
},
"query": {
"type": "string",
"minLength": 1,
"description": "What to find."
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false
}
}List items, optionally filtered by category (a name from list_categories) and type.
| Parameter | Type | Description |
|---|---|---|
| type | string | Only return this kind of item: component, chart, block (a page section), template (a whole page), pattern (a scenario built from components, such as a confirm-delete flow) or hook (a React hook). |
| category | string | Category name. |
{
"name": "list_items",
"title": "List items",
"description": "List items, optionally filtered by category (a name from list_categories) and type.",
"inputSchema": {
"type": "object",
"properties": {
"type": {
"enum": [
"component",
"chart",
"block",
"template",
"pattern",
"hook"
],
"type": "string",
"description": "Only return this kind of item: component, chart, block (a page section), template (a whole page), pattern (a scenario built from components, such as a confirm-delete flow) or hook (a React hook)."
},
"category": {
"type": "string",
"description": "Category name."
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false
}
}Everything about one item: description, props, a usage example, dependencies, accessibility notes, quality checks, docs URL, registry JSON URL and install command.
| Parameter | Type | Description |
|---|---|---|
| name * | string | Item name, e.g. 'marquee' or 'chart-bar-stacked'. Prefix @tealmac-pro/ for the Pro registry when a name exists in both. |
| type | string | Optional: pick the item of this type. |
{
"name": "get_item",
"title": "Get item",
"description": "Everything about one item: description, props, a usage example, dependencies, accessibility notes, quality checks, docs URL, registry JSON URL and install command.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"minLength": 1,
"description": "Item name, e.g. 'marquee' or 'chart-bar-stacked'. Prefix @tealmac-pro/ for the Pro registry when a name exists in both."
},
"type": {
"enum": [
"component",
"chart",
"block",
"template",
"pattern",
"hook"
],
"type": "string",
"description": "Optional: pick the item of this type."
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false
}
}The exact shadcn CLI command that installs an item, for npm, pnpm, yarn or bun. Run it in the project's root.
| Parameter | Type | Description |
|---|---|---|
| name * | string | |
| type | string | one of ["component","chart","block","template","pattern","hook"] |
| packageManager | string | one of ["npm","pnpm","yarn","bun"] |
{
"name": "get_install_command",
"title": "Get install command",
"description": "The exact shadcn CLI command that installs an item, for npm, pnpm, yarn or bun. Run it in the project's root.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"minLength": 1
},
"type": {
"enum": [
"component",
"chart",
"block",
"template",
"pattern",
"hook"
],
"type": "string"
},
"packageManager": {
"enum": [
"npm",
"pnpm",
"yarn",
"bun"
],
"type": "string",
"default": "npm"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false
}
}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.
No parameters.
{
"name": "get_quality_rules",
"title": "Get quality rules",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| name * | string | Item name. |
| type | string | one of ["component","chart","block","template","pattern","hook"] |
{
"name": "get_examples",
"title": "Get examples",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"minLength": 1,
"description": "Item name."
},
"type": {
"enum": [
"component",
"chart",
"block",
"template",
"pattern",
"hook"
],
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| name * | string | Item name. |
| type | string | one of ["component","chart","block","template","pattern","hook"] |
| packageManager | string | one of ["npm","pnpm","yarn","bun"] |
{
"name": "get_tests",
"title": "Get tests",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"minLength": 1,
"description": "Item name."
},
"type": {
"enum": [
"component",
"chart",
"block",
"template",
"pattern",
"hook"
],
"type": "string"
},
"packageManager": {
"enum": [
"npm",
"pnpm",
"yarn",
"bun"
],
"type": "string",
"default": "npm"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| name * | string | Item name. |
| type | string | one of ["component","chart","block","template","pattern","hook"] |
| since | string | A date (YYYY-MM-DD) or a library version (1.2.3). |
{
"name": "get_changes",
"title": "Get changes",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"minLength": 1,
"description": "Item name."
},
"type": {
"enum": [
"component",
"chart",
"block",
"template",
"pattern",
"hook"
],
"type": "string"
},
"since": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|\\d+\\.\\d+\\.\\d+)$",
"description": "A date (YYYY-MM-DD) or a library version (1.2.3)."
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| intent * | string | What the page is for. |
| includePro | boolean | Also pick Pro blocks and templates (they need a licence key). |
| packageManager | string | one of ["npm","pnpm","yarn","bun"] |
{
"name": "compose_page",
"title": "Compose a page",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"intent"
],
"properties": {
"intent": {
"type": "string",
"minLength": 3,
"description": "What the page is for."
},
"includePro": {
"type": "boolean",
"default": false,
"description": "Also pick Pro blocks and templates (they need a licence key)."
},
"packageManager": {
"enum": [
"npm",
"pnpm",
"yarn",
"bun"
],
"type": "string",
"default": "npm"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false
}
}How to prepare a project for this library: requirements, shadcn init, where files land, themes, dark mode and the Pro registry entry.
| Parameter | Type | Description |
|---|---|---|
| packageManager | string | one of ["npm","pnpm","yarn","bun"] |
{
"name": "get_setup",
"title": "Get setup",
"description": "How to prepare a project for this library: requirements, shadcn init, where files land, themes, dark mode and the Pro registry entry.",
"inputSchema": {
"type": "object",
"properties": {
"packageManager": {
"enum": [
"npm",
"pnpm",
"yarn",
"bun"
],
"type": "string",
"default": "npm"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false
}
}tealmac UI is a shadcn registry (namespace @tealmac, Pro items @tealmac-pro) of accessible React 19 and Tailwind CSS v4 components, charts, patterns, hooks, page blocks and templates. Use search_items or list_items to find candidates (list_categories shows what exists), get_item for props, usage and accessibility notes, get_examples for working example code, and get_install_command for the exact shadcn CLI command, which you run in the user's project (get_setup if it has no components.json). For a whole page use compose_page; it also suggests complete templates. Components install into components/ui, blocks and templates into components/tealmac-pro. Before you write or change UI, call get_quality_rules and build to them. When you finish, check the project with audit_project from the npm package (npx -y @tealmac/mcp runs it locally; this hosted server cannot read the user's files) and fix every error it reports. Before updating an installed item call get_changes; get_tests returns an item's tests to check it still works after edits. Pro items need a licence key.
Names, descriptions and schemas were written by the server and are shown as data.