UI Beats vs Url
A side-by-side look at the UI Beats and Url 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 Url 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 Url when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
parse_url, build_url, parse_query.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 49/100 · Fair | 49/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 | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 234 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View UI Beats | View Url |
Tools & capabilities
UI Beats tools
No tool names declared yet. Check the project README from the listing page.
Url tools 3
parse_urlParse a URL into its components (keyless, offline): protocol, host, hostname, port, path, query (as an object), fragment, origin, and any userinfo.build_urlBuild a URL string from components. Provide at least `hostname` (and optionally protocol, port, path, hash) plus a `query` object of key/value pairs.parse_queryParse a query string (with or without a leading "?") into an object; repeated keys become arrays.
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"
]
}
}
}
Url
{
"mcpServers": {
"url": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-url"
]
}
}
}
Frequently asked questions
UI Beats is categorized under Developer Tools and uses a local stdio subprocess. Url belongs to Developer Tools and uses a local stdio subprocess. Pick UI Beats for developer tools work and Url 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. Url 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 url 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. Url has 49/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.