Purpose
travel-art-mcp is the Model Context Protocol (MCP) server for travel.art, with the goal of exposing travel.art's art travel data to AI agents. The data scope includes biennales (such as the Venice Biennale, the Whitney Biennial), art fairs (such as Art Basel, Frieze), major museum visiting guides, and art travel recommendations.
Main capabilities
As of v1, the server provides three tools:
- find_art_events: Find biennales, art fairs, and art festivals, returning dates, venues, ticketing information, summaries, and links to full guides.
- find_museum_guide: Provides 2026 ticketing information, opening hours, and must-see works for major museums (the Louvre, the Vatican Museums, the Uffizi Gallery).
- recommend_art_trip: Generates itinerary recommendations based on a city, using only content already published by travel.art.
The catalog version is v1.6.0, containing 23 events, 12 museums, and 6 layover itineraries. The data is synced from the published calendar and core articles, and event facts were re-verified on 2026-09-14.
How to use
The server's online address is https://mcp.travel.art/。传输方式为 MCP Streamable HTTP (request/response mode, no SSE, single tool call). The protocol version is 2025-03-26. Authentication is none (public read-only).
The runtime is the Cloudflare Workers free tier (100,000 requests per day), and the language is TypeScript.
Claude Desktop configuration: add to ~/Library/Application Support/Claude/claude_desktop_config.json on macOS (requires CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID in environment variables, or use wrangler login). The Worker is bound to the mcp.travel.art custom domain via the Cloudflare API (one-time setup, see DECISIONS.md 2026-05-08).
Suitable scenarios
Suitable for scenarios that need to connect art travel information to AI agents, such as querying biennale and art fair schedules, obtaining museum visiting guides, and generating city-based art travel itineraries.
Limitations and future plans
Currently public read-only, with no authentication; the transport is request/response mode and does not support streaming responses; rate limiting relies on Cloudflare's own DDoS protection, with no per-IP rate limiting for now; no URL versioning for now (planned to introduce mcp.travel.art/v1, /v2 when compatibility is broken).
v2 to-dos include: build-time data extraction (use a sync script to read content/<slug>/index.md frontmatter, replacing the manually maintained data.ts, so that new core articles automatically enter the MCP); more tools (find_artist_residencies, find_collateral_events, today_in_art_tourism); authentication tiers (provide an API-key tier for commercial customers); streaming responses (switch long itinerary recommendations to SSE); rate limiting (per-IP rate limiting); schema versioning. For the complete agent operating specification, see .claude/agents/mcp-architect.md.
