Städel Museum MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list-setsA | Lists all organizational sets (collections/departments) available in the Städel Museum OAI-PMH interface. |
| 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. |
| 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. |
| open-staedel-explorerA | Open the interactive Städel Explorer app for browsing and filtering objects visually. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Städel Explorer | Interactive UI for browsing and filtering the Städel Museum digital collection. |
TDQS
Scored across 4 tools
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.
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.
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.
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.