Europeana MCP. Search millions of European art and history records
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Europeana MCP Server connects your AI agent to millions of cultural heritage items. Use this server to search, retrieve, and analyze metadata from European museums and libraries.
It lets you find records using advanced filters, get deep technical data on specific objects, and even harvest large datasets using OAI-PMH.
It's a single source for digitized European history and art.
What your AI agents can do
Get entity
Retrieves linked information about People, Places, Topics, and Organizations associated with cultural records.
Get record
Gets all technical and descriptive metadata for a single, specific cultural heritage object.
Oaipmh request
Performs bulk metadata harvesting, returning large sets of data in XML format.
Use search_records to find specific cultural items by applying filters and combining keywords using boolean logic.
Call get_record with a collection and record ID to pull all technical and descriptive metadata for one specific cultural object.
Use get_entity to find related information about people, places, topics, or organizations attached to a record.
Execute oaipmh_request for bulk data retrieval, pulling professional metadata in XML format.
Ask AI about this MCP
Supported MCP Clients
Waiting for input…
Europeana MCP Server: 4 Tools for Cultural Data
Use these four tools to search, retrieve, and analyze structured metadata from Europeana's vast collection of European cultural heritage items.
019e5d17get entity
Retrieves linked information about People, Places, Topics, and Organizations associated with cultural records.
019e5d17get record
Gets all technical and descriptive metadata for a single, specific cultural heritage object.
019e5d17oaipmh request
Performs bulk metadata harvesting, returning large sets of data in XML format.
019e5d17search records
Searches across the Europeana database using advanced filters and boolean operators to find relevant records.
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 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ 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
What you can do with this MCP connector
Europeana MCP Server connects your AI agent to millions of cultural heritage items. You can use this server to search, retrieve, and analyze metadata from European museums and libraries. It lets you find records using advanced filters, get deep technical data on specific objects, and even harvest large datasets using OAI-PMH.
It's a single source for digitized European history and art.
Search collections by criteria: You'll use search_records to find specific cultural items by applying filters and combining keywords using boolean logic. Retrieve full object data: Call get_record with a collection and record ID to pull all technical and descriptive metadata for one specific cultural object. Map linked data points: Use get_entity to find related information about people, places, topics, or organizations attached to a record. Harvest large metadata sets: Execute oaipmh_request for bulk data retrieval, pulling professional metadata in XML format.
How Europeana MCP Works
- 1 Subscribe to the Europeana server and input your Europeana API Key (WSKey).
- 2 Your AI client connects to the server and calls the desired tool (e.g.,
search_records). - 3 The tool executes the query against the Europeana database and returns the structured metadata results to your agent.
The bottom line is: you pass the query to your agent, and the agent uses the tools to pull structured data from Europeana.
Who Is Europeana MCP For?
This is for researchers, academics, and data scientists who need structured access to historical and cultural data. If your job involves cross-referencing primary sources, cataloging museum collections, or building applications that need geographical or historical context, this toolset is for you. It cuts out the manual research phase.
Uses search_records to find primary sources and metadata for a thesis, then uses get_entity to build a graph of related historical figures and places.
Uses get_record to pull detailed metadata profiles for newly accessioned items, ensuring all technical details are logged.
Uses oaipmh_request to harvest large batches of metadata, feeding the structured data directly into analysis pipelines.
What Changes When You Connect
- Advanced Filtering: Use
search_recordsto narrow down millions of results. You can filter by location, date, or subject simultaneously, making complex searches actionable. - Deep Object Inspection:
get_recordpulls the full metadata profile. You get deep technical details—not just the title, but the creator, dimensions, and provenance records. - Context Mapping: The
get_entitytool maps relationships. If you find a record about a painting, you can immediately find linked data on the artist, the place it was painted, and the topic. - Scalable Data Pipelines: For large-scale analysis,
oaipmh_requesthandles bulk harvesting. You get clean, professional metadata streams for data science models, bypassing manual API limits. - Efficiency: The combination of tools allows your agent to move from a broad search (
search_records) to deep context (get_entity) to bulk export (oaipmh_request) in a single, coherent workflow.
Real-World Use Cases
Academic research on a specific time period.
A student needs to find all records related to the Dutch Golden Age. They ask their agent to run search_records with filters for 'Netherlands' AND '1600-1700'. The agent returns a list of candidates. The student then uses get_entity on a specific result to map the key people (like Rembrandt) and places associated with those records, building a clear research graph.
Cataloging a museum's new collection.
A curator receives a batch of items with limited documentation. They ask their agent to use get_record on each item's ID. The agent pulls the full, detailed metadata, allowing the curator to cross-reference descriptions and ensure every field is populated before cataloging.
Building a dataset for geographic analysis.
A data scientist wants to correlate art movements with geographical shifts. They use oaipmh_request to harvest metadata for 500 records from a specific region. This bulk data is fed into a local analysis tool, allowing them to run large-scale statistical models.
Investigating a historical figure's influence.
A researcher wants to understand Leonardo da Vinci's influence. They first run search_records for his name. Then, for the top results, they use get_entity to pull all linked professional roles (painter, engineer, scientist) and the people who worked with him, giving a comprehensive view of his network.
The Tradeoffs
Treating Europeana like a simple keyword search
Just asking the agent to 'find art about Paris and the Louvre.' This results in too many general hits and lacks the specific context needed for proper academic work.
→
Run search_records and use specific boolean operators. Force the agent to search for 'Paris' AND 'Louvre' AND 'Painting' AND filters={date:1800-1900}. This narrows the result set to actionable, high-quality items.
Only pulling basic titles and descriptions
Relying on the initial search results to get full details. This leaves out critical technical metadata like the medium, dimensions, or original owner.
→
After finding a promising record ID, always use get_record to pull the full object data. This ensures you get the deep technical metadata required for accurate documentation.
Trying to build a large dataset manually
Copying and pasting metadata from dozens of search results into a spreadsheet. This is slow, error-prone, and hits API usage limits.
→
Use oaipmh_request for bulk harvesting. This tool is designed to pull metadata in professional XML batches, giving you a structured data source for analysis.
When It Fits, When It Doesn't
Use this server if you need structured, deep metadata about European cultural objects. Specifically, if your workflow requires connecting people to places, or if you need to filter records using complex boolean logic, this is the right tool. Don't use it if you just need a general search for 'art'—use search_records with filters. Also, don't use it if you need data from a single, private collection; it's for Europeana's public domain. If you need massive, structured data extraction, oaipmh_request is your dedicated tool; don't try to do that with search_records alone.
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 server provides 4 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Manually researching art and history is a black hole of clicks.
Today, researching a topic means jumping between museum websites, filling out complex forms, and manually comparing dates and names. You spend hours copy-pasting basic titles and digging through unstructured PDFs just to gather the core metadata points.
With this MCP server, your agent handles the complexity. Instead of navigating dozens of separate sites, you just ask it to find records related to 'Vermeer' and 'Delft'. It runs the search, pulls the metadata, and gives you structured data ready for analysis. You get the facts, not the friction.
Europeana MCP Server: Get Deep Records with `get_record`
Without this server, getting the full story on a single object means finding the record ID, then going to a second page to check the technical specs, and a third page just for the provenance. It's a multi-step, brittle process.
Now, you tell your agent the collection ID and the record ID. It executes `get_record` and pulls every piece of data—the languages, the digital object links, the full metadata profile—in one structured response. It's the whole story, instantly.
Common Questions About Europeana MCP
How do I use the `search_records` tool in Europeana? +
You pass the tool the search parameters. You should use boolean operators (AND, OR) and filters to narrow the search, like 'Paris' AND 'Louvre' AND 'Painting'. Don't just list words; structure your search.
Can `get_entity` find information about people? +
Yes. get_entity retrieves structured data on People, Places, Topics, and Organizations. For example, you can link records about a painting to the specific painter or the city where it was created.
Is `oaipmh_request` for searching or downloading? +
It's for bulk downloading. This tool executes OAI-PMH requests, pulling large batches of metadata in XML format for large-scale data processing, not for single searches.
What is the best way to get detailed info for one object? +
Use get_record. This tool requires a collection ID and a record ID. It returns the complete metadata profile for that single cultural object.
When should I use `get_record` versus `search_records`? +
Use search_records when you need to find a group of items. Use get_record when you already have the specific collection or record ID and need the full details for that single object.
How do I handle large-scale data pulls using `oaipmh_request`? +
You manage large pulls by structuring the OAI-PMH request. This tool returns XML data, which is perfect for bulk harvesting and feeding structured data into other systems.
Does `get_entity` support filtering by type (e.g., only places)? +
Yes, you specify the entity type in the request. You can narrow your search to focus on People, Places, Topics, or Organizations, giving you targeted results.
What authentication is required for `search_records`? +
The server requires a Europeana API Key (WSKey). You must provide this key when setting up the connection to authorize your AI client.
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.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Arcsecond.io
Access astronomical data and manage observatories with Arcsecond.io — search objects and track night logs via AI.
Deterministic Text Summarizer & Extractor
Equip your AI with pure Term Frequency (TF) text analysis. Deterministically extract keywords, bigrams, and generate extractive summaries without external API calls.
Maranhão Open Data
Access public datasets from Maranhão, Brazil — search packages, inspect resources, and query the datastore via SQL.
You might also like
Perfecto
Verify software testing ecosystems via Perfecto — search cloud devices, isolate execution artifacts, and execute real-time automated reports seamlessly.
Evil Insult
Generate creative and random insults from the Evil Insult Generator API directly within your AI agent.
Mem AI (Knowledge Workspace)
Manage your knowledge base via Mem.ai — create notes, run AI semantic search, and organize collections.