Wisty UI

ai.wistyPublished by wisty.aiOfficial publisherv1.0.0Updated Nov 5, 2026

Find, read and install shadcn components with Salesforce Lightning's look, for Radix and Base UI.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Searches, reads and installs Wisty UI shadcn components styled like Salesforce Lightning, with examples and shadcn CLI install steps.

What you can do
  • Search components by the job they do, ranked best first
  • List all items by kind (primitive, component, block, helper) with names and first sentences
  • Read one item's docs: install command, examples, when to use, usage, rules and API reference
  • Fetch the code of a working example for the project's base
  • Get shadcn CLI install steps, including the theme step and Salesforce icon sprite copying
When to use it
Useful when building React apps with shadcn, Radix or Base UI that need a Salesforce Lightning look, or when an assistant should pick, read and install the right registry item instead of guessing component APIs.
Requirements
A remote MCP endpoint; no package, account, key or header is declared. The project should use shadcn with a components.json, and the install steps assume the shadcn CLI and Node.js are available locally.
Before you install
Install steps write files into the project, including the theme in the stylesheet and icon sprites in static files; review them before running. Passing the style from components.json keeps the API accurate. Docs are also published as Markdown on the vendor's site.

Installation

In SourceWeft

  1. Open Wisty UI in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.wisty%2Fui/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "wisty-ui": {
      "type": "http",
      "url": "https://ui.wisty.ai/mcp"
    }
  }
}

Tools

5

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.

Parameterskindlimitqueryrequired

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.

Parameterskind

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.

Parametersnamerequiredstylesourcesections

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.

Parametersnamerequiredstyleexample

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.

ParametersnamerequiredstylerequiredsrcDirthemedtailwindCss

Version history

1
  1. v1.0.0LatestNov 5, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.