# r-huijts/rijksmuseum-mcp [Health: Active]

**Category:** 🎨 Art & Culture  
**Repository:** https://github.com/r-huijts/rijksmuseum-mcp  
**GitHub Stars:** 72  
**npm Downloads (last month):** 79  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/r-huijts-rijksmuseum-mcp

## Description
Rijksmuseum API integration for artwork search, details, and collections

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "rijksmuseum-mcp": {
    "command": "npx",
    "args": ["-y","mcp-server-rijksmuseum"],
    "env": {
      "RIJKSMUSEUM_API_KEY": "",
      "PORT": "",
      "LOG_LEVEL": ""
    }
  }
}
```

**Requires environment variables:** `RIJKSMUSEUM_API_KEY`, `PORT`, `LOG_LEVEL` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What r-huijts/rijksmuseum-mcp does

The r-huijts/rijksmuseum-mcp MCP server exposes Rijksmuseum collection data to an AI client through natural-language requests. It is intended for artwork discovery, object research, collection browsing, and artist-focused analysis rather than general museum or image-search tasks.

Search can use text and filters such as artist, artwork type, materials and techniques, time period, and color. Detailed object lookups return information including titles, artists, dates, physical properties, historical and curatorial context, visual information, and exhibition history. The server also supports user-created sets, high-resolution image data, browser-based image opening, and chronological artist timelines.

## How it works

The server uses the Rijksmuseum API as its collection data source. An MCP-compatible client starts the server and sends tool calls based on the user’s request. The server then translates those requests into collection searches or object-related operations and returns the results to the client.

The available operations include `search_artwork`, `get_artwork_details`, `get_artwork_image`, `get_user_sets`, `get_user_set_details`, `open_image_in_browser`, and `get_artist_timeline`. Image retrieval includes zoom-related data, image tiles, full-resolution support, and position information where provided by the API. Browser opening is separate from image-data retrieval and is intended for viewing an artwork directly.

## Setup and configuration

The documented npm setup is for Claude Desktop. Add an MCP server entry that runs `npx -y mcp-server-rijksmuseum` and provide the API key through the `RIJKSMUSEUM_API_KEY` environment variable. The key is obtained from the Rijksmuseum API Portal.

For a source installation, clone the repository, run `npm install`, copy `.env.example` to `.env`, and add the API key. The compiled server can then be started with Node using the built `index.js` path in the client configuration. The installation path must be replaced with the actual local path, and Claude Desktop must be restarted after configuration changes.

Configuration also lists `PORT`, which defaults to `3000`, and `LOG_LEVEL`, which defaults to `info`. The API key is required; the other two variables adjust server behavior.

## Tools and capabilities

The r-huijts/rijksmuseum-mcp MCP server supports these documented capabilities:

- Search and filter artworks by descriptive and collection criteria.
- Retrieve detailed metadata and curatorial information for an artwork.
- Access high-resolution image information with multiple zoom levels and tiles.
- Browse user-created sets and inspect individual set details.
- Open artwork images in a browser.
- Build chronological timelines of an artist’s works.

These tools can support questions about Rembrandt, Van Gogh, Vermeer, Dutch Golden Age art, thematic subjects, materials, techniques, and collection groupings when the corresponding information is available through the Rijksmuseum API.

## Limitations and notes

The documented client configuration covers Claude Desktop; it does not provide client-specific setup instructions for other MCP applications. Results and available metadata depend on the Rijksmuseum API and its collection records.

The README identifies the project as MIT licensed. API endpoint details are maintained in the Rijksmuseum API documentation linked by the project. Image viewing through `open_image_in_browser` requires a browser environment, while image data retrieval is handled through the MCP tool interface.

_Full upstream README: https://allmcps.com/mcp/r-huijts-rijksmuseum-mcp/readme_