The Met Museum MCP for AI. Deeply Filter Artworks by Department and Century
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Connect to your AI in seconds.
The Met Museum MCP Server connects your AI client directly to over 470,000 artworks in one of the world's largest collections.
You search by artist, filter by department, or narrow down pieces from specific centuries. It retrieves full metadata—including dimensions, materials, and open-access images—allowing deep historical and scholarly analysis without needing an API key.
What your AI can do
Get departments
Gets a list of all major museum departments, like Asian Art or Egyptian Art.
Get object
Gathers full metadata—title, artist, date, medium, dimensions—for one specific artwork ID.
Get objects by department
Returns a list of object IDs that belong to a single department.
Lists all major departments, allowing you to scope your search instantly.
Fetches complete metadata for a single artwork using its unique object ID. Includes images and dimensions.
Finds all available object IDs belonging to one specific department.
Filters the collection to find artworks created within a defined century (e.g., 1700-1799).
Retrieves a list of curator-selected 'highlight' objects from the entire collection.
Searches the full Met collection using multiple filters like department, date range, and medium type.
Locates objects that are currently displayed in the museum's physical galleries.
Ask an AI about this
Waiting for input…
The Met Museum MCP Server: 8 Collection Search Tools
These eight specialized tools let your agent filter vast art collections by departments, centuries, and specific object criteria.
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 The Met Museum on VinkiusGet Departments
Gets a list of all major museum departments, like Asian Art or Egyptian Art.
Get Object
Gathers full metadata—title, artist, date, medium, dimensions—for one specific...
Get Objects By Department
Returns a list of object IDs that belong to a single department.
Search By Century
Finds all artwork IDs created within a specific century range (e.g., 1500-1599).
Search Highlights
Retrieves object IDs for works selected by curators as significant pieces.
Search Objects
Runs a general search across the collection, allowing filtering by department, date range, or medium.
Search On View
Finds object IDs for artworks that are currently displayed in the museum's galleries.
Search With Images
Searches for objects, ensuring they have available high-resolution images attached...
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
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
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.
Start a conversation
Open a new chat. The The Met Museum 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
Make Your AI Do More
Start with The Met Museum, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ 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 The Met Museum. 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 8 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Sifting through art history shouldn't feel like navigating an old catalog index.
Today, researching a specific cultural movement means jumping between departmental pages. You search for 'Egyptian Art,' get a list of IDs; then you jump to the date filter and manually check if those objects fall within your required 3000-year range. It's copy/pasting IDs back and forth until you find what you need.
With this MCP server, you simply tell your agent: 'Show me all Egyptian Art pieces from the New Kingdom period.' The system handles the department lookup (`get_departments`), the scope restriction (`get_objects_by_department`), AND the time filtering—all in one query. You get a clean list of IDs and full metadata.
The Met Museum MCP Server: Accessing deep object data with `get_object`
When you find a promising ID from any search—say, an artifact from the Asian Art department—you usually have to click through three or four separate pages just to verify if it has dimensions listed. This is slow and manual.
Now, when your agent uses `get_object` on that single ID, all the data lands in one structured block: title, artist, date, medium, *and* dimensions. It’s instant verification, every time.
What your AI can actually do with this
The Met Museum MCP Server connects your AI client directly to over 470,000 artworks in one of the world's deepest collections. You don't need an API key or fancy database setup; you just talk to it like you're talking to a curator. Your agent handles the heavy lifting.
General Search and Filtering
The search_objects tool runs across the entire Met collection, letting you narrow down millions of records using multiple filters at once. You can specify a department, define a date range, or filter by material type to quickly pinpoint what you need. If you know you need high-resolution images for your project, use the search_with_images tool; it guarantees that every object ID returned has available digital files attached.
For broader scoping, start with get_departments, which gives you a full list of major museum sections—like Asian Art or Egyptian Art—so you can scope your search instantly.
Targeted Collection Scopes
You're not always looking at the whole lot. If you want to focus only on objects from one specific area, get_objects_by_department returns a comprehensive list of object IDs belonging solely to that department. Need to check out pieces created during a certain period? The search_by_century tool lets you find all artwork IDs within a defined century range—say, 1700 through 1799—cutting down decades of research in seconds.
For the ultimate quick look at what's currently on display, use search_on_view, which locates object IDs for pieces actually hanging in the museum's physical galleries right now.
Deep Dive and Curation Tools
Sometimes you don't need a search; you need specifics. The get_object tool pulls all metadata—the title, artist, date, medium, dimensions, and images—for one unique artwork ID. It gives you the full scholarly package on any single piece. When you’re trying to nail down significance, use search_highlights. This retrieves object IDs for works that curators have specifically marked as important or noteworthy pieces across the whole collection.
Putting it Together: A Workflow Example
You can combine these functions easily. You might want to find all objects in Egyptian Art (get_objects_by_department), then filter those results down only to pieces created between 2500 BCE and 2400 BCE (search_by_century). Then, if you need the full details on the top five of those matches, you pass those IDs to get_object.
It's a layered process that gives deep historical insight without writing a single SQL query. The system handles all the connections.
The Met Museum MCP Server makes scholarly analysis simple. You talk naturally; your agent does the complex database work. Don't get bogged down in API calls or manual data fetching. Just tell it what you want, and it delivers the full metadata package for those 470,000 pieces.
019d8458-b66e-720b-8d9e-b5745c9e91ac 
Here's how it actually works
The bottom line is that you talk to your agent using plain English, and the server handles all the complex filtering against 470k records for you.
Subscribe to this server on Vinkius. You won’t need an API key—all data is open access.
Your AI client (Claude, Cursor, etc.) runs the query against the available tools based on your natural language request.
The system returns a list of object IDs and their associated metadata, which you can then use to pull full details or perform follow-up searches.
Who is this actually for?
This tool is built for deep research. It’s essential for art historians who need reliable metadata, academic researchers tracking cultural provenance across centuries, and educators building detailed lesson plans that require verifiable object data.
Needs to cross-reference pieces by department (e.g., comparing European Paintings from the 17th century) and gather specific metadata like dimensions and medium.
Uses the search tools to build structured lesson plans, pulling object IDs and images for teaching materials across different eras or cultures.
Analyzes art collections or cultural heritage data by filtering on specific date ranges (like 1800-1900) to track trends in global art movements.
What Changes When You Connect
Analyze Provenance: Use search_by_century to filter thousands of artworks created in specific decades. This lets you track how artistic styles changed over time, making trend analysis easy.
Pinpoint Specific Objects: Once your search gives you a list of IDs, use get_object on the individual ID to get every detail: dimensions, medium, and credit line. No guessing required.
Scope Your Search Effort: Instead of searching 470k items generally, run get_departments first. Then, pipe that department into get_objects_by_department to narrow the focus immediately.
Plan a Visit: Use search_on_view if you need to know what's physically in the museum right now. This tool tells you what pieces are currently on display, so you don’t waste time searching for something that moved.
Focus on Visual Results: If your goal is visual output (e.g., a presentation slide), use search_with_images. It guarantees every returned object has an image attached, saving you from dead ends.
See it in action
Tracking Renaissance Painting Trends
A researcher needs to compare early Italian and French paintings. Instead of general search, they use get_departments to find both 'Italian Paintings' and 'French Paintings', then run search_objects on the resulting IDs. This immediately scopes the comparison to only relevant works.
Curating a Time-Sensitive Exhibit
An educator is building a lesson on American art from the 19th century. They use search_by_century to target objects between 1800 and 1899, then run get_objects_by_department (if they know the department) to limit results to 'American Art' only.
Checking for Digital Assets
A digital archivist needs a massive list of open-access images. They use search_with_images to filter the entire collection, ensuring every object they get back has a usable CC0 image file available for public domain use.
Researching Current Museum Layouts
A museum consultant needs to know which artifacts are physically on display this month. They run search_on_view. This gives them immediate insight into the current physical inventory, separate from the entire digital archive.
The honest tradeoffs
Trying to search everything at once
Asking the agent: 'Give me all paintings from European Art that are open access and were made in the 1800s.' This is too complex for one call.
Break it down. First, use get_departments to get the ID for 'European Paintings'. Then, run search_objects using that department ID AND specifying the date range/century. Finally, you can filter the result list by image status.
Missing the Department Scope
Running a general search with only '19th Century' as the filter results in hundreds of objects across every culture and department.
Always start by scoping. Use get_departments to find the ID, then use that specific ID with search_objects. This keeps your result set relevant.
Assuming a single tool handles all filtering
Thinking search_objects can filter by both department and century without knowing the IDs. It often fails to combine these filters correctly.
Use a two-step process: 1) Get Department ID via get_departments. 2) Use that ID in conjunction with your date range search using search_objects.
When It Fits, When It Doesn't
Use this server if your research requires deep metadata querying, specific cross-filtering of art departments and time periods, or needs access to CC0 images. It's for scholars and developers building complex data pipelines.
Don't use it if you just need a quick visual browse; the general search is powerful but verbose. If you only care about what’s currently displayed, search_on_view is faster than running a full historical query.
If your goal is to discover what departments exist before searching anything else, start with get_departments. Never assume object data—always confirm the necessary IDs first.
Questions you might have
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.
When I use the get_object tool, what specific metadata fields do I receive? +
It returns comprehensive details including title, artist, culture, date, medium, dimensions, and credit line. You also get image URLs for all Open Access CC0 public domain images.
If I want to find objects from a specific department, should I use the get_departments tool first? +
Yes, you must run get_departments before calling get_objects_by_department. This initial step gives you the necessary department ID, which you then pass to retrieve object IDs.
Does search_by_century return full artwork details or just identifiers? +
search_by_century only returns object IDs. To get the full metadata and images for those objects, you must follow up by using the get_object tool with those specific IDs.
What if I need to find pieces that have high-quality images, regardless of department? +
Use search_with_images. This tool supports all standard filters (like date or medium) but specifically limits results to objects confirmed to have available image data.
We've already built the connector for The Met Museum. 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.
Gemini 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.