Rijksmuseum vs Url
A side-by-side look at the Rijksmuseum 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 Rijksmuseum for art & culture 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 Rijksmuseum when
- You need dedicated capabilities in the Art & Culture domain.
- You prefer a local stdio subprocess transport.
- You want tools like
rijks_search, rijks_object, rijks_object_image.
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 | 53/100 · Good | 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 | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 3 | 3 |
| Full listing | View Rijksmuseum | View Url |
Tools & capabilities
Rijksmuseum tools 3
rijks_searchSearch the Rijksmuseum's ~800,000-object collection — Dutch Golden Age paintings, prints, drawings, photographs, Delftware, Asian art — by title, maker, object type, material, technique or object number, and get back real records: title, maker, date, materials, curatorial description, rights and a IIIF image URL. AUTHORITATIVE for what the Dutch national museum holds and how it catalogues it. Keyless. There is no free-text `q`: filters are field-scoped, and titles are catalogued in Dutch. Example: rijks_search({ creator: "Rembrandt", type: "painting", limit: 5 }).rijks_objectOne Rijksmuseum object in full: title, maker, date, object type, materials, place, depicted subjects, the museum's own curatorial description, object number, rights statement and image URL. Accepts the numeric object id, its id.rijksmuseum.nl URI, or a museum object number such as "SK-C-5" (resolved for you). Keyless. Example: rijks_object({ id: "200107928" }) → The Night Watch.rijks_object_imageImage URLs for one Rijksmuseum object: the IIIF Image API 3 service, full-resolution pixel dimensions, a full-size JPEG, a scaled JPEG at a width you choose, a thumbnail, and the object's rights statement (most of the collection is public domain). Says plainly when an object has no published image rather than returning a broken link. Keyless. Example: rijks_object_image({ id: "200107928", width: 1200 }).
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.
Rijksmuseum
{
"mcpServers": {
"rijksmuseum": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-rijksmuseum"
]
}
}
}
Url
{
"mcpServers": {
"url": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-url"
]
}
}
}
Frequently asked questions
Rijksmuseum is categorized under Art & Culture and uses a local stdio subprocess. Url belongs to Developer Tools and uses a local stdio subprocess. Pick Rijksmuseum 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.
Rijksmuseum 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 rijksmuseum and url as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Rijksmuseum has a quality signal of 53/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Url has 49/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.