
Connects your MCP client to The Metropolitan Museum of Art's collection data through Pipeworx's gateway infrastructure. The source documentation doesn't list specific tools, but you can query Met collection information using the ask_pipeworx interface by asking questions in plain English rather than calling structured endpoints. Part of Pipeworx's larger network of 842+ data sources, so you can either use the dedicated Met endpoint or tap into the full gateway. Useful when you're building agents that need to search artwork, retrieve object details, or explore the museum's public collection programmatically without writing custom API clients.
The Metropolitan Museum of Art Collection MCP.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
search_artworks | Search The Met's open-access collection by keyword. Optionally filter to objects with images, currently on view, by medium, or by a year range. Returns compact records (title, artist, date, medium, image) hydrated from object detail. Keyless. |
get_artwork | Get the rich detail for a single Met collection object by its objectID — artist bio, medium, dimensions, department, classification, culture, period, credit line, image URLs, tags, and gallery number. Keyless. |
list_departments | List The Met's curatorial departments (e.g. European Paintings, Egyptian Art, Arms and Armor) with their department IDs, usable to scope searches. Keyless. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"metmuseum": {
"url": "https://gateway.pipeworx.io/metmuseum/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/metmuseum/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Metmuseum data" })
The gateway picks the right tool and fills the arguments automatically.
MIT
curl -X POST https://gateway.pipeworx.io/v1/tools/metmuseum_search_artworks \
-H 'Content-Type: application/json' \
-d '{"q":"sunflowers"}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/metmuseum_search_artworks. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.