PrimeVue

You can query and explore PrimeVue components and design tokens through a dedicated MCP server. It exposes structured metadata, props, examples, and tooling to power AI assistants and development workflows, enabling fast discovery and integration of PrimeVue resources.

How to use

Connect your MCP client to the PrimeVue MCP Server to start querying components, tokens, and metadata. You can search by component name or description, retrieve detailed information about a component, list all available components with stats, or search design tokens. Use the provided HTTP endpoints to access the remote MCP server(s) and then leverage the client’s features to filter results, view props and examples, and integrate data into your tooling.

Recommended flow: 1) Choose an MCP server URL, 2) Use search components to locate items of interest, 3) Fetch detailed information with get component, 4) Browse design tokens with search tokens, 5) List components to understand coverage and stats. Your MCP client will present the results in a structured format that you can reuse in editors, AI prompts, or design tooling.

How to install

Prerequisites: you need Node.js installed on your machine. Ensure you have a modern npm version available to install dependencies and run scripts if you are setting up a local client or a local MCP bridge.

Step 1: Create or choose a project directory for your MCP client integration.

Step 2: Install necessary MCP client libraries or tooling as indicated by your integration approach. Use npm to install packages if required by your setup.

Step 3: Configure the MCP connection in your client. Point to the MCP server URL(s) you will use and ensure your environment can reach them over HTTP.

Notes and troubleshooting

Two HTTP MCP endpoints are available for PrimeVue MCP Server access. Use the provided URLs to connect your client: https://primevue-mcp-1.enol.dev and https://primevue-mcp-1.onrender.com. If you encounter connectivity issues, verify you can reach the URL from your network and that the server is reachable from your environment.

If you need to run a local stdio MCP process, check for explicit runtime commands in your setup. In this case, the source provides HTTP access points, so the HTTP configuration is the primary path for remote usage.

Security and access considerations

Only expose MCP server endpoints to trusted clients and networks. Use appropriate network controls and authentication as required by your environment to prevent unauthorized access to component metadata and design tokens.

Available tools

search_components

Search components by name, title, or description

get_component

Get detailed information about a specific component

search_tokens

Search design tokens

list_components

List all available components with stats