Travel Art MCP

What alexzavialov/travel-art-mcp MCP server does

The alexzavialov/travel-art-mcp MCP server makes travel.art’s art-tourism catalogue available to MCP-compatible agents. Its data covers major biennales, art fairs, festivals, museum visitor guides, and art-focused layover plans. Records include links back to the relevant travel.art guide, allowing an agent to provide a concise result while directing users to the fuller editorial material.

The catalogue includes events such as the Venice and Whitney Biennales, Art Basel editions, and Frieze fairs. Museum coverage includes institutions such as the Louvre, Vatican Museums, Uffizi, Prado, British Museum, MoMA, Rijksmuseum, and Tate Modern. The dataset also contains six European airport layover itineraries.

How it works

The hosted service is available at https://mcp.travel.art/. It accepts MCP Streamable HTTP requests using JSON-RPC 2.0 over HTTP POST. No account, token, or API key is required. A health endpoint is available at /health, and clients can request the tool list through the MCP protocol.

Four tools are exposed:

• find_art_events filters events by free-text query, country, event type, active date, start date, or end date. Results include dates, venues, ticket information, summaries, and guide URLs.
• find_museum_guide searches museum records by text, city, or country. Results can contain ticket details, opening hours, works in viewing order, route durations, and guide URLs.
• find_layover_itinerary finds three- to six-hour plans using query text, city, country, airport code, or a maximum duration. Results describe the art focus, venues, time budget, and practical constraints.
• recommend_art_trip combines events active during supplied dates with museum guides for a specified city.

The alexzavialov/travel-art-mcp MCP server relies on the catalogue published by travel.art rather than generating unsupported attractions or schedules. Each record includes a lastVerified date, which can help agents account for data freshness.

Setup and configuration

For the simplest setup, configure an MCP client with the hosted URL. Claude Desktop can use a server entry whose url is https://mcp.travel.art/. Cursor and other clients that support Streamable HTTP can point to the same endpoint.

A local stdio entry is also included in the repository. After cloning the project and installing its npm dependencies, run npm start; the project starts npx tsx src/stdio.ts. Claude Desktop can launch that local process with npx and the arguments tsx src/stdio.ts. The local and hosted entries share the tool definitions and catalogue.

Developers can deploy a copy with Cloudflare Workers using the repository’s Wrangler configuration. A Cloudflare account is required for that deployment, while the hosted public endpoint does not require a Cloudflare account.

Limitations and notes

The catalogue is hand-curated and limited to content published by travel.art. It is not presented as a general-purpose travel database. Coverage changes as new editorial guides are added, and the README lists the catalogue as growing weekly.

Event and museum results may include current-year ticket information, opening hours, booking rules, closure warnings, and transit calculations, but agents should still use the returned guide URLs and verify time-sensitive details before making final travel arrangements. The server exposes data and recommendations; it does not book tickets or provide an authenticated booking integration.

The project is released under the MIT license. Its source separates the hosted worker, local stdio entry point, shared tool handlers, and static dataset, so operators can inspect or deploy their own copy.