Skip to main content
Glama
mildlydiverting

whitney-museum-mcp-server

by mildlydiverting
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to whitney-museum-mcp-server

No user-submitted related servers found.

    Related Servers

    • mcp-artic

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      4 npm
      MIT

    • mcp-art

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching the Metropolitan Museum of Art collection by subject, artist, or keyword, retrieving detailed artwork information, and listing curatorial departments via natural language.
      4 npm
      1
      MIT

    • Smithsonian MCP Server

      AlexLin1234
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables searching and exploring millions of items from the Smithsonian Institution's collections including artifacts, artworks, specimens, photographs, and more, using the Smithsonian Open Access API.
      3
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each resource has a clear search/get or relationship tool, and the overlap between whitney_artist_artworks and whitney_search_artworks is explicitly resolved in the descriptions. whitney_query is positioned as an escape hatch for unsupported queries, not as a competing primary tool.

    Naming Consistency4/5

    The whitney_ prefix with search_/get_ resource names forms a clear pattern for most tools. The exceptions are whitney_artist_artworks and whitney_artist_exhibitions, which use a possessive noun style rather than a verb_noun style, and whitney_query, which is a one-off.

    Tool Count5/5

    11 tools is well-scoped for a museum API covering artists, artworks, exhibitions, events, and guides, plus relationship helpers and a query escape hatch. Each tool has a distinct job and none feel redundant.

    Completeness4/5

    Core read-only workflows are covered: search and detail retrieval exist for artworks, artists, and exhibitions, and searches exist for events and guides. The main gap is the lack of typed getters for individual events and guides, which the guide description implies should exist; whitney_query can work around this but it is less discoverable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources