How to Use the Europeana MCP in LlamaIndex

Index millions of cultural heritage records into your LlamaIndex RAG pipelines for grounded historical queries.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Europeana MCP to LlamaIndex

Create your Vinkius account to connect Europeana to LlamaIndex and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Europeana with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Index Europeana MCP Server Output

The `search_records` tool feeds raw metadata from museums and libraries straight into your LlamaIndex vector store. Your application doesn't just read the data once; it embeds the historical context for future semantic searches. When a user asks about Renaissance paintings, the engine queries your local index first. If the index lacks depth, the agent reaches out to fetch fresh data, keeping your knowledge base grounded in actual archival facts.

Embed Full Object Details

Calling `get_record` returns the exhaustive details of a specific cultural artifact. LlamaIndex takes this structured JSON and converts it into indexable documents. This means your RAG application can answer highly specific questions about an item's provenance or dimensions. You stop relying on the LLM's baseline training and start citing verifiable museum data.

Resolve and Store Linked Entities

The `get_entity` tool pulls biographical and geographical linked data associated with an artwork. Your agent embeds this context alongside the primary artifact record. Bulk ingestion is also an option using `oaipmh_request` for raw XML harvesting. You can write a custom ingestion pipeline that parses these batches and updates your LlamaIndex storage overnight.

Setup guide

Set up Europeana MCP in LlamaIndex

Prerequisites

Python 3.10+ installed
llama-index-tools-mcp package
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.
2

Connect with BasicMCPClient
Point BasicMCPClient to your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. Supports SSE and Streamable HTTP transports.
3

Convert to LlamaIndex tools
Call mcp_tool_spec.to_tool_list_async() to convert all Europeana MCP tools into native FunctionTool objects that any LlamaIndex agent can use.
4

Run with any LLM
Create a FunctionAgent with the tools and your preferred LLM. Swap OpenAI for Anthropic, Gemini, or any LlamaIndex-supported provider.

agent.py

from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

# Connect to the MCP
mcp_client = BasicMCPClient(
    "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
mcp_tool_spec = McpToolSpec(client=mcp_client)

# Convert MCP tools to LlamaIndex tools
tools = await mcp_tool_spec.to_tool_list_async()

# Create and run the agent
agent = FunctionAgent(
    tools=tools,
    llm=OpenAI(model="gpt-4o"),
    system_prompt="You have access to Europeana tools.",
)
response = await agent.run("List recent Europeana data")

Get your connection token →

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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Europeana now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Europeana MCP in LlamaIndex

Install llama-index-tools-mcp and instantiate a BasicMCPClient. Wrap it with McpToolSpec, call the async method to get the tool list, and pass them to your FunctionAgent.

Yes. By indexing the tool outputs, you effectively build a local vector cache. Subsequent queries hit your embedded storage instead of triggering new network requests.

The bulk harvesting tool returns raw XML. You will need a custom parser in your ingestion pipeline to convert those payloads into LlamaIndex Document objects before embedding.

Only if you configure your FunctionAgent to use the search tool as a fallback when the local index lacks relevant context. Otherwise, it just relies on what you already ingested.

This server processes historical metadata, artwork descriptions, and your search strings. Vinkius routes these requests through a zero-trust, ephemeral environment that destroys all memory of the transaction as soon as the response delivers.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript