Civitatis MCP server icon

Civitatis

by Civitatis

Travel7 toolsNo Auth Required

Search tours and activities worldwide, check live availability and build a day-by-day itinerary from your AI agent. 7 tools, no sign-in, checkout stays on civitatis.com.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Civitatis via MCP

https://civitatis-claude-app.civitatis.com/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Civitatis Tools & Capabilities (7)

search-activitiesRead-only

Browse activities for a destination — shows a visual carousel widget for open-ended discovery. Use ONLY when the user just wants to see what there is, and no activities are visible yet. DO NOT use this for itinerary or multi-day plan requests — for those call suggest-itinerary directly. To look up activityIds WITHOUT a widget, use list-activities.

list-activitiesRead-only

Look up activities (with numeric IDs) for a destination as PLAIN TEXT, without showing any widget. Use this to obtain activityIds before suggest-itinerary, get-activity-detail or check-availability when you don't already have them. Returns a text list of 'title (activityId=NNN)'.

get-activity-detailRead-only

Get full details of a specific activity: images, long description, highlights, cancellation policy, reviews, and price. Use it whenever the user asks for more info, details, description or highlights of a specific activity, including activities already mentioned earlier in the conversation — catalog data such as prices and policies changes over time, so fresh details come from this tool and are presented in its detail widget. Requires the NUMERIC activityId (e.g. 12345); look it up with list-activities if you only have a name.

check-availabilityRead-only

Check available time slots for a specific activity on a given date. Call this INSTEAD OF search-activities when the user asks about availability, dates, or schedules for an activity already shown in the conversation. Requires activityId from prior search results.

add-to-cartActs

Add an activity session to the cart and get a checkout URL. Call this when the user wants to book or reserve an activity. Requires activityId, date, time, modalityId, and ticketTypeId from check-availability results. To add another item to the SAME cart, pass both cartId AND cartToken exactly as returned by the previous add-to-cart call — cartId alone is rejected.

check-availability-batchRead-only

Check availability for MULTIPLE activities on the same date in one call. Use this when the user asks which of several activities are available on a specific date. More efficient than calling check-availability multiple times.

suggest-itineraryRead-only

Display a multi-day activity itinerary plan. Use this whenever the user asks for an itinerary, a plan, or a multi-day schedule for a destination (NOT search-activities). Call it DIRECTLY with destination, startDate, days and travelers — the server automatically picks the destination's top activities and distributes them across the days. Only pass `plan` when the user asked for SPECIFIC activities (get their numeric activityIds from list-activities first; NEVER invent activityIds).

Read from the server on 2026-08-16, including each tool's own safety annotations.

Limits

  • It cannot complete a purchase. Civitatis's documentation is explicit that the connector never processes payments; the cart returns a checkout link and the traveller pays on civitatis.com.
  • It defaults to Spanish. The server's own instructions say an omitted locale returns Spanish content. A client that never sends lang will answer in the wrong language.
  • One widget per response. The server instructs agents that a response may show at most one visual widget, so search-activities, availability and itinerary views cannot be combined in a single turn.
  • Activity IDs must be looked up, not guessed. suggest-itinerary warns agents never to invent activity IDs; they come from list-activities.
  • Prices and policies are point-in-time. get-activity-detail exists because catalogue data changes, so a price quoted earlier in a conversation may be stale.
  • The documentation is thin. Civitatis's public doc is a single page with no troubleshooting section, no stated rate limits and no plan gates, so none are claimed here.
  • We did not exercise any tool. Our check was a read-only initialize and tools/list handshake. Behaviour above comes from the server's own tool descriptions and Civitatis's documentation, not from calling anything.

Frequently asked questions

Can the Civitatis connector book and pay for a tour for you?

No. Civitatis states the connector never processes payments directly. The add-to-cart tool builds a cart and returns a checkout URL, and the traveller finishes the purchase on civitatis.com through Civitatis's own checkout. So the agent can assemble a booking, but a person still completes payment outside the conversation.

Do you need a Civitatis account to use the MCP server?

No. We opened an anonymous connection to the endpoint on 2026-08-16 and the server completed the handshake and returned all seven tools without any credential. Anthropic's directory also lists the server as authless. Browsing, availability checks and cart creation therefore work before anyone signs in to Civitatis.

Which languages and currencies does the Civitatis connector support?

Spanish, English, French, Italian and Portuguese, priced in EUR, USD or GBP, per Civitatis's connector documentation. The live tool schemas list the locale codes accepted: en_US, es_AR, es_ES, es_MX, fr_FR, it_IT, pt_BR and pt_PT. Both the language and the currency default to Spanish and EUR when the agent omits them.

Which Civitatis tools can change something?

One of the seven. The server annotates add-to-cart as not read-only, and does not annotate it destructive. It creates a cart and returns a checkout link. The other six carry a read-only hint and only fetch catalogue, availability or itinerary data, so they cannot alter anything at Civitatis.

Why does the Civitatis connector answer in Spanish?

Because the language parameter was left out. The server's own instructions state that it defaults to Spanish, so an omitted locale returns Spanish titles, categories and descriptions even in an English conversation. The fix is for the client to pass the lang parameter on every call, which the server instructs agents to do.

Sources

Use in Agentman

Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

Server Info

Category
Travel
Developer
Civitatis
Tools
7
Domain
civitatis-claude-app.civitatis.com

Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.