shadcn/ui answers in Perplexity
Add the connector and Perplexity answers UI questions from the registry, with a component's props, a demo and the install, rather than from blog posts. It's part of shadcn.io Pro.
- Kind
- App
- Goes in
Settings → Connectors- Connects
- Through mcp-remote
- Team config
- No
Add it to the Mac app
Perplexity's Mac app runs the server through mcp-remote, a small bridge from npm. With Pro, the JSON beside these steps is already filled in with your URL.
Copy the JSON
It starts
npx -y mcp-remotewith your MCP URL, token included. No token yet? Create one on your account.Install Node.js and PerplexityXPC
npxships with Node.js (brew install nodeis one way). Perplexity also asks you to install its helper app, PerplexityXPC, before it lets you add a local connector.Add a custom connector
Open Plugins in the sidebar (Customize → Connectors if you don't have Plugins yet), choose Add custom and add an MCP connector. On the Advanced tab, enter
shadcnioas the Server Name, paste the JSON and select Save.Wait for Running, then turn it on
Open it under Plugins → Installed and wait for Running. Then, in a new thread, open Sources and switch
shadcnioon.
How it reads, with YOUR_TOKEN where your token goes:
{ "args": [ "-y", "mcp-remote", "https://www.shadcn.io/api/mcp?token=YOUR_TOKEN" ], "command": "npx", "env": {} }
Perplexity keeps the connector in the app, with no file to commit, and the token travels only from your Mac to shadcn.io. Treat it as a key: regenerate it if it leaks.
| Route | Who can use it | What goes in |
|---|---|---|
| Local connector, Advanced tab | The Mac app, with Node.js and PerplexityXPC | The JSON beside these steps |
| Remote connector (opens in a new tab) | Perplexity Pro, Max and Enterprise, no Node.js | Your MCP URL, authentication None |
| Enterprise member | Once an admin allows custom connectors (off by default) | A remote connector, with your own URL |
Watch it reach Running
Perplexity lists connectors under Plugins → Installed, each with its state: a working shadcnio reads Running, with its tool count.
- Open Plugins → Installed (or Customize → Connectors) and find
shadcnio. - Wait for Running, with 22 tools available.
- In a new thread, open Sources and switch
shadcnioon. - Ask the prompt below and confirm the call: Perplexity runs
whoamiand answers with your account, your plan and the calls left this minute.
Three questions, asked in Perplexity
Each starts as a question in a thread, the way Perplexity gets used: the calls it makes, then what you get back. Switch the MCP off to see the same question answered from the web.
- shadcn.io MCP connected · 22 tools
MCP call: search_components({ query: "multi select tags" })Returns: combobox, the closest matchMCP call: get_component_api({ name: "combobox", prop: "multiple" })Returns: On the root: several picks, the value an arrayMCP call: get_component({ name: "combobox", include: ["install", "demo"], demo: "multiple" })Returns: npx shadcn add …/r/combobox.json, and the chips demoAgent step: Wrote the answer: why a combobox, the command, the demoReturns: One reply, nothing pieced together from the web
In your project
Combobox, multiple
- Chips with remove buttons, typing to filter
- The install for your React app, in one line
1 prompt → 3 MCP calls
Questions to ask it
A thread starts without your project, so each one names the server and the framework.
Getting more from it in Perplexity
Sources, confirmations, your profile and the bridge: the parts of Perplexity that decide how well the MCP answers.
Switch it on in Sources
A connector only answers in threads where it's switched on: open Sources in the message box and turn
shadcnioon. Leave Web on to mix in articles, or turn it off to answer from the registry alone.Confirming a call is safe
Perplexity asks before it runs a connector's tool, and you confirm in the thread. All 22
shadcniotools only read the registry, so a yes never changes your files, your project or your account.Put your stack in your profile
A new thread knows nothing about your project. Your profile's instructions in Settings apply to every question, so write your stack there once, and that UI questions go to
shadcnio.For questions about UI components, use the shadcnio connector. My stack: Next.js, React, Base UI, pnpm.
Give it the full path to npx
Perplexity may not find
npxwhen Node.js came from nvm or another version manager. Put the path thatwhich npxprints in Terminal intocommand; with Homebrew on Apple silicon, it's usually this one."command": "/opt/homebrew/bin/npx"
Or add it as a remote connector
On Pro, Max or Enterprise, skip Node.js: Plugins → Add custom → Connector → Add MCP connector, choose Remote and fill in the form as below. Tick the acknowledgement, select Add, then its card to turn it on.
Name: shadcnio MCP Server URL: YOUR_MCP_URL Authentication: None Transport: Streamable HTTP
Keep the token out of the URL
The Advanced tab's
envreachesmcp-remote, which fills${AUTH_HEADER}in from it. Use your URL without?token=, and the token travels as anAuthorizationheader instead.{ "args": [ "-y", "mcp-remote", "https://…/api/mcp", "--header", "Authorization:${AUTH_HEADER}" ], "command": "npx", "env": { "AUTH_HEADER": "Bearer YOUR_TOKEN" } }
When it won't answer
Most problems come down to the bridge, the token or the Sources switch. The troubleshooting guide has every client's fixes.
shadcnionever shows Running under Plugins → Installed.- Perplexity couldn't start the command. Run
npx -y mcp-remote "YOUR_MCP_URL"in Terminal: if Node.js is missing or older than 18, install a current one; if it connects there, give the connector the full path tonpx. - Tool calls come back with a 401.
- The token in the connector's URL is missing, or older than your last regenerate. Copy the JSON from this page again and edit the connector, or delete
shadcnioand add it back. - Tool calls come back with a 403.
- A 403 says the token is real but the Pro plan on its account isn't active. Renew from pricing and leave the connector as it is.
- It shows Running, yet the answer cites web pages and never calls
shadcnio. - Switch it on under Sources in that thread, and make sure no Web-only, Academic or Social filter is set. Then name it:
use shadcnio to…. - There's no way to add a local connector.
- Local connectors need the Mac app with PerplexityXPC installed; update the app if the option is missing. On Windows or the web, add
shadcnioas a remote connector (opens in a new tab) instead. - Your Enterprise account can't add custom connectors.
- Admins decide: Allow members to add custom connectors, in Enterprise settings, is off by default. Ask for it, so each person's connector keeps their own token.
Get the MCP for Perplexity with Pro
The MCP comes with every Pro plan, with every block and premium template, for you or your whole team. Monthly, yearly or lifetime.
4.9/5 out of 5 · 150+ reviewsfrom 150+ founders and developers.
- Secure checkout via Stripe
- Code lives in your repo
- Keep what you've shipped if you cancel
- License terms
Frequently asked questions
The shadcn MCP in Perplexity: setup, limits, and the rest.
Open Plugins in the sidebar, choose Add custom and add an MCP connector. On the Advanced tab, enter shadcnio as the Server Name, paste the JSON from this page and save. Perplexity first asks you to install its helper app, PerplexityXPC. Wait for Running, then switch shadcnio on under Sources in a new thread.
The local connector is a command Perplexity starts on your Mac, while the shadcn server lives on the web. npx, which ships with Node.js, fetches mcp-remote, and mcp-remote passes each call from Perplexity on to your MCP URL. A remote connector skips Node.js entirely.
Not as a local connector: Perplexity runs those only in its Mac app. On Windows, the web or a phone, add shadcnio as a remote connector instead, with your MCP URL and authentication set to None. That needs Perplexity Pro, Max or Enterprise, and nothing runs on your device.
It may not when Node.js came from nvm or another version manager. Put the path that which npx prints in Terminal into the connector's command field. With Homebrew on Apple silicon, that is usually /opt/homebrew/bin/npx.
Perplexity asks before it runs any connector's tool, which is a sensible default. Every shadcnio tool only reads the registry: none of them can change your files, your project or your account, so confirming is safe.
It hands you the install instead. For React, that's one npx shadcn add command with your token in it, to run in your project's terminal. For Vue, Svelte and Solid, the answer lists every file with its path and the packages to add, ready to copy.
Say it in the question (Next.js on Radix, Nuxt, SvelteKit, SolidStart), or write your stack once in your profile's instructions so every thread starts with it. Without one, the tools answer for React on Base UI.
A web search finds articles written for whatever version their authors had, and Perplexity summarizes them. The connector answers from the registry itself: the component's current props, its demos and its install, for your framework, with nothing to reconcile.
Two plans are involved. On Perplexity's side, the local connector runs in the Mac app, and remote custom connectors come with Pro, Max and Enterprise. On shadcn.io's side, the server needs a Pro plan: monthly, yearly or lifetime, or a Team or Organization plan that covers every member.
Not with one shared connector. Each person adds shadcnio with their own token, locally or as a remote connector, and a Team or Organization plan at shadcn.io gives every member Pro access. A connector shared by one person would carry that person's token for everyone.
Admins decide: Allow members to add custom connectors, in Enterprise settings, is off by default. Ask for it, so each person's connector keeps their own token.
With the local connector, the URL sits in the connector on your Mac, and mcp-remote sends it to shadcn.io alone. A remote connector holds the same URL in its form. Should it leak, regenerate the token on your account page: the old one stops working within a few minutes, and you edit the connector to hold the new URL.
Yes. In the local connector's Advanced JSON, use the URL without ?token=, add an Authorization header argument for mcp-remote and put the token in the connector's env block. The token then travels as a header instead of a query string.
Only the tool calls, such as a requested component, a chosen framework or a query. The rest of your thread and your files stay with Perplexity and your device, and every shadcnio tool only reads from the registry.
Perplexity couldn't start the command. Run npx -y mcp-remote with your MCP URL in Terminal: if Node.js is missing or older than 18, install a current one, and if it connects there, give the connector the full path to npx.
A 401 means the token in the connector's URL is missing or older than your last regenerate: copy the JSON again and edit the connector. A 403 means the token is real but Pro isn't active on that account. A 429 is the per-token ceiling of 600 calls a minute; pause for as long as Retry-After says.
Switch shadcnio on under Sources in that thread, and make sure no Web-only, Academic or Social filter is set. Then name it in the question: use shadcnio to...
Using another agent too?
The same URL works in every MCP client: use it beside Perplexity, in your editor, your terminal or your chat app.
4.9 out of 5 from 150+ developers
Ask Perplexity, get the real component
Every component, 6,231 blocks and 294k icons behind one Perplexity connector, with any shadcn.io Pro plan.
Get Pro