Labsco
MCP SERVER

Rijksmuseum MCP Server

by r-huijts

Search the Rijksmuseum collection down to material, technique, century and colour, and get one artist's works back in date order as a timeline.

Encyclopedic & Cultural ReferenceVerified
Summary
"How did this artist's work change" becomes one call instead of a reading list.

get_artist_timeline returns an artist's works in date order with a maxWorks bound, which is where art-historical questions usually start, and search_artwork's filters reach material, technique and colour — so "oil on panel, seventeenth century, with red in it" is a query rather than a browse. One tool behaves differently from the rest: open_image_in_browser opens a window on the machine running the server, not in the session.

What it is

Seven tools over the Rijksmuseum collection: filtered search, full object detail, deep-zoom image tiles, the user-curated sets in Rijksstudio, and a generated chronological timeline for a single artist.

What you get
  • Collection search filtered by maker, type, material, technique, century, colour and culture, with sorting, paging and an image-only or top-pieces restriction
  • Full detail for one object number: title, artist, dates, dimensions, materials, techniques and history
  • Image tile data for deep zoom, so an artwork can be examined at several levels of magnification
  • A chronological timeline of one artist's works in the collection, bounded by maxWorks
  • The sets Rijksstudio users have curated, and the full contents and metadata of any one of them
  • A high-resolution image opened in the default browser on the machine running the server
Requirements

A Rijksmuseum API key in RIJKSMUSEUM_API_KEY, and Node on your PATH.

Setup effort

One command plus a key — npx -y mcp-server-rijksmuseum, then supply credentials