Met Museum MCP Server vs Metmuseum MCP
A side-by-side look at the Met Museum MCP Server and Metmuseum MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Met Museum MCP Server for art & culture work as a local process; choose Metmuseum MCP for art & culture as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Met Museum MCP Server when
- You need dedicated capabilities in the Art & Culture domain.
- You prefer a local stdio subprocess transport.
- You want tools like
met_list_departments, met_search_collections, met_list_objects.
Choose Metmuseum MCP when
- You need dedicated capabilities in the Art & Culture domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
list-departments, search-museum-objects, get-museum-object.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Art & Culture | Art & Culture |
| Quality signal | 52/100 · Good | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 35 |
| Directory activity | 1 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 4 | 4 |
| Full listing | View Met Museum MCP Server | View Metmuseum MCP |
Tools & capabilities
Met Museum MCP Server tools 4
met_list_departmentsReturn all 19 curatorial departments with their numeric IDs and display namesmet_search_collectionsSearch the collection by keyword, optionally matched in titles or tags only, with filters for department, date range, medium, geography, image availability, on-view status, and highlight designationmet_list_objectsList every object ID in a department, every object created or revised since a date, or both, without a keywordmet_get_objectFetch full records for one or more object IDs — metadata, provenance, artist info, CC0 image URLs, tags, and Wikidata links — optionally with up to 3 CC0 images as image content
Metmuseum MCP tools 4
list-departmentsList all departments in the Metropolitan Museum of Art (Met Museum)search-museum-objectsSearch for objects in the Metropolitan Museum of Art (Met Museum). Will return Total objects found, followed by a paginated list of Object Ids. If the Met Explorer app (open-met-explorer) is open and the user is referring to its existing results, prefer using those results from context instead of calling this tool. The parameter title should be set to true if you want to search for objects by title. The parameter hasImages is false by default, but can be set to true to return only objects with images. Additional optional filters are available for highlights, tags, on-view status, artist/culture match, medium, geographic location, and date range. Use page and pageSize to paginate results.get-museum-objectGet a museum object by its ID, from the Metropolitan Museum of Art Collection. Use this when the user asks for deeper details on a specific object ID.open-met-explorerOpen the interactive Met Explorer app for browsing and filtering objects. For exploration intents, pass q so the app can run a live search on open. After opening, keep your chat handoff short and UI-focused. For deeper details on a specific object ID, prefer get-museum-object.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Met Museum MCP Server
{
"mcpServers": {
"met-museum-mcp-server": {
"command": "bunx",
"args": [
"@cyanheads/met-museum-mcp-server@latest"
]
}
}
}
Metmuseum MCP
{
"mcpServers": {
"mikechao-metmuseum-mcp": {
"command": "npx",
"args": [
"-y",
"metmuseum-mcp"
]
}
}
}
Frequently asked questions
Met Museum MCP Server is categorized under Art & Culture and uses a local stdio subprocess. Metmuseum MCP belongs to Art & Culture and uses a local stdio subprocess. Pick Met Museum MCP Server for art & culture work and Metmuseum MCP for art & culture.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Met Museum MCP Server has no declared pricing — check the project's own site. Metmuseum MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add met-museum-mcp-server and mikechao-metmuseum-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Met Museum MCP Server has a quality signal of 52/100 (Good) with 1 views, 0 installs and 4 GitHub stars. Metmuseum MCP has 64/100 (Good) with 6 views, 0 installs and 35 GitHub stars.