Yarr MCP vs TypeUI
A side-by-side look at the Yarr MCP and TypeUI MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Yarr MCP for developer tools work as a local process; choose TypeUI for architecture & design as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose TypeUI when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Architecture & Design |
| Quality signal | 47/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 | YARR_SERVICESYARR_SONARR_URLYARR_SONARR_API_KEYYARR_MCP_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 16 | 2,134 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Yarr MCP | View TypeUI |
Tools & capabilities
Yarr MCP tools
No tool names declared yet. Check the project README from the listing page.
TypeUI 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.
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"
}
}
}
}
TypeUI
{
"mcpServers": {
"typeui": {
"command": "npx",
"args": [
"-y",
"typeui.sh"
]
}
}
}
Frequently asked questions
Yarr MCP is categorized under Developer Tools and uses a local stdio subprocess. TypeUI belongs to Architecture & Design and uses a local stdio subprocess. Pick Yarr MCP for developer tools work and TypeUI for architecture & design.
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.
Yarr MCP has no declared pricing — check the project's own site. TypeUI 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 yarr-mcp and typeui as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Yarr MCP has a quality signal of 47/100 (Fair) with 1 views, 0 installs and 16 GitHub stars. TypeUI has 47/100 (Fair) with 2 views, 0 installs and 2,134 GitHub stars.