Civitatis MCP Server
Bookings, availability and tours for Civitatis activity suppliers.
Hosted MCP Server
npx add-mcp 'https://cotlet.dev/mcp/v1/civitatis'Installs into Claude Code, Codex, Cursor and more
Documentation
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
Civitatis API and MCP server: Let your AI agent run your Civitatis provider panel.
Civitatis has no MCP server and no API a supplier can call to read or change its provider panel (checked 24 Oct 2026). Its supply API works the other way: Civitatis calls your booking system. Cotlet runs 13 Civitatis tools hosted, over MCP for agents and REST for scripts.
Connect Civitatis provider activities, bookings and availability to your operations workflow. Use an AI agent through MCP or REST from automation tools and scripts.
- Free 7-day trial, no card
- Unofficial, not affiliated with Civitatis
- Page: https://cotlet.dev/integrations/civitatis-api-mcp-server
What can you automate in Civitatis?
- Close dates when a guide is off
- Cap places per start time
- Send guides tomorrow's bookings
- Answer traveler messages
- Request the monthly payment
- Sum up reviews per activity
Does Civitatis have an MCP server or an API?
- The Connected API on connectivity.civitatis.com has 8 endpoints your system builds on the OCTO pattern: products, availability, create, confirm and cancel bookings. Civitatis certifies and validates each one before your products go live.
- The easy route is a channel manager. Bókun, FareHarbor, Ventrata, Palisis and TuriTop are the "Golden" partners, with 30+ more listed. They push availability in and pull bookings out.
- Neither route has messages, reviews, invoices or the monthly payment request. No Zapier or n8n app exists, and Civitatis points smaller operators to "manual management from our extranet".
| What you need | Channel manager | Email parser (GitHub) | Cotlet |
|---|---|---|---|
| Close dates and set quotas | Yes, in its own calendar | No | Yes, in the panel |
| Tomorrow's bookings per start time | Yes | From booking emails | Yes |
| Messages with travelers and the booking department | No | No | Yes, sends after your OK |
| Reviews, invoices, payment request | No | No | Yes |
| Keeps your calendar where it is | You move it in | Yes | Yes |
| Fixed for you when Civitatis changes | Yes, by the vendor | No | Yes, tested every 12 h |
Checked 24 Oct 2026. Sources: Civitatis Partners portal: supply, Civitatis Connected API documentation, Civitatis provider FAQs, Bókun: becoming a Civitatis supplier
How does Cotlet connect to Civitatis?
- Sign in to Civitatis. Use your own account in its Cotlet Cloud Browser.
- Choose MCP or REST. Connect your agent or create a Cotlet API key.
- Run your workflow. Ask your agent or send an HTTP request.
We never save your panel password, and messages and payment requests wait for your OK.
Connect Civitatis to your agent or workflow
Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.
- Enable Civitatis for agents. Sign up, log in to your Civitatis provider panel in its Cloud Browser, then press Enable for agents.
- Add the Cotlet address. Put https://cotlet.dev/mcp/v1 in the MCP or connector settings of your agent.
- Sign in or paste a key. Chat apps sign you in to Cotlet; editors and scripts take an API key from the console.
One address serves all the apps you enable. Enable Civitatis after you connect, and a refresh of the connector brings its tools in.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY"
ChatGPT:
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Cursor:
// ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n:
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: civitatis_read
Make, Zapier:
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: civitatis_write
How to use the Civitatis REST API
Create your Cotlet API key
Sign in to Civitatis in its Cotlet Cloud Browser and enable the app for agents. Use your Civitatis provider panel login.
Create a Cotlet API key with access to Civitatis and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Make your first Civitatis API request
cURL: list_activities:
curl https://cotlet.dev/api/v1/civitatis/activities \
-H "Authorization: Bearer $COTLET_API_KEY"
Read activities before booking reports
A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.
Illustrative response excerpt:
{
"status": "success",
"app": "civitatis",
"tool": "list_activities",
"result": {
"activities": [
{
"activity_id": "act_48213",
"name": "Bike tour of the old town",
"destination": "Madrid",
"status": "active"
}
]
}
}
Read result.activities and use the returned IDs for booking and availability reads. The activity list has no pagination input.
Booking reads use activity dates, defaulting to today through seven days ahead and confirmed bookings. Use status=all to include cancelled bookings and pass returned cursors until null; no page-size input is available.
Invoices and payments accept a year, defaulting to the current year. Preserve currency and booking IDs in reconciliation reports; reviews are read only.
Civitatis workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Read activities, bookings and booking details into a departure manifest grouped by date and time. |
| Make | HTTP > Make a request | Read unread messages with booking context into a customer-question review queue without replying. |
| Python or Node.js | REST API | Combine yearly invoices and payments into a settlement report that preserves booking references and currency. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads Civitatis; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.
Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.
The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.
Civitatis API endpoints and MCP tools
Activities, dates and quotas
Closing a date stops new sales only; bookings already made stay. A quota counts per start time, not per day. If you also run a channel manager, change dates in one place.
- List activities (
list_activities, read): Your activities on Civitatis with destination and status. - Get availability (
get_availability, read): Calendar of an activity: open and closed dates and the quota per day and time. - Close dates (
close_dates, write): Stop sales of an activity on a date range, all day or for chosen times. - Open dates (
open_dates, write): Reopen sales of an activity on dates you closed before. - Set quota (
set_quota, write): Limit the places sold for an activity on given days and times.
Bookings
By activity date, not by booking date. Travelers call the phone number on their voucher, so late groups ring you.
- List bookings (
list_bookings, read): Bookings by activity date, with activity, time, number of people and status. - Get booking (
get_booking, read): One booking: reference, activity, date and time, people, price and lead traveler contact.
Messages and reviews
One thread per booking, with the traveler or with the Civitatis booking department. Reviews can be read, not answered.
- List messages (
list_messages, read): Messages with customers and the Civitatis booking department, newest first. - Send message (
send_message, write, asks first): Write to a customer about a booking, or to the Civitatis booking department. - List reviews (
list_reviews, read): Customer reviews of your activities with rating, text and date.
Settlements, payouts and invoices
Civitatis pays nothing until you request it, from the 1st of the month for the month before. Invoices are for its commission.
- List payments (
list_payments, read): Monthly settlements: services rendered, commission, net amount and payment status. - Request payment (
request_payment, write, asks first): Request payment for services rendered in the previous month, net of commission. - List invoices (
list_invoices, read): Commission invoices from Civitatis with period, amount and a download link.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/civitatis-api-mcp-server#tools
Who can see my Civitatis session, and how do I revoke it?
- What we store. Your signed-in provider panel, AES-256-GCM, in Finland. Never the password.
- What your agent gets. The 13 Civitatis tools. No cookie, no panel login.
- What the session sees. What your panel login sees: bookings, lead travelers' phones, messages, settlements.
- What no tool touches. Listings, prices, photos, bank details and panel users.
- If Civitatis logs you out. You get an email with a sign-in link. We never log in for you.
- How to cut access. Disable Civitatis for agents, reset its browser or delete the key.
Traveler details from get_booking go only to the agent that asked and are not kept by Cotlet. A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results). No SOC 2 report or third-party pentest yet.
Is it against Civitatis's terms? Account safety
CIVITATIS reserves the right to deny any attempt to access the Website and/or App or to terminate user accounts in cases where the Website and/or App is used improperly, in accordance with the provisions of this clause.
Those are the website terms. They do not mention bots, scraping or automated access, and a closed account gets the reasons and six months to appeal. Suppliers also accept "general collaboration conditions" at sign-up, which Civitatis does not publish, so read your copy. We found no public case of a supplier removed for automation (checked 24 Oct 2026).
How we keep your panel looking like you:
- Your own provider login, signed in by you
- One Cloud Browser with its own IP and cookies
- Messages and payment requests wait for your OK
- No listing, price or bank detail edits
- Sign-in and 2FA stay with you; we never bypass MFA
- If Civitatis objects, Civitatis tools pause for everyone within 24 h
Civitatis picks the main supplier of an activity with a score that weighs availability, among other things, so close only the slots nobody can run.
What happens when Civitatis changes?
- 12 h between tests of the Civitatis tools
- $0 for calls to a tool paused for a fix
The provider panel is the only place messages, reviews and payouts exist, so a panel change is ours to fix, not yours. status.cotlet.dev checks the site, console and API every 3 minutes.
Approvals, undo and mistakes
- Reads last month. The settlement: services, commission, net.
- Checks it against bookings. Confirmed and cancelled, and stops on a gap.
- Waits for your OK. The request shows up in your Cotlet console.
- Hands over the invoice. With the expected Tuesday payout date.
| Action | Undo |
|---|---|
| Close dates | Yes, open_dates for the same days and times |
| Set a quota | Yes, set the old number again |
| Send a message | No, the traveler or the booking department has it |
| Request a payment | No, it joins the next Tuesday's payout |
2 of 13 tools ask first: messages and payment requests. Closing, opening and quotas run at once, because they reach no one and undo in one call. A quota below the people already booked stops the agent, which asks you first.
MCP call:
{
"name": "close_dates",
"arguments": {
"activity_id": "act_48213",
"from": "2026-10-20",
"to": "2026-10-22",
"times": [
"10:00",
"16:00"
]
}
}
REST:
curl -X POST https://cotlet.dev/api/v1/civitatis/activities/act_48213/dates/close \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"from":"2026-10-20","to":"2026-10-22","times":["10:00","16:00"]}'
Tool output:
{
"activity_id": "act_48213",
"activity": "Bike tour of the old town",
"closed": [
{
"date": "2026-10-20",
"times": [
"10:00",
"16:00"
]
},
{
"date": "2026-10-21",
"times": [
"10:00",
"16:00"
]
},
{
"date": "2026-10-22",
"times": [
"10:00",
"16:00"
]
}
],
"bookings_on_closed_slots": 0
}
Scripts and cron jobs reach the same tools over REST under /api/v1/civitatis. A call that fails uses no credits. The tools table lists the REST path of each tool.
How much does the Civitatis MCP server cost?
About $29 a month for a supplier with 3 activities and about 60 bookings a month, 5,070 credits. The Civitatis commission stays as agreed.
| Job | Calls | Credits |
|---|---|---|
| Tomorrow's list for the guides, daily | 6 × 30 | 1,800 |
| Answer traveler messages, daily | 5 × 30 | 1,500 |
| Close dates for a guide who is off, then reopen | 7 × 2 | 140 |
| Request the monthly payment, fetch the invoice | 5 × 1 | 50 |
| Review summary per activity, weekly | 2 × 4 | 80 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 5,070 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- No booking fee on top of the Civitatis commission
The supplier size is our assumption. Civitatis counts over 10 million travelers a year across 4,000+ operators, about 200 travelers a month each on average, and big operators pull that up. A channel manager such as Bókun starts at $49 a month plus 1.5% per booking. Dollars at the $29 pack rate.
Civitatis MCP server, channel manager or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| Bókun and other channel managers | Bókun pulls in your Civitatis bookings and sends real-time availability back. FareHarbor, Ventrata, Palisis and TuriTop connect the same way. | No messages, reviews or payouts; Bókun from $49 a month plus 1.5%. |
| Your own Connected API | The same sync without a vendor: you build 8 endpoints on the OCTO pattern. | Developers, an OCTO certificate and Civitatis validation first. |
| GitHub | No Civitatis MCP server. Two email parsers turn booking emails into sales records (0 stars, no license). | Read only, one booking per email, nothing from the panel. |
| Apify scrapers | Three actors read public tours, prices and reviews. | No sign-in, so none of your own bookings or messages. |
Already on a booking system? Keep it for the calendar and add Cotlet for messages, reviews and payouts. Selling only on Civitatis from the panel? Cotlet covers dates and bookings too, without moving your calendar.
Who runs Cotlet
Cotlet belongs to Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Civitatis tools go to contact@cotlet.dev.
Civitatis API and MCP: questions
Can I use the Civitatis API without an AI agent?
Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.
How do I get access?
Sign up free at https://cotlet.dev, open Civitatis under Integrations in the console and log in to your provider panel in its Cloud Browser. Your free trial starts when you sign up, no card needed.
How do I connect Civitatis to ChatGPT or Claude?
Sign up at cotlet.dev, log in to Civitatis once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Civitatis account through Cotlet, in their phone apps too.
What can ChatGPT do in Civitatis?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Civitatis: close tour dates or cut places when a guide is unavailable; limit places per day and time; answer customer messages before the tour. You ask in plain words, and anything that reaches other people waits for your OK first.
When can I request my payment?
Per the Civitatis provider FAQ, from the first day of each month you can request payment for the previous month. Requests made Monday to Sunday are paid the following Tuesday, except Madrid public holidays.
Do I need a booking system or a channel manager?
No. Cotlet works in the provider panel, the same place Civitatis points smaller operators to. If you already sync through Bókun or FareHarbor, keep that for the calendar and change dates in one place only, so the two do not overwrite each other.
Is this for travelers who book on Civitatis?
No. The 13 tools are for activity suppliers who sell on Civitatis and log in to its provider panel. Travelers have no panel to connect.
Does Civitatis send webhooks?
Only to a connected booking system, for new and confirmed bookings. A panel-only supplier gets one email per booking. To react to bookings or messages, run your agent on a schedule with list_bookings or list_messages.
Is the MCP server different from the REST API?
Only the way in. Both have the same 13 tools, inputs and answers, one API key and one price. Agents use MCP; scripts, cron jobs and HTTP steps use REST.
Is Cotlet affiliated with Civitatis?
No. Cotlet is independent and not affiliated with Civitatis.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.