
Primereact Mcp
io.github.wisdomrockPublished by GitHub account wisdomrockv1.2.3Updated Oct 24, 2026
105 PrimeReact v10 components with props, types, and events
Overview
Local MCP server exposing PrimeReact v10 component documentation — props, events, examples and search — so an assistant can look up and compare UI components.
- What you can do
- List and search components, filter by category, and get suggestions for a use case
- Inspect a component's props, events, methods, slots, pass-through options, design tokens and CSS classes
- Retrieve sections, usage examples, import statements and official documentation links
- Find components by prop, event or feature, and compare two components side by side
- Check version and compatibility info, and list form, data and overlay component groups
- When to use it
- Useful when building or maintaining a React UI with PrimeReact v10 and you want the assistant to answer questions about component APIs, pick the right component, or produce correct imports and examples without guessing.
- Requirements
- Node.js 18 or later; runs locally over stdio, typically via npx with no install, or from a cloned repository. Component data ships pre-generated in the package. No accounts, API keys or environment variables are declared.
Installation
In SourceWeft
- Open Primereact Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
primereact-mcp
A Model Context Protocol (MCP) server that gives AI assistants full access to PrimeReact v10 component documentation — props, events, examples, and search.
Why does this exist?
The PrimeReact team has not yet published an official@primereact/mcppackage. This server fills that gap using the same engine (@primeuix/mcp) that powers the official PrimeNG MCP server, with component data extracted from PrimeReact's TypeScript definitions. The official PrimeReact MCP will be launched with v11.
Features
- 105 PrimeReact v10 components with full prop/event documentation
- 15+ MCP tools: search, suggest, inspect props, get examples, compare components, and more
- Works with Claude Code, Claude Desktop, Cursor, Windsurf, and any MCP-compatible client
- Generated directly from PrimeReact's TypeScript
.d.tssource — no stale hand-written docs
Quick Start
Prerequisites
- Node.js 18 or later
- An MCP-compatible AI client (see below)
Option A — npx (no install needed)
Use npx -y primereact-mcp directly in your MCP client config. Component data ships pre-generated inside the package.
Option B — clone and run locally
To regenerate component data after a PrimeReact version upgrade:
MCP Client Setup
Claude Code (CLI)
Or add it to your project's .mcp.json:
Claude Desktop
Add the following to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
Cursor
Add to .cursor/mcp.json in your project root:
Windsurf
Add to ~/.codeium/windsurf/mcp_config.json:
Available Tools
Example prompts
Upgrading PrimeReact Version
To update the component data after upgrading PrimeReact:
The generate-data.mjs script re-reads all .d.ts files and rewrites components-data.json.
Project Structure
MCP Registry
This server is published to the Official MCP Registry. Registry metadata is in server.json at the repo root.
How it works
-
generate-data.mjsreads each component's.d.tsfile from theprimereactnpm package, parses JSDoc comments and TypeScript interface definitions using a line-by-line state machine, and writes structured JSON tocomponents-data.json. -
index.mjscallsrunPrimeMcpServer()from@primeuix/mcp— the same shared engine used by the official PrimeNG MCP server — passing PrimeReact-specific configuration and the generated component data.
Contributing
Contributions welcome! Areas that would benefit from improvement:
- Richer examples — add JSX code snippets to more component sections
- PrimeReact v11 support — the alpha v11 uses
@primereact/types, requiring a different parsing strategy - Pass Through (PT) data — extract PT options from
.d.tsfiles - Design tokens — extract CSS variable names
Please open an issue before sending a large PR.
License
MIT — see LICENSE.
Related
- @primeng/mcp — Official MCP server for PrimeNG (Angular)
- @primeuix/mcp — Shared MCP engine by the PrimeFaces team
- PrimeReact Documentation
- Model Context Protocol
Source: README.md at commit 9685499
Tools
0Version history
1- v1.2.3LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts