Skip to main content
Glama
Städel Museum MCP Server

Städel Museum MCP Server

Städel Museum MCP Server

A Model Context Protocol server that gives AI assistants direct access to the Städel Museum Digital Collection. It talks to the museum's public OAI-PMH interface (LIDO metadata format), so an assistant can harvest object records, read rich multilingual metadata, and display high-resolution artwork images — with an interactive browsing UI (MCP Apps) on top.

This is a personal portfolio project built to demonstrate working with the Model Context Protocol, an OAI-PMH/LIDO harvesting API, and MCP Apps interactive UIs end-to-end — not an official Städel Museum product.

Features

Tool

Description

list-sets

Lists the OAI-PMH sets (e.g. Masterpieces, Prints and Drawings) available to filter by.

search-museum-objects

Harvests the identifiers of live (non-deleted) objects, filtered by set and/or a from/until date range, with pagination via resumptionToken.

get-museum-object

Resolves one object's full LIDO record into clean, normalized JSON — titles, artists, date, medium, dimensions, image, license — plus the image itself.

open-staedel-explorer

Opens an interactive MCP App UI for browsing and filtering the collection visually, in hosts that support it.

Because the Städel exposes its collection through OAI-PMH (a harvesting protocol, not a search engine), there is no full-text keyword search — you filter by set and/or date range, then fetch full details per object. The tool descriptions make this explicit so the assistant doesn't assume Google-style search is available.

Related MCP server: artic-mcp

Architecture

src/
├── index.ts      # entry point: stdio, or stateless Streamable HTTP with --http
├── server.ts     # the four tools and the explorer UI resource
├── api.ts        # OAI-PMH client: throttled fetch, retry, XML parsing
├── lido.ts       # flattens a LIDO record into the normalized object (and its Zod schema)
└── explorer.ts   # the self-contained MCP App HTML for the explorer

lido.ts does the interesting work: LIDO is a verbose, multilingual, deeply nested XML format, and flattenLido turns it into a small, stable JSON shape — resolving xml:lang variants (preferring English, falling back to German), picking the largest image rendition, and reading each object's actual rights statement instead of assuming one blanket license.

Licensing & Attribution (important)

  • Metadata harvested from the OAI-PMH interface is CC0 1.0 (public domain).

  • Images are typically CC BY-SA 4.0 Städel Museum, Frankfurt am Main, though some objects carry a different rights statement (e.g. Public Domain Mark) — get-museum-object reports the actual license for each object rather than hard-coding one.

  • Whenever an assistant displays or describes an image from this server, it should include the credit line reported in the license field.

Prerequisites

Installation

git clone https://github.com/topoftheblock/staedel-mcp.git
cd staedel-mcp
corepack enable
pnpm install
pnpm run build

Running

Stdio (used by Claude Desktop, Claude Code, and most MCP clients):

node dist/index.js

Streamable HTTP (for testing with clients that connect over HTTP):

node dist/index.js --http
# -> http://localhost:3001/mcp  (localhost only; override the port with the PORT env var)

Add it to Claude Desktop / Claude Code

Add to your MCP client's config (e.g. claude_desktop_config.json):

{
  "mcpServers": {
    "staedel-museum": {
      "command": "node",
      "args": ["/absolute/path/to/staedel-mcp/dist/index.js"]
    }
  }
}

Try it with the MCP Inspector

npx @modelcontextprotocol/inspector node dist/index.js

Development

pnpm run watch   # tsc --watch
pnpm run check   # type-check without emitting

Configuration

Environment variable

Default

Purpose

STAEDEL_API_TIMEOUT_MS

10000

Per-request timeout to the Städel API.

PORT

3001

Port for --http mode.

Reference

Available Tools

4 tools
get-museum-objectA

Get detailed information about a specific Städel museum object by its OAI identifier (e.g. oai:DE-MUS-048017:2442) or bare object number (e.g. 2442). Returns metadata and optionally the high-resolution image.

Inputs: objectId (required), returnImage. Returns: object

list-setsA

Lists all organizational sets (collections/departments) available in the Städel Museum OAI-PMH interface.

Inputs: no named parameters. Returns: sets

open-staedel-explorerA

Open the interactive Städel Explorer app for browsing and filtering objects visually.

Inputs: set, from. Returns: initialState

search-museum-objectsA

Harvests a list of object identifiers from the Städel Museum. Note: This uses OAI-PMH, so standard full-text keyword searching is not supported. You must filter by date or Set. Returns a list of identifiers to be used with the get-museum-object tool.

Inputs: set, from, until, resumptionToken. Returns: records, pageCount, resumptionToken

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct purpose: list-sets retrieves organizational sets, search-museum-objects harvests identifiers for objects, get-museum-object retrieves full details of a specific object, and open-staedel-explorer provides an alternative visual browsing experience. There is no overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent verb-noun pattern with lowercase and hyphens (e.g., list-sets, get-museum-object). The verbs are descriptive and the nouns clearly indicate the resource or action, making it easy to understand the tool's function.

    Tool Count5/5

    With 4 tools covering set listing, object search, object detail retrieval, and a visual explorer, the count is well-scoped and appropriate for the domain. There are no redundant or missing tools for the intended functionality.

    Completeness5/5

    The tool set covers the complete workflow: discover sets (list-sets), find objects within a set (search-museum-objects), get detailed information (get-museum-object), and optionally explore visually (open-staedel-explorer). Given the OAI-PMH constraints, there are no essential gaps.

    Related MCP Connectors

    Related MCP Servers

    • 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
      175 npm
      35
      MIT
    • A
      license
      B
      quality
      D
      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
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides access to European cultural heritage collections and artworks, allowing users to search for items, get detailed information about specific artworks, browse collections by institution, and receive AI-powered recommendations based on interests.
      1
      -