Quick Verdict
Met Museum MCP is an unofficial community package maintained by mikechao, not a product of The Metropolitan Museum of Art. The npm version reviewed here is 1.0.0, and the server code is distributed under the MIT license. It exposes four MCP tools: list departments, search museum objects, retrieve one object’s details, and open the interactive Met Explorer MCP App. The package is useful for teaching, exploratory research, collection discovery, and MCP demonstrations, provided users keep its source and rights boundaries visible.
The software itself is free, but “MIT licensed” applies to the package code. It does not declare every record or image returned by The Met API free for every use. Object data, Open Access indicators, image availability, and rights statements must be checked against The Met Collection API and the museum’s policies. The Streamable HTTP mode also has no built-in user authentication. Prefer local stdio for individual use; if HTTP must be reachable over a network, place it behind authentication, source restrictions, rate limits, resource limits, and monitoring.
Best For
This server is best for educators, students, research assistants, cultural-content editors, and developers prototyping art-discovery interfaces. Its narrow four-tool surface is easy to explain: discover a department, search for IDs, inspect selected objects, and optionally browse through an MCP App. Results can be traced back to The Met object records instead of relying on a model’s memory alone.
It is not a substitute for an official museum service agreement, a complete collection mirror, a digital asset management system, or automated rights clearance. Teams that need broad web research can compare Perplexity. Those building a visual knowledge application may prefer Dify, while n8n is more suitable when the real requirement is a multi-step data workflow rather than a dedicated museum MCP adapter.
Key Features
list-departments: returns valid Met curatorial departments and identifiers that can be used as search filters.search-museum-objects: searches by query and supports image availability, title, department, and pagination controls.get-museum-object: retrieves open object information by ID and can include image content when an eligible image exists and the request enables it.open-met-explorer: opens an interactive search and filtering interface in MCP clients that implement MCP Apps.- Two transports: stdio is the default for local clients; Streamable HTTP supports network integration but requires an external authentication boundary.
- Community package: npm package
metmuseum-mcpversion 1.0.0, MIT-licensed server code, with collection data obtained from The Met Collection API.
The four tools deliberately provide query and presentation functions rather than a full data warehouse. Applications should preserve object identifiers, source links, Open Access status, and rights text so users can verify a result at its origin.
Use Cases
In a classroom, students can compare how a topic appears across curatorial departments, then inspect dates, media, artists, and credit lines for selected objects. A researcher can build an initial reading or viewing list and retain object IDs as citations. A content editor can shortlist images, but publication should wait until the original object page and rights status have been checked.
The Met Explorer tool is useful when the target client supports MCP Apps and users benefit from interactive filtering. Clients without that extension can still use the other three data tools. Test the app surface and the underlying tool calls separately; failure to render an app does not necessarily mean search or retrieval is unavailable.
Remote HTTP deployment deserves stricter controls than a local demonstration. The endpoint does not include built-in user authentication. Even though the tools primarily read public data, an exposed process can be abused for repeated requests, bandwidth consumption, memory pressure, or upstream API load. Put it behind an authenticated gateway, cap request rates and response sizes, and avoid running it in the same high-privilege process as tools that can write files or access private databases.
Pricing
Version 1.0.0 is MIT-licensed and has no software license fee. Operators still pay for their Node.js runtime, host, network transfer, gateway, logging, and monitoring. The Met Collection API is an upstream service with its own availability, behavior, and policies; the community package cannot promise an uptime level or freeze upstream fields.
Code licensing and content rights are separate decisions. The MIT license permits use of the server code under its terms. Museum metadata and images must be evaluated using the object response, Open Access status, the source record, and The Met’s official guidance. An image does not gain a new license merely because it was returned inside an MCP result.
Pros
- Four tools create a small, understandable permission and testing surface.
- Results originate from The Met Collection API and can be verified on source records.
- Stdio and Streamable HTTP cover local and network-oriented integration patterns.
- The Met Explorer app offers a more visual experience in compatible MCP clients.
- The MIT license makes the server code straightforward to inspect, adapt, and self-host.
- Search filters and pagination support controlled exploration instead of oversized responses.
- The package is focused on one collection rather than pretending to be a universal research system.
Cons
- It is an unofficial community project with no Met support or service commitment.
- HTTP mode lacks built-in user authentication and should not be exposed directly.
- Availability, fields, object status, and limits depend on The Met API.
- The MIT code license does not clear all metadata and image rights for publication.
- Returning image content can increase response size, memory use, and client processing cost.
- The interactive app requires MCP Apps support and may not render in every client.
- It does not provide a complete collection mirror, rights-clearing workflow, or academic citation manager.
Alternatives
| Option | Primary focus | Data scope | Operation | Better fit when |
|---|---|---|---|---|
| Met Museum MCP | MCP access to The Met collection | One museum’s public API | Local stdio or self-hosted HTTP | Art education and collection exploration |
| Perplexity | Web answers with sources | Public web | Online service | Initial research spans many institutions |
| Dify | AI application building | User-provided knowledge and APIs | Cloud or self-hosted | Building a complete knowledge product |
| n8n | Workflow automation | User-connected APIs and databases | Cloud or self-hosted | Batch processing and scheduled data flows |
| LangChain | Model application framework | Custom tools and sources | Local or self-hosted | Writing a tailored research application |
| Open WebUI | Self-hosted model interface | Depends on attached models and tools | Local or server | A unified conversational front end is needed |
These products are not direct replacements for the same four tools. They represent broader choices: a dedicated collection adapter, general web research, a visual application platform, workflow automation, a code framework, or a self-hosted user interface.
FAQ
Is this an official server from The Metropolitan Museum of Art?
No. It is a third-party community implementation maintained by mikechao. It uses The Met Collection API but is not officially associated with the museum.
How many tools are in version 1.0.0?
There are four: list-departments, search-museum-objects, get-museum-object, and open-met-explorer. Older descriptions that mention only three omit the app-opening tool.
Does the MIT license make every returned image commercially reusable?
No. MIT covers the server code. Check the object’s Open Access status, source record, image information, and The Met’s official rights policy before publishing or redistributing content.
Can I expose the HTTP endpoint directly to the internet?
That is not recommended. The server has no built-in user authentication. Use an authenticated gateway plus source controls, rate limits, monitoring, timeouts, and resource caps.
Why might an object have no image?
An object may have no digitized image, its image may not be Open Access, or the upstream image service may be temporarily unavailable. Applications should treat “no image” as a normal result.
Do I need a client that supports MCP Apps?
Only for the interactive Met Explorer experience. Department listing, search, and object retrieval can still work as normal MCP tools in clients without app rendering.
Bottom Line
Met Museum MCP 1.0.0 is a focused community adapter whose four tools are sufficient for department browsing, collection search, object verification, and an optional interactive explorer. Its simplicity, MIT-licensed code, and local stdio mode make it attractive for education and prototypes. The limits are equally important: it is unofficial, depends on The Met API, ships HTTP without user authentication, and cannot transfer content rights through its software license. Add access controls for remote use and verify source rights before publication.