Skip to main content
Glama
cfpramod

open-museum-mcp

by cfpramod
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to open-museum-mcp

  • Met Museum MCP Server

    mikechao
    A
    license
    A
    quality
    C
    maintenance
    A MCP Server that lets user ask AI models to discover the collection of the Metropolitan Museum of Art. Adds the discovered art works as Resources on the server.
    4
    242 npm
    35
    MIT

Related Servers

  • @cyanheads/met-museum-mcp

    cyanheads
    A
    license
    Not graded
    quality
    A
    maintenance
    Searches the Metropolitan Museum of Art collection and fetches full artwork records with open-access images via MCP, supporting STDIO and Streamable HTTP transports.
    296 npm
    4
    Apache 2.0

  • webfetch

    ashlrai
    A
    license
    A
    quality
    A
    maintenance
    License-first federated image search for AI agents and humans. Exposes MCP tools for concise, attribution-aware image discovery, license probing, and guarded downloads across open, platform, and editorial sources.
    7
    18 npm
    3
    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

  • free-image-library

    surendranb
    A
    license
    A
    quality
    B
    maintenance
    Enables keyless search and retrieval of millions of openly-licensed Creative Commons images and audio, with ready-to-paste attribution and license-awareness built into every result.
    5
    MIT

  • mcp-clevelandart

    pipeworx-io
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables querying the Cleveland Museum of Art's open access API to search artworks by filters like type, artist, and CC0 status, retrieve details by accession number, find creators, and explore exhibitions.
    4 npm
    1
    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 5 tools

Disambiguation5/5

Each tool has a distinct, non-overlapping purpose: cite for citations, discover_random for random selection, get_artwork for specific artwork retrieval, list_traditions for metadata exploration, and search_artworks for querying. No ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in lowercase snake_case (e.g., search_artworks, list_traditions), with 'cite' being a concise verb that fits the pattern. Highly predictable and readable.

Tool Count5/5

With 5 tools covering search, retrieval, citation, random discovery, and metadata listing, the set is well-scoped for a museum API. Each tool earns its place without redundancy.

Completeness5/5

The tool set covers all essential operations for a read-only museum data API: searching, fetching single items, citing, random discovery, and exploring available traditions. No obvious gaps given the domain.

Maintenance

ActivityActive
ResponsivenessWithin a week

Resources