Do I need an API key?

No! The Met Museum API is completely free and open. No authentication required. 80 requests/second rate limit.

Can I use the artwork images commercially?

Yes! Open Access images are licensed under CC0 (Public Domain). You can use them for any purpose without restriction.

How many artworks are in the collection?

The Met collection includes 470,000+ artworks spanning 5,000 years of art history from every part of the globe.

What departments are available?

The Met has 20+ departments including: European Paintings, Egyptian Art, Asian Art, Arms and Armor, Greek and Roman Art, Islamic Art, Modern and Contemporary Art, and many more. Use get_departments to see the full list.

The Met Museum MCP Server for CrewAI 8 tools — connect in under 2 minutes

Name: The Met Museum
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 8 Tools Framework

Connect your CrewAI agents to The Met Museum through Vinkius, pass the Edge URL in the `mcps` parameter and every The Met Museum tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="The Met Museum Specialist",
    goal="Help users interact with The Met Museum effectively",
    backstory=(
        "You are an expert at leveraging The Met Museum tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in The Met Museum "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 8 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About The Met Museum MCP Server

Connect to The Met Museum and explore one of the world's largest art collections through natural conversation — no API key needed.

When paired with CrewAI, The Met Museum becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call The Met Museum tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Artwork Search — Search 470,000+ artworks by artist name, title, culture, medium or any term
Artwork Details — Get full metadata including title, artist, date, medium, dimensions, credit line and images
Department Browse — Explore artworks by department (European Paintings, Egyptian Art, Asian Art, etc.)
Highlights — Discover curator-selected highlights from the collection
On-View Objects — Find artworks currently displayed in the museum galleries
Date Range Search — Filter artworks by century or specific date ranges
Image Discovery — Find artworks with Open Access CC0 images

The The Met Museum MCP Server exposes 8 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect The Met Museum to CrewAI via MCP

Follow these steps to integrate the The Met Museum MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 8 tools from The Met Museum

Why Use CrewAI with the The Met Museum MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with The Met Museum through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

The Met Museum + CrewAI Use Cases

Practical scenarios where CrewAI combined with the The Met Museum MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries The Met Museum for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries The Met Museum, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain The Met Museum tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries The Met Museum against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

The Met Museum MCP Tools for CrewAI (8)

These 8 tools become available when you connect The Met Museum to CrewAI via MCP:

get_departments

Useful for filtering searches by department (e.g. European Paintings, Egyptian Art, Asian Art, Arms and Armor). Get all museum departments

get_object

Returns title, artist, culture, date, medium, dimensions, credit line, repository URL, image URLs and more. All Open Access images are CC0 public domain. Get detailed info for a specific artwork by object ID

get_objects_by_department

Use get_departments first to find the department ID. Returns list of object IDs which can be used with get_object for full details. Get all object IDs for a specific department

search_by_century

Returns object IDs which can be used with get_object for full artwork details including images. Search for objects created in a specific century

search_highlights

These represent some of the most significant and popular works in the collection. Search for highlighted (curator-selected) objects

search_objects

Supports filtering by department, date range, medium, images, highlights and on-view status. Returns object IDs which can be used with get_object for full details. Search The Met collection for artworks

search_on_view

Useful for planning museum visits. Search for objects currently on view in the museum

search_with_images

Useful for finding visual artworks. Supports all standard search filters plus has_images=true. Search for objects that have images

Example Prompts for The Met Museum in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with The Met Museum immediately.

"Search for paintings by Monet."

"Show me the highlights from Egyptian Art."

"Find sculptures from the 1800s."

Troubleshooting The Met Museum MCP Server with CrewAI

Common issues when connecting The Met Museum to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

The Met Museum + CrewAI FAQ

Common questions about integrating The Met Museum MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.