Met Museum Mcp Server
Let your coding agent search the Met’s open collection for artwork metadata, provenance, and images while you prototype cultural or educational products.
Overview
io.github.cyanheads/met-museum-mcp-server is a MCP server for the Idea phase that searches the Met’s 500K+ artwork catalog and returns metadata, provenance, and open-access image pointers for agent workflows.
What is this MCP server?
- Queries 500,000+ Met Museum artworks with rich metadata and provenance fields
- Supports open-access image discovery for compliant reuse in apps and demos
- Exposes collection search suitable for agent-driven literature and design research
- Ships as @cyanheads/met-museum-mcp-server v0.2.0 with stdio and streamable-http transports
- Optional hosted remote at met-museum.caseyjhand.com/mcp plus local HTTP on port 3010
- Catalog scale stated as 500K+ artworks in package description
- Package version 0.2.0 with stdio and streamable-http transports
- Published npm identifier @cyanheads/met-museum-mcp-server
Community signal: 3 GitHub stars.
What problem does it solve?
Building art or education apps means juggling opaque museum APIs and manual lookup instead of letting your agent pull verified object records in chat.
Who is it for?
Indie builders prototyping museum, travel, or learning products who want agent-native access to a large, reputable open collection.
Skip if: Teams that need write access, ticketing, or guaranteed high-res licensing outside Met open-access rules without their own legal review.
What do I get? / Deliverables
After you register the server, your agent can query Met collection data on demand so prototypes and content drafts cite real works and assets faster.
- Live MCP tools your agent can call against Met collection data
- Structured artwork metadata suitable for specs, landing copy, or seed content
- Pointers to open-access media where Met policy allows reuse
Recommended MCP Servers
Journey fit
Solo builders often need authoritative reference material and media before committing to a niche app; museum APIs support early discovery and content validation. Research is where you gather real datasets and inspiration—half a million catalog records beat guessing titles, dates, and licensing for open-access assets.
How it compares
Public museum data MCP bridge, not a hosted DAM or Shopify-style media library.
Common Questions / FAQ
Who is io.github.cyanheads/met-museum-mcp-server for?
It is for solo and small-team builders using AI coding agents who need Metropolitan Museum collection search and metadata during research or content-heavy builds.
When should I use io.github.cyanheads/met-museum-mcp-server?
Use it in the Idea or Validate phase when you are scoping a cultural, educational, or creative app and want the agent to ground copy and UI samples in real artwork records.
How do I add io.github.cyanheads/met-museum-mcp-server to my agent?
Install @cyanheads/met-museum-mcp-server from npm, run Bun with the package’s start:stdio script for local stdio, or point your MCP client at the streamable-http URL or the documented remote host.