← Directory

mikechao/metmuseum-mcp

Open Source
• Updated Jun 4, 2026, 06:35 PM

The MetMuseum MCP server is a server implementation of the Model Context Protocol (MCP) that integrates with the Metropolitan Museum of Art's public Collection API.

Use Cases ▼
01

Researching art history by asking an AI assistant to find and compare works by a specific artist or style.

02

Building a museum visitor chatbot that can answer questions about artworks on display or in storage.

03

Creating educational tools that allow students to explore cultural artifacts through conversational AI.

04

Generating curatorial insights by cross-referencing artworks based on medium, period, or cultural origin.

05

Populating art discovery apps with rich metadata and imagery from a trusted institutional source.

06

Prototyping AI-driven recommendation systems for museum collections.

What Problem It Solves ▼

AI developers and researchers often need to integrate domain-specific data sources into their LLM applications but face the challenge of bridging proprietary or public APIs with AI models. The MetMuseum MCP server solves this by providing a standardized interface that connects any MCP-enabled LLM to the Metropolitan Museum of Art's collection, enabling seamless natural language queries over millions of artworks without custom coding for each API endpoint.

Key Features ▼
✓

Easy integration with MCP-compatible AI clients.

✓

Access to a vast, high-quality museum collection dataset.

✓

Open source and self-hosted for full control and privacy.

✓

Well-documented with clear setup instructions.

✓

Modular and extensible for other API integrations.

Overview

The MetMuseum MCP server is a server implementation of the Model Context Protocol (MCP) that integrates with the Metropolitan Museum of Art's public Collection API. It allows Large Language Models (LLMs) and AI applications to search, retrieve, and display artworks from the Met's extensive collection. Built with TypeScript, the server exposes tools that enable natural language queries over the museum's data, making it possible to find artworks by artist, title, date, culture, medium, and more. The server handles API communication, data formatting, and presents results in a structured way suitable for AI agents.

Full Description ▼

Users can run the server locally via Docker or npm, and connect it to any MCP-compatible client, such as Claude Desktop or other AI assistants. Once connected, the AI can access detailed artwork metadata, including images, descriptions, dimensions, and provenance. This opens up possibilities for art exploration, research, education, and creative applications that require rich cultural data.

The project is open source, hosted on GitHub, and follows best practices for MCP server development. It includes pre-built scripts, CI workflows, and an AGENTS.md file to guide other agents. With a modular architecture and clear separation of concerns, the server can be extended to support additional museum APIs or custom functionalities.

Pros & Cons

Pros

+

Easy integration with MCP-compatible AI clients.

+

Access to a vast, high-quality museum collection dataset.

+

Open source and self-hosted for full control and privacy.

+

Well-documented with clear setup instructions.

+

Modular and extensible for other API integrations.

Cons

−

Limited to the Metropolitan Museum of Art's data and API constraints.

−

Requires technical knowledge to deploy and maintain.

−

Dependent on external API availability and rate limits.

Similar Tools

europeana-mcp-server smithsonian-mcp-server art-gallery-mcp museum-collections-api-mcp

More in Developer Tools