Europeana MCP for AI. Access millions of European cultural records instantly.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
Europeana lets your AI agent search millions of cultural artifacts, artworks, books, and historical records from thousands of European museums and libraries.
Use complex filters to find items matching multiple criteria or gather structured metadata on people and places linked to the archives.
What your AI can do
Get entity
Retrieves background information about people, places, or topics associated with a record.
Oaipmh request
Downloads large sets of raw, structured metadata in XML format for bulk data analysis.
Get record
Fetches all specific technical and descriptive metadata for one cultural heritage object ID.
Search the entire database for cultural objects by combining multiple keywords or applying specific filters.
Retrieve all technical and descriptive metadata associated with a single, known artifact ID.
Discover contextual information about individuals, locations, or topics related to the records you find.
Download large amounts of raw metadata in XML format for systematic analysis.
Ask an AI about this
Waiting for input…
Europeana: 4 Tools for Heritage Data
Use these tools to search, filter, retrieve specific details, or bulk download structured metadata from Europe's cultural archives.
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 Europeana on VinkiusGet Entity
Retrieves background information about people, places, or topics associated with a record.
Oaipmh Request
Downloads large sets of raw, structured metadata in XML format for bulk data...
Get Record
Fetches all specific technical and descriptive metadata for one cultural heritage...
Search Records
Searches the Europeana database using keywords and logical filters to find relevant...
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.
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
Make Your AI Do More
Start with Europeana, 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
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Europeana. 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
Works with 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 4 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Finding art history data involves clicking through endless portals.
Right now, finding a comprehensive view of European cultural assets means juggling dozens of institutional websites. You click into the British Museum's portal for one item, then switch to the Louvre's site for another, copy key details—like dates or associated people—into a spreadsheet, and repeat that process until your day ends.
With this MCP, you simply prompt your agent. It handles the data connection across all those sources automatically. You get structured metadata compiled right in your chat window, saving you the tedious chore of copy-pasting into multiple tabs.
The `get_entity` tool provides context about people and places.
If you find a record that mentions 'Johannes Vermeer' but only gives his name, you currently have to open three different Google searches just to confirm if he was also an engineer or worked in Delft. You spend time verifying roles and associated locations manually.
Using `get_entity` pulls all of that linked information for you. It delivers confirmed professional roles, key dates, and related places immediately. The context is ready.
What your AI can actually do with this
Instead of visiting dozens of individual museum websites and manually cross-referencing dates and names, your agent connects directly to Europeana's massive collection. You can ask it detailed questions—like finding all illuminated manuscripts from 15th-century France linked to a specific noble family. It handles the complex search and data retrieval across thousands of European institutions.
If you need structured data for analysis or large-scale research, this MCP offers professional metadata harvesting capabilities. This makes Europeana available in your workflow through Vinkius, connecting it instantly to any AI client you use.
019e5d17-355c-73b4-bc79-0ed3550e2774 Here's how it actually works
The bottom line is that once you input the key, your AI client handles all the complex steps of querying across the entire European archive for you.
First, subscribe to the Europeana MCP and provide your unique API Key (WSKey).
Next, direct your AI client to run a query—for example, searching for records related to 'Vermeer' and 'Delft'.
Finally, the agent executes the search or request and returns structured metadata directly into your chat or script.
Who is this actually for?
This MCP is essential for academic researchers and digital humanities specialists who spend time sifting through disparate museum databases. If you're tired of spending hours on Google Scholar just to piece together a timeline, this tool saves the day.
Uses it to gather primary source metadata for papers, allowing them to cross-reference dates and locations across multiple European archives in one session.
Employs it to catalog collections, using the tool to pull detailed descriptions and linked entities from historical records before a public exhibit launch.
Connects it to scripts for bulk harvesting via OAI-PMH, turning unstructured cultural data into clean XML files for analysis.
What Changes When You Connect
Don't manually build complex search queries. Use search_records to ask your agent to find items by combining keywords and applying filters, like finding all 'Louvre' artworks from the 17th century.
Avoid incomplete data sets. With get_record, you get deep technical metadata for a specific object ID—not just a title or date.
Skip cross-referencing websites. If you need to know everything about 'Leonardo da Vinci,' use get_entity to pull biographical facts, roles, and related records in one go.
Stop manual data exports. Use oaipmh_request for professional metadata harvesting, grabbing massive amounts of structured XML for your own database.
Speed up research flow. By centralizing access across thousands of European libraries, you cut down days of clicking into minutes.
See it in action
A historian needs to trace a figure's influence
The agent finds the entity for 'Christopher Columbus.' It then uses get_entity to list related records, and subsequently uses search_records to filter those results down to only items published in the Caribbean region.
A student needs a bibliography of all 19th-century French poetry
The agent executes a broad search using search_records, applying boolean filters like 'France' AND 'Poetry' AND (1800-1900). It then provides the list of IDs for the student to review.
A developer needs raw data on all Roman artifacts
The agent triggers oaipmh_request with specific parameters, returning a massive XML file that the developer can ingest directly into their application's database schema.
The honest tradeoffs
Searching for context only
Asking 'Tell me about Rembrandt.' This is too vague and gives generic results, missing professional roles or linked people.
First, run get_entity on the name. This retrieves structured data (biographical dates, professional roles) that you can then use to refine a subsequent search with search_records.
Getting details without knowing IDs
Asking 'What are the details for the Paris artwork?' The system needs more specific identifiers than just a city name.
First, use search_records to get a list of candidate records. Then, select an ID from that list and pass it into get_record.
Missing the big data approach
Only using search tools when you actually need a full archive dump.
If your goal is large-scale analysis, don't rely on searching. Use oaipmh_request to pull everything into XML format.
When It Fits, When It Doesn't
Use this MCP if your project requires accessing structured metadata or historical records from a vast, decentralized source like European museums. It excels when you need to move beyond simple keyword searches and perform targeted lookups (get_record) or entity mapping (get_entity). Don't use it if all you need is a quick definition; then a general knowledge tool works better. If your data needs are purely programmatic—i.e., you need thousands of records for a database migration—skip the search tools and jump straight to oaipmh_request. Always start by checking what kind of information you have: an ID, or just keywords.
Questions you might have
How do I find records about a specific item using the search_records tool? +
You run search_records and provide keywords combined with boolean operators. This allows you to narrow down millions of results efficiently (e.g., 'Paris' AND 'Louvre').
What is the difference between get_record and search_records? +
Use search_records when you only have keywords, as it returns a list of potential items. Use get_record when you already know the exact ID and need all the deep details for that single item.
Can I use oaipmh_request to get data from multiple years? +
Yes, oaipmh_request is designed for bulk harvesting. You configure it with parameters that define a date range or collection scope, allowing you to download thousands of records at once.
How does the get_entity tool help me find related people? +
It doesn't just list names; get_entity pulls structured data about that person—their roles (painter, scientist), their dates, and links to other records associated with them.
What is the process for authenticating or setting up my API key when using get_record? +
You must subscribe to the MCP and provide a valid Europeana API Key (WSKey). This credential authorizes your agent to access the secure metadata endpoints. The system uses this key to validate every request, ensuring you have proper permissions before retrieving detailed records.
Can I use search_records to filter results based on geographical places or organizations? +
Yes, search_records supports advanced boolean operators and filters for these entity types. You can combine location names (e.g., 'Paris') with organizational identifiers in a single query to narrow down your search scope effectively.
What should I know about rate limits when running a large metadata harvest using oaipmh_request? +
The oaipmh_request tool is designed for bulk data, but you must be mindful of API throttling. For massive datasets, submit your requests in batches rather than attempting one single call to avoid hitting rate limits and ensure reliable data retrieval.
When I use get_record, how do I handle records that contain multiple languages or formats? +
The get_record tool retrieves comprehensive metadata structures. You can filter the output parameters to specifically request descriptions in a primary language or access technical data fields like Dublin Core for consistent formatting across different record types.
How can I filter my search to only include images? +
You can use the qf (Query Filter) parameter in the search_records tool. For example, setting qf=TYPE:IMAGE will narrow your results to visual media only.
Can I retrieve information about a specific artist or historical figure? +
Yes! Use the get_entity tool with the type set to 'person' and the corresponding entity ID to fetch detailed information about individuals linked to Europeana records.
What is the OAI-PMH tool used for? +
The oaipmh_request tool is designed for bulk harvesting of metadata. It allows you to list identifiers, sets, and records in XML format, which is ideal for large-scale data integration and archival synchronization.
We've already built the connector for Europeana. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 4 tools are live and waiting.
You're up and running in seconds.
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.
Built, hosted, and secured by Vinkius. You just connect and go.