Cuddlynest MCP vs Viator MCP
A side-by-side look at the Cuddlynest MCP and Viator MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Cuddlynest MCP for travel & transportation work as a local process; choose Viator MCP for travel & transportation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Cuddlynest MCP when
- You need dedicated capabilities in the Travel & Transportation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
cuddlynest_search, cuddlynest_listing_details.
Choose Viator MCP when
- You need dedicated capabilities in the Travel & Transportation domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
VIATOR_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Travel & Transportation | Travel & Transportation |
| Quality signal | 55/100 · Good | 45/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 | VIATOR_API_KEY |
Tools & capabilities
Cuddlynest MCP tools 2
cuddlynest_searchSearch a destination and the top hotels there, from public CuddlyNest APIscuddlynest_listing_detailsStatic basics **and** rooms/pricing for one hotel.
Viator 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.
Cuddlynest MCP
{
"mcpServers": {
"cuddlynest-mcp": {
"command": "npx",
"args": [
"-y",
"cuddlynest-mcp"
]
}
}
}
Viator MCP
{
"mcpServers": {
"viator-mcp": {
"command": "npx",
"args": [
"-y",
"@chrischall/viator-mcp"
],
"env": {
"VIATOR_API_KEY": "YOUR_VIATOR_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Cuddlynest MCP is categorized under Travel & Transportation and uses a local stdio subprocess. Viator MCP belongs to Travel & Transportation and uses a local stdio subprocess. Pick Cuddlynest MCP for travel & transportation work and Viator MCP for travel & transportation.
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.
Cuddlynest MCP has no declared pricing — check the project's own site. Viator 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 cuddlynest-mcp and viator-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cuddlynest MCP has a quality signal of 55/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Viator MCP has 45/100 (Fair) with 0 views, 0 installs and 1 GitHub stars.