UI Beats vs Wellness Project
A side-by-side look at the UI Beats and Wellness Project 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 Wellness Project for developer tools over a hosted endpoint. 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 Wellness Project when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 49/100 · Fair | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 234 | 2 |
| 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 Wellness Project |
Tools & capabilities
UI Beats tools
No tool names declared yet. Check the project README from the listing page.
Wellness Project 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"
]
}
}
}
Wellness Project
{
"mcpServers": {
"wellness-project": {
"url": "https://wellnessproject.ai/api/mcp"
}
}
}
Frequently asked questions
UI Beats is categorized under Developer Tools and uses a local stdio subprocess. Wellness Project belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick UI Beats for developer tools work and Wellness Project 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. Wellness Project has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 wellness-project 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. Wellness Project has 43/100 (Fair) with 1 views, 0 installs and 2 GitHub stars.