Wisty UI MCP
An MCP server that allows AI agents to search and read documentation for Wisty UI, a shadcn registry providing React components styled with Salesforce Lightning Design System (SLDS) for Radix and Base UI projects.
Endpoint and access
No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.
https://ui.wisty.ai/mcpWhat its tools do
5 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.
Checks and signals
Each line is separate evidence, not a trust score.
- Passed Endpoint answered the live check ·
- Passed Official MCP Registry namespace is tied to wisty.ai ·
- Passed Endpoint is on the registry namespace domain ·
- Availability 1 of 1 checks passed in 30 days
What you can do with it
- Search for specific UI components within the Wisty UI registry
- Read documentation and API references for Wisty UI components
- Identify when to use or avoid specific components based on docs
Source and maintenance
Protocol and capabilities
- Server
- wisty-ui 2026.11.06-3de83f6-dirty
- MCP protocol negotiated in check
- 2025-11-25
- Tools
- 5 advertised
- Resources
- Not advertised
- Resource templates
- Not advertised
- Prompts
- Not advertised
{
"tools": {
"listChanged": false
}
}Server-provided instructions
Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.
Tools
5 advertised
search_components — Search Wisty UI
Find Wisty UI components by the job they do, ranked best first. Use one to three short keywords, like "record picker", "picklist", "toast" or "confirm delete", not a sentence. Each match gives the item's name, kind (primitive, component, block, helper), its description and, when its docs hold the query's words, the line of its When to use or When not to use that does. Read a match with get_component.
{
"type": "object",
"required": [
"query"
],
"properties": {
"kind": {
"enum": [
"primitive",
"component",
"block",
"helper"
],
"type": "string",
"description": "Only items of this kind."
},
"limit": {
"type": "integer",
"default": 8,
"maximum": 20,
"minimum": 1,
"description": "The most matches to return."
},
"query": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "One to three keywords for the job."
}
},
"additionalProperties": false
}{
"title": "Search Wisty UI",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}list_components — List Wisty UI
List every Wisty UI item by kind, with its name and first sentence, optionally only one kind. Primitives are shadcn's own components with the Salesforce look; components are what shadcn lacks, like lookup; blocks are Salesforce assemblies over sample data; helpers turn records into a block's props. Prefer search_components when you know the job.
{
"type": "object",
"properties": {
"kind": {
"enum": [
"primitive",
"component",
"block",
"helper"
],
"type": "string",
"description": "Only items of this kind."
}
},
"additionalProperties": false
}{
"title": "List Wisty UI",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}get_component — Read a Wisty UI item
Read one Wisty UI item: its install command, its examples by name, When to use, When not to use, Usage, Rules, its API reference for the project's base, then its longer docs sections. Pass style from components.json so the API matches the project. An agent that already knows the item can ask for only some sections, like ["Rules"] or ["API reference"]. With source: true it adds the installable files, which you rarely need: install with the shadcn command instead.
{
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "The item's name, like \"lookup\", as search_components and list_components give it."
},
"style": {
"type": "string",
"description": "The \"style\" field of the project's components.json, like \"radix-nova\" or \"base-nova\". It picks the Radix or Base UI version. Leave it out for the Radix version."
},
"source": {
"type": "boolean",
"default": false,
"description": "Add the item's installable files, for reading or copying by hand."
},
"sections": {
"type": "array",
"items": {
"enum": [
"When to use",
"When not to use",
"Usage",
"SLDS mapping",
"Keyboard interactions",
"Accessibility",
"Motion",
"Responsive behavior",
"Performance",
"Rules",
"Examples",
"API reference"
],
"type": "string"
},
"description": "Only these parts, under the item's title and install command. Leave it out for all of them."
}
},
"additionalProperties": false
}{
"title": "Read a Wisty UI item",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}get_example — Read a Wisty UI example
Get the code of one example of a Wisty UI item, for the project's base: a complete, working use you can adapt. Without example, the first one, which shows the job the item is for. A page block's first example is the files its install writes, the page first; any other example that imports its item's own files, like its sample data, is followed by them. get_component lists each item's examples by name.
{
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "The item's name, like \"lookup\", as search_components and list_components give it."
},
"style": {
"type": "string",
"description": "The \"style\" field of the project's components.json, like \"radix-nova\" or \"base-nova\". It picks the Radix or Base UI version. Leave it out for the Radix version."
},
"example": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "The example's name, like \"default\"."
}
},
"additionalProperties": false
}{
"title": "Read a Wisty UI example",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}get_install_command — Install a Wisty UI item
Get the steps to install one Wisty UI item with the shadcn CLI: the npx shadcn command, the theme step that writes Wisty UI's theme into the project's stylesheet once, and, for an item that draws Salesforce icons, the step that copies their sprites to the app's static files. Read style and tailwind.css from the project's components.json, and whether the project has a src/ folder, first; a project without one runs npx shadcn@latest init before anything else.
{
"type": "object",
"required": [
"name",
"style"
],
"properties": {
"name": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "The item's name, like \"lookup\", as search_components and list_components give it."
},
"style": {
"type": "string",
"description": "The \"style\" field of the project's components.json, like \"radix-nova\" or \"base-nova\". It picks the Radix or Base UI version."
},
"srcDir": {
"type": "boolean",
"description": "Whether the project has a src/ folder, where the shadcn CLI puts the theme files. Without it, a tailwindCss under src/ is taken to mean one."
},
"themed": {
"type": "boolean",
"description": "True when the stylesheet already has Wisty UI's theme: --color-page in its @theme inline, or an import of tokens.css. Leaves the theme step out."
},
"tailwindCss": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "The \"tailwind.css\" path from components.json, like \"src/index.css\", relative to the project. It gives the exact lines for importing the theme by hand; without it, the steps name the files to import instead."
}
},
"additionalProperties": false
}{
"title": "Install a Wisty UI item",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}Prompts
Not advertised
Resources
Not advertised
30-day availability
Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.
- Successful checks
- 1 of 1 (100%)
- Average latency
- 509 ms
- 95th percentile latency
- 509 ms
Maintenance history
Public check and source-refresh events. Editorial and ownership records remain private.
- · probe · passed · 509 ms · metadata changed · 5 tool(s)
Connect from your client
Each snippet registers the same endpoint; pick the client you use.
Claude Code
claude mcp add --transport http wisty-ui-mcp https://ui.wisty.ai/mcpCodex
codex mcp add wisty-ui-mcp --url https://ui.wisty.ai/mcpCursor
{
"mcpServers": {
"wisty-ui-mcp": {
"url": "https://ui.wisty.ai/mcp"
}
}
}Cline
{
"mcpServers": {
"wisty-ui-mcp": {
"type": "streamableHttp",
"url": "https://ui.wisty.ai/mcp",
"disabled": false
}
}
}VS Code
{
"servers": {
"wisty-ui-mcp": {
"type": "http",
"url": "https://ui.wisty.ai/mcp"
}
}
}Gemini CLI
gemini mcp add --transport http wisty-ui-mcp https://ui.wisty.ai/mcpClaude Desktop
https://ui.wisty.ai/mcpWindsurf
{
"mcpServers": {
"wisty-ui-mcp": {
"serverUrl": "https://ui.wisty.ai/mcp"
}
}
}Let your agent find its tools
Find servers like Wisty UI MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.
Other developer tools servers
Do you run Wisty UI MCP?
Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.