art.travel/mcp (MCP Server)

This Model Context Protocol (MCP) server exposes art-tourism data from travel.art to AI agents, including biennales, art fairs, museums, and layover itineraries with 2026 facts. It provides access to four MCP tools over Streamable HTTP using request/response mode and JSON-RPC 2.0 over HTTP POST.

🛠️ Key Features

MCP server for art-tourism data (biennales, art fairs, museum visitor guides, layover itineraries)
Live endpoint: https://mcp.travel.art/
Public, unauthenticated, free
Tooling: 4 tools via MCP Streamable HTTP (JSON-RPC 2.0 over HTTP POST)

🚀 Use Cases

Query travel.art’s catalogue of biennales, art fairs, and festivals
Retrieve museum-related visitor guidance
Generate layover itineraries using 2026 facts

⚡ Developer Benefits

Structured tool access through MCP (4 tools total)
JSON-RPC 2.0 over HTTP POST request/response workflow
Topic coverage includes museums, tourism, and travel

⚠️ Limitations

Available functionality is limited to the four exposed tools
Server description provided only includes find_art_events details; other tools are not specified here

mcp/

Model Context Protocol server for travel.art. Live at https://mcp.travel.art/.

What it does

Exposes travel.art's art-tourism data to AI agents over the Model Context Protocol (Streamable HTTP transport, request/response mode).

Three tools as of v1:

find_art_events — biennales, art fairs, festivals with dates, venues, ticket info, summaries, links to full guides
find_museum_guide — major museums (Louvre, Vatican, Uffizi) with 2026 ticket info, opening hours, essential works
recommend_art_trip — city-based itinerary using only published travel.art content

Catalogue v1.6.0: 23 events + 12 museums + 6 layover itineraries (synced from the published calendar and cornerstone articles; event facts re-verified 2026-09-14).

Stack

code

mcp/
  src/
    index.ts        # Worker entry, MCP HTTP protocol (JSON-RPC 2.0)
    tools.ts        # Tool definitions + handlers
    data.ts         # Static dataset (typed)
  scripts/          # (Future) sync from content/<slug>/index.md frontmatter
  data/             # (Future) sync output
  package.json
  wrangler.toml
  tsconfig.json

Runtime: Cloudflare Workers, free tier (100k requests/day)
Language: TypeScript
Transport: MCP Streamable HTTP (request/response, no SSE — single-shot tool calls)
Protocol version: 2025-03-26
Auth: None (public read-only)

Use it

Health check

bash

curl https://mcp.travel.art/health

Initialize handshake

bash

curl -X POST https://mcp.travel.art/ \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"my-client","version":"0.1"}}}'

List tools

bash

curl -X POST https://mcp.travel.art/ \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'

Call a tool

bash

curl -X POST https://mcp.travel.art/ \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"find_art_events","arguments":{"country":"IT"}}}'

Claude Desktop config

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):

json

{
  "mcpServers": {
    "travel-art": {
      "url": "https://mcp.travel.art/"
    }
  }
}

Deploy

bash

cd mcp
npm install
npx wrangler deploy

(Requires CLOUDFLARE_API_TOKEN + CLOUDFLARE_ACCOUNT_ID in env or wrangler login.)

The Worker is bound to the mcp.travel.art custom domain via Cloudflare API (one-time setup; see DECISIONS.md 2026-05-08).

Future (v2 backlog)

Build-time data extraction — replace hand-curated data.ts with a sync script that reads content/<slug>/index.md frontmatter (events from Event-typed schema, museums from Place-typed schema). New cornerstones flow into MCP automatically.
More tools — find_artist_residencies, find_collateral_events, today_in_art_tourism (calendar of what's open today across our catalogue).
Authentication tier — currently public read-only. If commercial clients want high-volume programmatic access, add API-key tier under Account API Tokens.
Streaming responses — for long itinerary recommendations, switch to SSE.
Rate limiting — per-IP throttle (currently relies on Cloudflare's own DDoS protection).
Schema versioning — mcp.travel.art/v1, /v2 URL versioning when we break compatibility.

See .claude/agents/mcp-architect.md for the full agent operating spec.

query	string	optional	Free-text query (event name, theme, keyword). Optional.
country	string	optional	ISO 3166-1 alpha-2 country code (e.g., 'IT', 'CH', 'GB', 'US'). Optional filter.
type	string	optional	Filter by event type. Optional.
activeOn	string	optional	ISO 8601 date (YYYY-MM-DD). Returns only events whose date range covers this date. Optional.
startsAfter	string	optional	ISO 8601 date. Returns only events starting on or after this date. Optional.
endsBefore	string	optional	ISO 8601 date. Returns only events ending on or before this date. Optional.

query	string	optional	Free-text query (museum name, work, artist, city). Optional.
city	string	optional	City filter (e.g., 'Paris', 'Rome', 'Florence'). Optional.
country	string	optional	ISO 3166-1 alpha-2 country code. Optional.

query	string	optional	Free-text query (city, artist, museum, airport, theme). Optional.
city	string	optional	City filter (e.g., 'Milan', 'Rome', 'Florence', 'Amsterdam', 'Paris', 'London'). Optional.
country	string	optional	ISO 3166-1 alpha-2 country code (e.g., 'IT', 'NL', 'FR', 'GB'). Optional.
airport	string	optional	IATA airport code the layover serves (e.g., 'MXP', 'FCO', 'AMS', 'CDG', 'LHR'). Optional filter.
maxDurationHours	number	optional	Maximum time-on-ground budget in hours. Returns only itineraries that fit ≤ this duration. Optional.

city	string	required	Destination city (e.g., 'Paris', 'Venice', 'Florence', 'London', 'Basel', 'Miami Beach').
startDate	string	optional	ISO 8601 trip start date. Optional — if provided, filters events to those active on or near these dates.
endDate	string	optional	ISO 8601 trip end date. Optional.

travel.art

art.travel/mcp (MCP Server)

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

find_art_events

find_museum_guide

find_layover_itinerary

recommend_art_trip

mcp/

What it does

Stack

Use it

Health check

Initialize handshake

List tools

Call a tool

Claude Desktop config

Deploy

Future (v2 backlog)

Install

Remote endpoint

Related servers