What does this MCP do?

It identifies the shadcn/ui components and packages required by any JSX or TSX code snippet you provide to your AI agent.

Which AI clients can use this?

You can use this with any MCP-compatible client, including Claude, Cursor, and Windsurf.

How does it help with shadcn/ui?

It prevents 'dependency blindness' by ensuring your agent knows exactly which base packages and sub-components are needed for the code it writes.

Does it install the components for me?

No, it identifies the dependencies so your agent can tell you exactly what needs to be installed.

Can it verify if a component is valid?

Yes, the validate_component_registry_entry capability checks if a string is a known shadcn/ui component.

What does the extract_dependencies capability return?

It returns a unique list of required components, the total count of detected components, and a list of any missing sub-components found in your snippet.

How does it identify components?

The capability scans your JSX for tags starting with an uppercase letter and matches them against a strict registry of shadcn/ui component families.

Can I verify a specific tag name?

Yes, you can use the validate_component_registry_entry capability to check if a specific string like 'AccordionItem' is recognized as a valid shadcn/ui component.

An astronaut overseeing a futuristic data hub

Download PDF Markdown Version

Connect Shadcnui Dependency Resolve (Alternative) to your AI

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Keep your AI agent from breaking your React components.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 3 capabilities

We ship only the actions that matter.

Capability set01 / 01

01-03

3 capabilities in this set.

Part of 3 available through shadcn/ui Resolver.

01
Extract dependencies
This capability analyzes JSX snippets to find required shadcn/ui components and identifies any missing sub-components. It returns the necessary packages and a count of missing tags.
02
List all registry components
This capability provides a full list of every shadcn/ui component the MCP can resolve. Use it to see what the agent is capable of identifying.
03
Validate component registry entry
This capability checks if a specific string is a recognized shadcn/ui sub-component or base component. It returns the component's status and its parent base package.

Real work

What teams actually run

Fixing AI Hallucinations

When an agent suggests a component that doesn't exist or isn't installed, this MCP validates the component against the real registry.

Automating Setup

The agent uses the extracted dependency list to tell you exactly which shadcn/ui components to install via CLI.

Code Auditing

You can pass large blocks of JSX to the agent to verify if all used components are valid shadcn/ui entries.

Component Mapping

The agent identifies which base package a specific sub-component belongs to before attempting to import it.

One connector, every AI

shadcn/ui Resolver works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put shadcn/ui Resolver to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

539ms average. Fast in production.

shadcn/ui Resolver is checked daily against the live service.

Daily averagePeak 623ms

Oct 3Today

Fastest day: 474ms
Slowest day: 623ms
14-day trend: Slowing+5%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 3 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of shadcn/ui Resolver, so you can see the experience inside your AI.

It does not authenticate your account with shadcn/ui Resolver. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

shadcn/ui Resolver Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_U9irMWgXv28cwSXxmqiAgD6Vnm7Obd7lVDbcbdVU/mcp

Claude Desktop

Follow the steps below to connect in seconds.

1In Claude Desktop, open Settings → Connectors.
2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
3Click Add and start a new chat — shadcn/ui Resolver capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "shadcnui-dependency-resolver-alternative-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_U9irMWgXv28cwSXxmqiAgD6Vnm7Obd7lVDbcbdVU/mcp"
    }
  }
}

Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up shadcn/ui Resolver in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work shadcn/ui Resolver owners hand off.

Frontend developers and engineers using AI agents to accelerate UI development.

01
Frontend Engineers
They use the MCP to ensure AI-generated React code matches their local shadcn/ui installation.
02
Full Stack Developers
They hand off UI component generation to agents and use this to prevent dependency errors.
03
AI Workflow Builders
They integrate this into agentic workflows to automate the setup of component libraries.

FAQ

Questions shadcn/ui Resolver owners ask.

01
What does this MCP do?
It identifies the shadcn/ui components and packages required by any JSX or TSX code snippet you provide to your AI agent.
02
Which AI clients can use this?
You can use this with any MCP-compatible client, including Claude, Cursor, and Windsurf.
03
How does it help with shadcn/ui?
It prevents 'dependency blindness' by ensuring your agent knows exactly which base packages and sub-components are needed for the code it writes.
04
Does it install the components for me?
No, it identifies the dependencies so your agent can tell you exactly what needs to be installed.
05
Can it verify if a component is valid?
Yes, the validate_component_registry_entry capability checks if a string is a known shadcn/ui component.
06
What does the extract_dependencies capability return?
It returns a unique list of required components, the total count of detected components, and a list of any missing sub-components found in your snippet.
07
How does it identify components?
The capability scans your JSX for tags starting with an uppercase letter and matches them against a strict registry of shadcn/ui component families.
08
Can I verify a specific tag name?
Yes, you can use the validate_component_registry_entry capability to check if a specific string like 'AccordionItem' is recognized as a valid shadcn/ui component.

Explore

More in Development

Connect shadcn/ui Resolver to Claude, Cursor, ChatGPT & more

Your AI does the work. We keep it safe and sound.

Each Connector runs inside its own sealed environment.

One switch stops every agent. Instantly.

Spending limits that pause instead of surprise.

We ship only the actions that matter.

01-03

Extract dependencies

List all registry components

Validate component registry entry

What teams actually run

Fixing AI Hallucinations

Automating Setup

Code Auditing

Component Mapping

Building your own app? The connector is yours to use.

shadcn/ui Resolver Connector

Claude Desktop

Frontend Engineers

Full Stack Developers

AI Workflow Builders

What does this MCP do?

Which AI clients can use this?

How does it help with shadcn/ui?

Does it install the components for me?

Can it verify if a component is valid?

What does the extract_dependencies capability return?

How does it identify components?

Can I verify a specific tag name?

shadcn/ui Dependency Resolver AI Connector

React 19 useActionState Validator AI Connector

Task DAG Dependency Resolver AI Connector

Postgres Migration Dependency Resolver AI Connector

Suggestions

Reactor Design CSTR AI Connector

Reactor Network Synthesis AI Connector

Dependency Version Conflict Detector AI Connector

Socket.dev (Dependency Security) AI Connector