A side-by-side look at the Harvard Art and Met Museum MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Harvard Art for art & culture work as a local process; choose Met Museum MCP Server for art & culture as a local process. You can also run both side by side in one mcpServers block.
search, object.met_list_departments, met_search_collections, met_list_objects.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Art & Culture | Art & Culture |
| Quality signal | 51/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 4 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 2 | 4 |
| Full listing | View Harvard Art | View Met Museum MCP Server |
searchSearch the Harvard Art Museums collection by keyword. Returns matching items with ids (pass an id to object), titles, creators, dates and image links.objectFetch full details for one Harvard Art Museums item by id — a Harvard Art Museums object id (numeric, from search).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 contentPaste 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.
{
"mcpServers": {
"harvard-art": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-harvard-art"
]
}
}
}
{
"mcpServers": {
"met-museum-mcp-server": {
"command": "bunx",
"args": [
"@cyanheads/met-museum-mcp-server@latest"
]
}
}
}