artic
A Model Context Protocol (MCP) 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.
claude mcp add --transport stdio mikechao-artic-mcp node server.js
How to use
The Art Institute of Chicago MCP Server provides AI-friendly access to the Art Institute of Chicago Collection through a set of dedicated tools. These tools enable models to search artworks by title, fetch detailed information about a specific artwork, perform full-text searches across metadata, find artists, locate artworks by a given artist, and search by medium. A special art-gallery prompt is also available to generate an interactive gallery visualization for a chosen artist. Each tool returns structured data, including titles, IDs, descriptions, and, when available, image data or references, making it straightforward to incorporate into reasoning and planning workflows.
To use the tools, interact with the server’s endpoints using the tool names described in the Features list (search-by-title, get-artwork-by-id, full-text-search, search-for-artist, get-artwork-by-artist, search-by-medium, and art-gallery). For example, a model can request artworks by a specific title, retrieve a piece by its ID to obtain full metadata and image information, or run a full-text search to discover artworks related to a broader query. The art-gallery prompt helps generate a ready-to-render HTML gallery for a given artist, useful for visualization steps in an analytics or creative workflow.
How to install
Prerequisites:
- Node.js (LTS version) installed on your system
- Git (optional, for cloning the repository)
Installation steps:
-
Clone the repository (replace with the actual source URL if different): git clone https://github.com/mikechao/artic-mcp.git cd artic-mcp
-
Install dependencies: npm install
-
Configure environment variables if needed (see additional_notes for details). Create a .env file at the project root if required by your deployment.
-
Start the MCP server locally: node server.js
-
(Optional) If you are deploying with a process manager, ensure the startup script uses the same entry point (server.js) and that environment variables are loaded in the deployment environment.
Additional notes
Notes and tips:
- If the server requires API keys or access tokens for the Art Institute of Chicago API, set them in environment variables (e.g., ARTIC_API_KEY) as described in your deployment environment. The README does not specify keys, so verify if authentication is needed in your deployment.
- The tools return structured results with fields like Title, Artwork ID, Description, and metadata. Use these fields to guide reasoning or to render UI components in downstream applications.
- If you encounter rate limits or API availability issues from the Art Institute of Chicago, consider implementing client-side caching or request backoff strategies in your consuming model.
- Ensure your hosting environment exposes the server on the expected port and that any firewall rules or reverse proxies allow traffic to the MCP gateway.
Related MCP Servers
obsidian -tools
Add Obsidian integrations like semantic search and custom Templater prompts to Claude or any MCP client.
ironcurtain
A secure* runtime for autonomous AI agents. Policy from plain-English constitutions. (*https://ironcurtain.dev)
CanvasMCPClient
Canvas MCP Client is an open-source, self-hostable dashboard application built around an infinite, zoomable, and pannable canvas. It provides a unified interface for interacting with multiple MCP (Model Context Protocol) servers through a flexible, widget-based system.
vikunja
Model Context Protocol server for Vikunja task management. Enables AI assistants to interact with Vikunja instances via MCP.
grok-faf
First MCP server for Grok | FAST⚡️AF • URL-based AI context • Vercel-deployed
mcp-turso
MCP server for interacting with Turso-hosted LibSQL databases