Museum MCP Server
Related Servers
Alternatives to Museum MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables searching artworks, artists, and exhibitions from the Art Institute of Chicago collection via natural language, returning detailed artwork information, artist biographies, and exhibition status through the ARTIC public API.2 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants with access to search, explore, and analyze over 3 million collection objects from the Smithsonian Institution's museums. Enables finding objects currently on exhibit, retrieving detailed metadata, high-resolution images, and 3D models from America's national museums.34 npm10MIT
- AlicenseNot gradedqualityCmaintenanceEnables searching the Metropolitan Museum of Art collection by subject, artist, or keyword, retrieving detailed artwork information, and listing curatorial departments via natural language.2 npm1MIT
- AlicenseBqualityCmaintenanceA server that provides access to the Art Institute of Chicago Collection through natural language interactions. This server allows AI models to search the Art Institute of Chicago Collection and have art works available as a Resource.66 npm5MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query a 282,731-node knowledge graph of art market transactions and provenance records, returning cited answers with <1% hallucination and explicit coverage gaps.5 npmMIT
- AlicenseAqualityAmaintenanceEnables AI-native access to Swiss cultural heritage data from SIK-ISEA (artists), Nationalmuseum (collections), and Nationalbibliothek (bibliography) via MCP tools, without authentication.11MIT
TDQS
Scored across 9 tools
The tools are mostly distinct, but `tool_search_artworks` (generic search) and `tool_search_by_artist`, `tool_search_by_department`, and `tool_search_by_period` could be confused, especially if the generic search already supports filtering. However, the focused search tools have clear parameters, so overlap is manageable.
Tools follow a consistent `tool_` prefix followed by a verb_noun pattern (e.g., `tool_get_met_departments`, `tool_search_artworks`). There are minor inconsistencies like `tool_compare_museums` (verb_object without underscore) and `tool_get_artwork_details` vs `tool_get_museum_highlights` but overall the pattern is recognizable.
With 9 tools, the server is well-scoped for a museum-focused MCP server. Each tool addresses a specific need (departments, search, details, random, highlights, comparisons), and the count is within the ideal range of 3-15.
The tool set covers the main museum browsing workflows: get departments, search by various criteria, get details, highlights, random, and comparison. Missing features might include artwork filtering by medium or sorting, but the current set supports core discovery and exploration without critical gaps.