Vinkius
Rijksmuseum

Rijksmuseum MCP for AI. Query Dutch Art Metadata and Academic Records

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Rijksmuseum MCP on Cursor AI Code EditorRijksmuseum MCP on Claude Desktop AppRijksmuseum MCP on OpenAI Agents SDKRijksmuseum MCP on Visual Studio CodeRijksmuseum MCP on GitHub Copilot AI AgentRijksmuseum MCP on Google Gemini AIRijksmuseum MCP on Lovable AI DevelopmentRijksmuseum MCP on Mistral AI AgentsRijksmuseum MCP on Amazon AWS Bedrock

How this MCP server connects to your AI agent

Rijksmuseum MCP Server provides direct access to Dutch art history data. Use this server to search Rembrandt's works, retrieve high-resolution image metadata via IIIF, and query deep bibliographic records from the museum's research library.

It handles complex standards like OAI-PMH and Linked Data Event Streams (LDES), letting your AI client pull structured information across multiple formats.

What AI agents can do with Rijksmuseum Automation

Get iiif image info

Gets the technical metadata for an IIIF image, detailing its resolution and format capabilities.

Get iiif manifest

Retrieves the full IIIF presentation manifest which defines how to display a specific high-resolution object online.

Get ldes collection

Fetches metadata streams for an entire Linked Data Event Stream (LDES) collection.

+ 5 more capabilities included
Search Artworks by Criteria

You can use search_collection to filter the museum's vast holdings based on parameters like creator, material, or time period.

Retrieve IIIF Image Details

The get_iiif_image_info tool fetches technical metadata for an artwork image, including its maximum resolution and available formats.

Fetch Presentation Manifests

Use get_iiif_manifest to get the full IIIF presentation manifest for an object, detailing how the high-resolution asset can be viewed.

Query Academic Library Records

search_library runs contextual queries against bibliographic records from the Research Library using CQL syntax.

Harvest Metadata via OAI-PMH

The oai_pmh_request tool allows you to pull metadata in bulk by requesting data through the Open Archives Initiative Protocol (OAI-PMH).

Resolve Object Identifiers

You can run resolve_pid to dereference a Persistent Identifier, guaranteeing you have the most current object metadata.

Included with Plan

Waiting for input…

AI Agent

What AI agents can do with Rijksmuseum MCP Server: 8 Tools for Cultural Heritage Data

These eight tools allow your agent to perform specialized functions—from searching artworks by criteria to harvesting metadata via industry standards like IIIF and OAI-PMH.

Make your AI actually useful.

Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.

Start using Rijksmuseum on Vinkius

Get Iiif Image Info

Gets the technical metadata for an IIIF image, detailing its resolution and format capabilities.

Get Iiif Manifest

Retrieves the full IIIF presentation manifest which defines how to display a...

Get Ldes Collection

Fetches metadata streams for an entire Linked Data Event Stream (LDES) collection.

Get Ldes Dataset

Retrieves specific data records from a defined LDES dataset using its identifier.

Oai Pmh Request

Harvests metadata in bulk by making requests to the Open Archives Initiative...

Resolve Pid

Takes a Persistent Identifier and resolves it to ensure you have the current, accurate object record.

Search Collection

Searches for objects within the museum's collection using various filters like creator or material type.

Search Library

Queries bibliographic records from the Research Library using Contextual Query...

Security and governance baked right in.

Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.

Claude AI

Claude AI

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

3

Start a conversation

Open a new chat. The Rijksmuseum integration is available immediately — no restart needed.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

  • Import from OpenAPI, Swagger, or YAML specs
  • Create Agent Skills with progressive disclosure
  • Deploy to edge with MCPFusion framework
  • Built in DLP, auth, and compliance on every call
  • Real time usage dashboard and cost metering
  • Publish to catalog or keep private
Start building

Make Your AI Do More

Start with Rijksmuseum, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.

  • Use this MCP plus 5,100+ others, all in one place
  • Add new capabilities to your AI anytime you want
  • Every connection is secured and compliant automatically
  • Track usage and costs across all your servers
  • Works with Claude, ChatGPT, Cursor, and more
  • New servers added to the catalog every week
Rijksmuseum MCP server cover

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Rijksmuseum. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

Your data is protected. See how we built it.

Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This connection provides 8 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.

Getting comprehensive art data used to be a mess of different APIs., Solved with Vinkius AI Gateway

Today, getting all the facts about a painting involves jumping between at least three different systems. You call one API for basic search results, another specialized endpoint for IIIF image files, and a third system using MARC or Dublin Core standards just to find the academic history. It's copy-paste hell.

With this MCP server, your agent handles the handoffs. You ask it for details on an object—say, 'Rembrandt's self-portrait.' The agent runs `search_collection` for the ID, then automatically uses that ID to call `get_iiif_manifest` and `search_library`, handing you one unified response.

Rijksmuseum MCP Server: Structured data retrieval with Linked Data.

Previously, pulling related metadata—like all the associated technical reports or object variants—required manually executing protocols like OAI-PMH and then writing custom parsers for LDES streams. It was a bespoke development project just to get clean JSON.

Now, your agent handles those standards automatically. You ask it to pull linked data, and using `get_ldes_dataset` or `get_ldes_collection`, you get the structured results without writing a single line of protocol handling code.

What your AI can actually do with this

Rijksmuseum MCP Server provides straight access to Dutch art data and deep historical records. You're connecting your AI client directly to the museum's core collection, research library, and high-resolution image metadata. This isn't surface-level searching; it handles complex standards like OAI-PMH and Linked Data Event Streams (LDES), letting your agent pull structured information across multiple formats.

Searching for Artworks by Criteria

The search_collection tool lets you filter the museum's massive holdings. You input parameters—like creator, material type, or a specific time period—and it returns objects matching those criteria. For instance, if you need all of Rembrandt’s works painted in oil between 1630 and 1645, you run search_collection with those filters.

If you're unsure about an object ID or a name, use the resolve_pid tool. It takes a Persistent Identifier (PID) and resolves it instantly, guaranteeing your agent gets the most current and accurate metadata record for that artwork.

To query academic records specifically, run search_library. This tool works against the Research Library's bibliographic data using Contextual Query Language (CQL) syntax. You can ask detailed questions—like 'Show me all sources mentioning Vermeer and light refraction'—and it pulls those structured library results for you.

Handling High-Resolution Image Details

The get_iiif_image_info tool fetches the technical metadata for any IIIF image. When you run this, you get details on its resolution and what formats are available. You'll know if it supports 4K or if it's restricted to JPG/PNG. It tells you exactly what kind of asset you're working with.

To see how that high-resolution object can be viewed online, use get_iiif_manifest. This tool retrieves the full IIIF presentation manifest for an object. That manifest isn't just a link; it defines every step needed to display the high-res asset correctly in a viewer.

Bulk and Structured Data Harvesting

For pulling massive amounts of metadata, you use oai_pmh_request. This tool harvests data in bulk by making requests through the Open Archives Initiative Protocol (OAI-PMH). You specify what collection or date range you want, and it pulls hundreds of records at once.

When dealing with evolving datasets, Linked Data Event Streams (LDES) are key. Start by running get_ldes_collection to fetch metadata streams for an entire LDES collection. This gives you the roadmap for the data. Then, use get_ldes_dataset. You feed it a specific dataset identifier, and it pulls those defined records directly.

It’s how your agent digs into complex, structured streams of information.

You don't need to write any boilerplate code or worry about API keys; you just tell your AI client what data you need—a Rembrandt search, the IIIF manifest for a specific object, or bulk metadata via OAI-PMH—and it handles routing the query through the appropriate tool. It’s straight access to museum history.

Built · Hosted · Managed by Vinkius Rijksmuseum MCP Server - Art Data & Metadata
Server ID 019e5d50-eefa-73df-943c-8e15ba8e13ca
Vinkius Inspector
Compliance Grade F
Score 3.6/100
Vinkius Inspector Badge — Score 3.6/100

Questions you might have

How do I search for an object by creator? +

You use the search_collection tool. You pass the artist's name (e.g., 'Rembrandt') into the appropriate filter parameters to narrow down the results.

Do I need a PID before using get_iiif_manifest? +

It's best practice to use resolve_pid first. This confirms the ID is current and valid, which prevents the manifest request from failing due to an outdated identifier.

What is the difference between oai_pmh_request and get_ldes_dataset? +

OAI-PMH handles bulk metadata harvesting using a standard protocol. LDES tools are for pulling structured, event-driven streams of related data points.

Can I search academic papers with search_collection? +

No. Use search_collection only for physical works in the museum's inventory. For bibliographic records or research documents, you must use the search_library tool.

What happens if I use `resolve_pid` with an identifier that doesn't exist? +

The tool returns a specific error code indicating no match was found. You must check your source data for typos or outdated identifiers before retrying the call.

Are there rate limits when running bulk queries using `search_collection`? +

Yes, the server enforces a limit of 100 requests per minute. If you exceed this cap, your agent receives an HTTP 429 error and must wait before retrying.

How do I authenticate my AI client when calling tools like `get_iiif_manifest`? +

You need to pass your unique Rijksmuseum API Key in the request headers. Authentication is required for all calls and tracks usage against your subscription limits.

What format does the output from `get_iiif_manifest` come in? +

The manifest arrives as standard JSON, which you'll need to parse with your client language. It contains structured links for image tiles and object metadata.

How can I find all paintings by a specific artist like Rembrandt? +

You can use the search_collection tool and provide the artist's name in the creator field. You can also refine the search by setting the type to 'painting'.

Can I search for books and research papers related to an artwork? +

Yes! Use the search_library tool to query the Rijksmuseum Research Library. You can search by subject, author, or title using CQL queries.

How do I access high-resolution image data for a masterpiece? +

Use the get_iiif_manifest tool with the object's identifier. This provides a standardized manifest containing image sequences and metadata for high-resolution viewing.

Built & Managed by Vinkius 30s setup 8 tools

We've already built the connector for Rijksmuseum. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 8 tools are live and waiting. You're up and running in seconds.

Vinkius runs on Claude Claude
Vinkius runs on ChatGPT ChatGPT
Vinkius runs on Cursor Cursor
Vinkius runs on Gemini Gemini
Vinkius runs on Windsurf Windsurf
Vinkius runs on VS Code VS Code
Vinkius runs on JetBrains JetBrains
Vinkius runs on Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.