Met Museum MCP Server vs Smithsonian MCP
A side-by-side look at the Met Museum MCP Server and Smithsonian 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 Smithsonian 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 Smithsonian MCP when
- You need dedicated capabilities in the Art & Culture domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
SMITHSONIAN_API_KEY, MCP_TRANSPORT, MCP_HOST, MCP_ALLOWED_HOSTS, UV_PROJECT_ENVIRONMENT. - You want tools like
simple_explore, continue_explore, search_collections.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Art & Culture | Art & Culture |
| Quality signal | 56/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | SMITHSONIAN_API_KEYMCP_TRANSPORTMCP_HOSTMCP_ALLOWED_HOSTSUV_PROJECT_ENVIRONMENT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 10 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 4 | 18 |
| Full listing | View Met Museum MCP Server | View Smithsonian 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
Smithsonian MCP tools 18
simple_exploreSmart diverse sampling across museums and object types (recommended for general discovery)continue_exploreGet more results about the same topic while avoiding duplicatessearch_collectionsAdvanced search with filters (prioritizes museum-specific results when unit_code specified)search_and_get_first_url**Easiest option**: Search and get validated URL in one step (prevents manual URL construction)get_object_detailsDetailed object informationget_object_urlGet validated object URLs with flexible identifier support (MANDATORY: never construct URLs manually)search_by_unitMuseum-specific searchesget_objects_on_viewFind objects currently on physical exhibitcheck_object_on_viewCheck if a specific object is on displayget_museum_collection_typesGet comprehensive list of object types available in each museum (based on systematic collection sampling)check_museum_has_object_typeCheck if a specific museum has objects of a particular type (e.g., paintings, sculptures)get_smithsonian_unitsList all museums- +6 more on the listing page
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"
]
}
}
}
Smithsonian MCP
{
"mcpServers": {
"molanojustin-smithsonian-mcp": {
"command": "uvx",
"args": [
"at"
],
"env": {
"SMITHSONIAN_API_KEY": "YOUR_SMITHSONIAN_API_KEY_HERE",
"MCP_TRANSPORT": "YOUR_MCP_TRANSPORT_HERE",
"MCP_HOST": "YOUR_MCP_HOST_HERE",
"MCP_ALLOWED_HOSTS": "YOUR_MCP_ALLOWED_HOSTS_HERE",
"UV_PROJECT_ENVIRONMENT": "YOUR_UV_PROJECT_ENVIRONMENT_HERE"
}
}
}
}
Frequently asked questions
Met Museum MCP Server is categorized under Art & Culture and uses a local stdio subprocess. Smithsonian MCP belongs to Art & Culture and uses a local stdio subprocess. Pick Met Museum MCP Server for art & culture work and Smithsonian 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. Smithsonian MCP is listed as free. Auth: api key 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 molanojustin-smithsonian-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 56/100 (Good) with 2 views, 0 installs and 4 GitHub stars. Smithsonian MCP has 57/100 (Good) with 2 views, 0 installs and 10 GitHub stars.