Skip to main content
Glama
mikechao

Met Museum MCP Server

by mikechao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Met Museum MCP Server

No user-submitted related servers found.

    Related Servers

    • theo-van-gogh-mcp

      johnfire
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that lets AI assistants manage an art catalogue — find paintings, post to social media, upload to galleries, schedule posts, and update metadata.
      -

    • mcp-va-museum

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for querying the Victoria and Albert Museum (V\&A) collections via natural language or direct tool calls.
      5 npm
      2
      MIT

    • art-mcp

      puf3zin
      A
      license
      A
      quality
      D
      maintenance
      MCP server for searching museum collections and viewing artwork images and metadata from multiple museums, including the Met, Art Institute of Chicago, Rijksmuseum, and more.
      2
      4
      7 npm
      2
      MIT

    • solid-mcp

      jeswr
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for the Solid protocol enabling AI models to read, write, search, and manage resources in Solid pods.
      1
      MIT

    • artic-mcp

      mikechao
      A
      license
      B
      quality
      C
      maintenance
      A 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.
      6
      9 npm
      5
      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.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get-museum-object retrieves details by ID, list-departments lists departments, open-met-explorer launches an interactive app, and search-museum-objects performs filtered searches. There is no ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent verb-noun pattern with lowercase hyphens (e.g., get-museum-object, list-departments). No mixing of styles.

    Tool Count5/5

    Four tools is an appropriate count for a museum collection server covering search, detail retrieval, department listing, and an interactive explorer. Not too sparse or overwhelming.

    Completeness4/5

    The tool surface covers key read operations (search, detail, departments) and an interactive explorer. Minor gaps like direct department-based object listing are covered by search filters, so no significant missing functionality.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources