Rijksmuseum vs Filesystem
A side-by-side look at the Rijksmuseum and Filesystem 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 Filesystem for file systems 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 Filesystem when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
path, head, tail.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Art & Culture | File Systems |
| Quality signal | 53/100 · Good | 85/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 91,512 |
| Directory activity | 1 views 0 installs 0 upvotes | 9 views 0 installs 0 upvotes |
| Tools | 3 | 17 |
| Full listing | View Rijksmuseum | View Filesystem |
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 }).
Filesystem tools 17
pathheadtailpathscontenteditsoldTextnewTextdryRunsortBysourcedestination- +5 more on 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.
Rijksmuseum
{
"mcpServers": {
"rijksmuseum": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-rijksmuseum"
]
}
}
}
Filesystem
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem"
]
}
}
}
Frequently asked questions
Rijksmuseum is categorized under Art & Culture and uses a local stdio subprocess. Filesystem belongs to File Systems and uses a local stdio subprocess. Pick Rijksmuseum for art & culture work and Filesystem for file systems.
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. Filesystem is listed as free. Auth: no auth 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 rijksmuseum and filesystem 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. Filesystem has 85/100 (Excellent) with 9 views, 0 installs and 91,512 GitHub stars.