UI Beats vs Yarr MCP
A side-by-side look at the UI Beats and Yarr MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose UI Beats for developer tools work as a local process; choose Yarr MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose UI Beats when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Choose Yarr MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
YARR_SERVICES, YARR_SONARR_URL, YARR_SONARR_API_KEY, YARR_MCP_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 49/100 · Fair | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | YARR_SERVICESYARR_SONARR_URLYARR_SONARR_API_KEYYARR_MCP_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 234 | 16 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View UI Beats | View Yarr MCP |
Tools & capabilities
UI Beats tools
No tool names declared yet. Check the project README from the listing page.
Yarr MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
UI Beats
{
"mcpServers": {
"ui-beats": {
"command": "npx",
"args": [
"-y",
"shadcn@latest"
]
}
}
}
Yarr MCP
{
"mcpServers": {
"yarr-mcp": {
"command": "npx",
"args": [
"-y",
"@dinglebear/yarr"
],
"env": {
"YARR_SERVICES": "YOUR_YARR_SERVICES_HERE",
"YARR_SONARR_URL": "YOUR_YARR_SONARR_URL_HERE",
"YARR_SONARR_API_KEY": "YOUR_YARR_SONARR_API_KEY_HERE",
"YARR_MCP_TOKEN": "YOUR_YARR_MCP_TOKEN_HERE"
}
}
}
}
Frequently asked questions
UI Beats is categorized under Developer Tools and uses a local stdio subprocess. Yarr MCP belongs to Developer Tools and uses a local stdio subprocess. Pick UI Beats for developer tools work and Yarr MCP for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
UI Beats has no declared pricing — check the project's own site. Yarr MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add ui-beats and yarr-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, UI Beats has a quality signal of 49/100 (Fair) with 0 views, 0 installs and 234 GitHub stars. Yarr MCP has 47/100 (Fair) with 1 views, 0 installs and 16 GitHub stars.