In-depth architectural comparison of the Smithsonian MCP and Metmuseum MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Smithsonian MCP
Art & Culture · Local stdio
Quality: 55/100 (Good) | Auth: API Key required
Metmuseum MCP
Art & Culture · Local stdio
Quality: 64/100 (Good) | Auth: No auth required
Verdict Summary: Choose Smithsonian MCP if you need specialized Art & Culture tools running via a local process. Choose Metmuseum MCP if your workspace requires Art & Culture integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Smithsonian MCP when:
You need dedicated capabilities in the Art & Culture domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: SMITHSONIAN_API_KEY.
Smithsonian MCP is categorized under Art & Culture and uses a local stdio subprocess. In contrast, Metmuseum MCP belongs to Art & Culture using local stdio subprocess. Select Smithsonian MCP when you need capabilities focused on art & culture and Metmuseum MCP when you require tools for art & culture.
Get validated object URLs with flexible identifier support (MANDATORY: never construct URLs manually)
search_by_unit
Museum-specific searches
get_objects_on_view
Find objects currently on physical exhibit
check_object_on_view
Check if a specific object is on display
get_museum_collection_types
Get comprehensive list of object types available in each museum (based on systematic collection sampling)
check_museum_has_object_type
Check if a specific museum has objects of a particular type (e.g., paintings, sculptures)
get_smithsonian_units
List all museums
+6 more tools listed on main page
Metmuseum MCP Tools (4)
list-departments
List all departments in the Metropolitan Museum of Art (Met Museum)
search-museum-objects
Search 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-object
Get 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-explorer
Open 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.