Use evex agents from your editor with the shadcn MCP server
Browse and install evex agents from Cursor, VS Code, or Claude Code through the shadcn MCP server. Setup steps and example prompts for @evex/{slug} items.
What the shadcn MCP server does
The shadcn project ships an MCP server that lets AI-assisted editors discover and install registry items through the Model Context Protocol. Clients such as Cursor, VS Code, and Claude Code can search a registry, inspect items, and run installs from a conversation.
Because evex is part of the shadcn community registry, the MCP server addresses every evex agent as @evex/{slug}. You need no evex-specific server or configuration.
Set up the MCP server
Configure the shadcn MCP server in your editor by following the official setup guide for your client. Once you register the server, your assistant resolves @evex items the same way the CLI does.
https://ui.shadcn.com/docs/mcpExample prompts
With the server configured, ask your assistant in plain language. It searches the catalog, shows what an item contains, and runs the install for you.
- Install @evex/code-reviewer into this project
- Find an evex agent that reviews pull requests
- Show me the files @evex/{slug} will add before installing it
- List evex agents in the devops category
What happens on install
An MCP-driven install produces the same result as running the shadcn CLI yourself: the agent source lands under agent/ in your project, along with evals, the README, and any .env.example. Review the written files, fill in credentials from the environment template, and run the evals before relying on the agent.