Travel Art MCP vs Rijksmuseum MCP
A side-by-side look at the Travel Art MCP and Rijksmuseum MCP 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 Rijksmuseum MCP for art & culture 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 Rijksmuseum MCP when
- You need dedicated capabilities in the Art & Culture domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
RIJKSMUSEUM_API_KEY, PORT, LOG_LEVEL.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Art & Culture | Art & Culture |
| Quality signal | 51/100 · Good | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | BYOK (pay the provider) |
| Required env vars | None listed | RIJKSMUSEUM_API_KEYPORTLOG_LEVEL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 72 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Travel Art MCP | View Rijksmuseum MCP |
Tools & capabilities
Travel Art MCP tools
No tool names declared yet. Check the project README from the listing page.
Rijksmuseum 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.
Travel Art MCP
{
"mcpServers": {
"alexzavialov-travel-art-mcp": {
"url": "https://mcp.travel.art/health"
}
}
}
Rijksmuseum MCP
{
"mcpServers": {
"r-huijts-rijksmuseum-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-server-rijksmuseum"
],
"env": {
"RIJKSMUSEUM_API_KEY": "YOUR_RIJKSMUSEUM_API_KEY_HERE",
"PORT": "YOUR_PORT_HERE",
"LOG_LEVEL": "YOUR_LOG_LEVEL_HERE"
}
}
}
}
Frequently asked questions
Travel Art MCP is categorized under Art & Culture and uses a remote HTTP/SSE transport. Rijksmuseum MCP belongs to Art & Culture and uses a local stdio subprocess. Pick Travel Art MCP for art & culture work and Rijksmuseum MCP for art & culture.
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. Rijksmuseum MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. 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 r-huijts-rijksmuseum-mcp 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. Rijksmuseum MCP has 43/100 (Fair) with 1 views, 0 installs and 72 GitHub stars.