Skip to main content
Glama

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).

Related MCP server: Museum MCP Server

Stack

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

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

Initialize handshake

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

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

Call a tool

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):

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

Deploy

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.

Available Tools

4 tools
find_art_eventsAInspect

Search travel.art's catalogue of upcoming and current art events (biennales, art fairs, festivals). Returns events with dates, venues, ticket info, summary, and a link to travel.art's full visitor guide. Use for queries like 'when is Venice Biennale 2026', 'art fairs in October 2026', 'what's on in Miami in December'.

Inputs: type, query, country, activeOn, +2 more.

find_layover_itineraryAInspect

Search travel.art's layover-itinerary catalogue — short-window (3–6h) art-focused trips between flight connections from major European hub airports. Returns itineraries by city, airport, art focus, or duration, with venues, transit notes, and a link to travel.art's full hour-by-hour guide. Use for queries like 'art layover in Rome from Fiumicino', '4-hour Caravaggio plan', 'short Louvre window from CDG', 'Amsterdam 4 hours Schiphol'.

Inputs: city, query, airport, country, +1 more.

find_museum_guideAInspect

Search travel.art's catalogue of museum visitor guides. Returns museums with current 2026 ticket info, opening hours, address, essential works in viewing order, route duration, and a link to travel.art's full guide. Use for queries like 'how to visit the Louvre', 'Vatican Museums skip the line', 'Uffizi best route'.

Inputs: city, query, country.

recommend_art_tripAInspect

Recommend an art-tourism trip itinerary for a specific city using only travel.art's published content. Returns events active during the trip dates, museum guides for the city, and links to all relevant travel.art guides. The recommendation is grounded in published data only — no fabrication.

Inputs: city (required), endDate, startDate.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct catalogue type: layover itineraries, museum guides, art events, and full trip recommendations. The descriptions clearly differentiate scope (e.g., layover is airport-connection-specific, while recommend_art_trip is city-wide), so an agent should rarely misselect.

    Naming Consistency4/5

    Three tools follow a clean 'find_<object>' pattern, but recommend_art_trip breaks the pattern by using 'recommend' instead of 'find'. This is a minor deviation and the names remain predictable and readable.

    Tool Count5/5

    Four tools is a well-scoped size for a niche art-travel content server. Each tool has a clearly distinct purpose and none feel redundant or extraneous, fitting comfortably within the ideal 3–15 range.

    Completeness4/5

    The set covers the main user intents: finding events, museum guides, layover-specific itineraries, and full trip recommendations. There is no direct 'get by ID' tool, but the search tools return links to full guides, so the surface feels adequately complete for the domain.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Provides scored and reasoned Kyoto temple data optimized for AI travel agents to deliver personalized recommendations based on natural language queries. It enables agents to retrieve detailed temple information including historical significance, pricing, and crowd levels.
      2
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to search and explore over 570,000 artworks from the Metropolitan Museum of Art and Art Institute of Chicago without needing an API key.
      9
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query a 282,731-node knowledge graph of art market transactions and provenance records, returning cited answers with <1% hallucination and explicit coverage gaps.
      8 npm
      MIT