VengeanceUI MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@VengeanceUI MCP Server search for animated card components"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
VengeanceUI MCP Server
An Model Context Protocol (MCP) server that brings 129 beautiful VengeanceUI components directly to your AI assistant! Browse, search, and retrieve component source code from the VengeanceUI GitHub repository seamlessly within Claude Desktop, Cursor, or any MCP-enabled tool.
β¨ Features
π¨ 129+ Components: Access the complete VengeanceUI component library
π Smart Search: Search by name, category, tags, or description with fuzzy matching
π¦ Full Source Code: Get complete component code with metadata
ποΈ Category Filtering: Browse by Buttons, Cards, Forms, Navigation, and more
π Component Metadata: View dependencies, tags, file size, and source URLs
β‘ Smart Caching: Built-in 5-minute cache for faster responses
π Real-time Sync: Components loaded directly from the latest GitHub repository
Related MCP server: shadcn MCP Server
π Quick Start
Prerequisites
Node.js: v18 or higher (tested with v22.17.0)
npm: Latest version
Claude Desktop or Cursor IDE (or any MCP-compatible client)
Installation
Clone this repository:
git clone https://github.com/krockxz/VengeanceUI-MCP.git cd VengeanceUI-MCPInstall dependencies:
npm installBuild the project:
npm run buildYou should see:
> vengeanceui-mcp-server@1.0.0 build > tscVerify the build:
ls -lh dist/server.js
βοΈ Configuration
For Claude Desktop
Locate your configuration file:
Linux:
~/.config/Claude/claude_desktop_config.jsonmacOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Add the VengeanceUI server configuration:
{ "mcpServers": { "vengeanceui": { "command": "node", "args": ["/absolute/path/to/mcp VengeanceUI/dist/server.js"] } } }β οΈ Important: Replace
/absolute/path/to/with your actual absolute path!Example on Linux:
"args": ["/home/kunal/Documents/mcp VengeanceUI/dist/server.js"]Restart Claude Desktop:
Linux: Press
Ctrl + Ror fully restart the applicationmacOS/Windows: Fully quit and restart Claude Desktop
Verify the server is running:
Look for the π¨ tool icon in the bottom-right corner of Claude Desktop
Click it to see available MCP servers
You should see "VengeanceUI MCP Server" listed
For Cursor IDE
Create or edit
.cursor/mcp-servers.jsonin your project:{ "mcpServers": { "vengeanceui": { "command": "node", "args": ["/absolute/path/to/mcp VengeanceUI/dist/server.js"] } } }Restart Cursor IDE
Optional: GitHub Token for Higher Rate Limits
Adding a GitHub token increases API rate limits from 60 to 5000 requests/hour.
Create a GitHub Personal Access Token:
Click "Generate new token (classic)"
Select scope:
public_repo(read access to public repositories)Copy the generated token (starts with
ghp_)
Update your configuration:
{ "mcpServers": { "vengeanceui": { "command": "node", "args": ["/absolute/path/to/mcp VengeanceUI/dist/server.js"], "env": { "GITHUB_TOKEN": "ghp_your_token_here" } } } }Restart your MCP client
π οΈ Available Tools
The server provides 7 powerful tools for working with VengeanceUI components:
1. list_components
List all available VengeanceUI components with their categories and descriptions.
Parameters:
category(optional): Filter by category (e.g., "Buttons", "Cards", "Forms")limit(optional): Maximum number of components to return
Example prompts:
"List all VengeanceUI components"
"Show me the first 20 components"
"List all components in the Buttons category"
2. search_components
Search for components using fuzzy matching across names, categories, tags, and descriptions.
Parameters:
query(required): Search termlimit(optional): Maximum results to return (default: 10)
Example prompts:
"Search for button components"
"Find animated card components"
"Search for gradient effects"
3. get_component_code
Retrieve the complete source code for a specific component with metadata.
Parameters:
component_name(required): Exact or partial component nameinclude_metadata(optional): Include metadata like tags, dependencies (default: true)
Example prompts:
"Get the code for AnimatedButton"
"Show me the source code for GradientCard"
"Get button.tsx code"
4. get_components_by_category
Get all components in a specific category.
Parameters:
category(required): Component category name
Example prompts:
"Show all components in the Forms category"
"What's in the Navigation category?"
5. get_component_info
Get detailed metadata about a component including dependencies, file size, and tags.
Parameters:
component_name(required): Component name
Example prompts:
"Get info for AnimatedButton"
"What are the dependencies for GradientCard?"
6. list_categories
List all component categories with component counts.
Example prompts:
"List all categories"
"What categories are available in VengeanceUI?"
7. refresh_cache
Force refresh the component cache from the GitHub repository.
Example prompts:
"Refresh the VengeanceUI component cache"
"Update the component list"
π‘ Usage Examples
Once configured in Claude Desktop, try these natural language prompts:
Discovery
"What VengeanceUI components are available?"
"List all categories in VengeanceUI"
"How many components are there in total?"Search
"Find all button components"
"Search for gradient or animated components"
"Show me navigation components"Get Code
"Get the code for button.tsx"
"Show me the AnimatedButton component"
"I need the source code for GradientCard"Browse by Category
"Show all components in the Buttons category"
"What forms components are available?"
"List all navigation components"Component Details
"Get detailed info for AnimatedButton"
"What dependencies does the GradientCard component have?"
"Show me the metadata for button.tsx"π§ Development
Development Mode
Run the server in watch mode:
npm run devBuild
Compile TypeScript to JavaScript:
npm run buildWatch Mode
Automatically rebuild on file changes:
npm run watchπ How It Works
Component Discovery: The server connects to the VengeanceUI GitHub repository and scans the following directories:
registry/new-york/- Main component registrysrc/components/- Source components
Intelligent Parsing:
Extracts component names from filenames
Parses code to detect categories, tags, and dependencies
Analyzes JSDoc comments for descriptions
Identifies animation, styling, and interaction patterns
Smart Caching:
Components are cached for 5 minutes
Reduces GitHub API calls
Automatic refresh on cache expiration
MCP Integration:
Implements the Model Context Protocol
Exposes 7 tools via stdio transport
Provides structured responses with metadata
π Troubleshooting
Server doesn't appear in Claude Desktop
Check configuration file syntax:
cat ~/.config/Claude/claude_desktop_config.json | jq .If
jqshows an error, your JSON is malformed.Verify the server file exists:
ls -lh "/absolute/path/to/mcp VengeanceUI/dist/server.js"Check Claude Desktop logs:
# Find log directory find ~ -name "*Claude*" -type d 2>/dev/null | grep -i log # View logs tail -f ~/.config/Claude/logs/mcp*.logTest the server manually:
cd "mcp VengeanceUI" node dist/server.js
No components are loading
Check GitHub API rate limits:
Without token: Limited to 60 requests/hour
Solution: Add a GitHub token (see Configuration section)
Force refresh the cache:
Use the prompt: "Refresh the VengeanceUI component cache"
Components are outdated
The cache refreshes every 5 minutes. To force an immediate refresh, use the refresh_cache tool via this prompt:
"Refresh the VengeanceUI component cache"π Acknowledgments
VengeanceUI - For the incredible component library featuring beautiful, animated components
Model Context Protocol - For the server framework enabling AI assistant integration
shadcn-ui-mcp-server - Inspiration for this project
π Links
VengeanceUI Repository: https://github.com/Ashutoshx7/VengeanceUI
MCP Documentation: https://modelcontextprotocol.io
Issues & Support: Open an issue in this repository
Available Tools
7 toolsget_component_codeA
Get the complete source code for a specific VengeanceUI component
Inputs: component_name (required), include_metadata.
get_component_infoA
Get detailed information about a component including metadata, dependencies, and stats
Inputs: component_name (required).
get_components_by_categoryA
Get all components in a specific category
Inputs: category (required).
list_categoriesA
List all component categories with counts and descriptions
Inputs: no named parameters.
list_componentsA
List all available VengeanceUI components with their categories and descriptions
Inputs: limit, category.
refresh_cacheB
Force refresh the component cache from the GitHub repository
Inputs: no named parameters.
search_componentsA
Search for VengeanceUI components by name, category, tags, or description with fuzzy matching
Inputs: query (required), limit.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 7 tools
Most tools have clearly distinct purposes, but get_component_info and get_component_code both target a specific component, which could cause confusion. However, the descriptions clarify that one returns metadata and the other returns source code, so the ambiguity is minor.
All tool names follow a consistent verb_noun pattern in snake_case (list_components, search_components, get_component_code, get_components_by_category, etc.), making the naming predictable and easy to learn.
With 7 tools, the server is well-scoped for a component library. Each tool serves a distinct function, and the count is within the ideal range for a focused MCP server.
The tool set covers the full lifecycle for a read-only component library: listing, searching, retrieving code and info, browsing by category, listing categories, and cache refresh. No obvious functional gaps exist.
Maintenance
Related MCP Connectors
Find UI components and themes, retrieve code, and generate with hosted 21st AI when enabled.
Code intelligence for LLMs. Analyze, search, and retrieve code from any public git repository.
Connect AI assistants to your GitHub-hosted Obsidian vault to seamlessly access, search, and analyβ¦
Search, read and install ReUI shadcn components, examples, blocks and icons from your coding agent.
Related MCP Servers
AlicenseCqualityDmaintenanceProvides AI assistants with comprehensive access to Grafana's React component library, including TypeScript source code, MDX documentation, Storybook examples, test files, and design system tokens for building Grafana-compatible interfaces.1359 npm9MIT- FlicenseAqualityDmaintenanceProvides AI assistants with direct access to shadcn/ui components and blocks, enabling real-time fetching of component source code, documentation, and implementation examples.422 npm4-
- AlicenseAqualityDmaintenanceProvides AI assistants with comprehensive access to shadcn/ui v4 components, blocks, demos, and metadata across React, Svelte, Vue, and React Native, enabling efficient component integration and code generation.106,787 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to retrieve NHS.UK frontend component templates, styles, macro options, and usage examples directly from the source repository.8 npm1MIT