Travel Art MCP vs Url
A side-by-side look at the Travel Art MCP 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 Travel Art MCP for art & culture work over a hosted endpoint; 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 Travel Art MCP when
- You need dedicated capabilities in the Art & Culture domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
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 | Art & Culture | Developer Tools |
| Quality signal | 51/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Travel Art MCP | View Url |
Tools & capabilities
Travel Art MCP 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.
Travel Art MCP
{
"mcpServers": {
"alexzavialov-travel-art-mcp": {
"url": "https://mcp.travel.art/health"
}
}
}
Url
{
"mcpServers": {
"url": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-url"
]
}
}
}
Frequently asked questions
Travel Art MCP is categorized under Art & Culture and uses a remote HTTP/SSE transport. Url belongs to Developer Tools and uses a local stdio subprocess. Pick Travel Art MCP for art & culture 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.
Travel Art MCP is listed as free. Auth: no auth required. 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 alexzavialov-travel-art-mcp and url as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Travel Art MCP has a quality signal of 51/100 (Good) with 3 views, 0 installs and 2 GitHub stars. Url has 49/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.