VengeanceUI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | Optional GitHub personal access token for higher API rate limits. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_componentsA | List all available VengeanceUI components with their categories and descriptions |
| search_componentsA | Search for VengeanceUI components by name, category, tags, or description with fuzzy matching |
| get_component_codeA | Get the complete source code for a specific VengeanceUI component |
| get_components_by_categoryA | Get all components in a specific category |
| get_component_infoA | Get detailed information about a component including metadata, dependencies, and stats |
| list_categoriesA | List all component categories with counts and descriptions |
| refresh_cacheB | Force refresh the component cache from the GitHub repository |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.