Rijksmuseum MCP Server

What is Rijksmuseum MCP Server?

A Model Context Protocol server that provides access to the Rijksmuseum’s collection through natural language interactions, enabling AI models to explore, analyze, and interact with artworks from the museum.

How to use Rijksmuseum MCP Server?

Install via npm (npx -y mcp-server-rijksmuseum) or from source. Add your Rijksmuseum API key as the environment variable RIJKSMUSEUM_API_KEY. Configure in Claude Desktop’s claude_desktop_config.json under mcpServers. Optional settings: PORT (default 3000) and LOG_LEVEL (default ‘info’).

Key features of Rijksmuseum MCP Server

• Search artworks by artist, type, material, period, color, and more.
• Retrieve comprehensive details about specific artworks.
• Access high-resolution images with deep zoom capabilities.
• Browse and examine user‑curated collections.
• Open artwork images directly in a browser.
• Generate chronological timelines of artists’ works.

Use cases of Rijksmuseum MCP Server

• Discover artworks by artist, time period, or visual characteristics.
• Analyze an artwork’s history, material, and curatorial context.
• Research an artist’s career progression and style evolution.
• Explore thematic groupings like biblical scenes or still lifes.
• Examine high‑resolution details of brushwork, jewelry, or facial expressions.

FAQ from Rijksmuseum MCP Server

What does the server require to run?

Node.js and npm are required. The server needs a Rijksmuseum API key set in the RIJKSMUSEUM_API_KEY environment variable.

How do I get an API key?

You can obtain an API key from the Rijksmuseum API Portal.

Where does the artwork data come from?

All data is fetched from the Rijksmuseum’s official API.

Can I use this server with other MCP clients besides Claude Desktop?

The README provides configurations for Claude Desktop, but the server follows the Model Context Protocol and can be used with any compatible MCP client.

What configuration options are available?

The server accepts RIJKSMUSEUM_API_KEY (required), PORT (default 3000), and LOG_LEVEL (default ‘info’).