Tiqets MCP Server
在您的 Tiqets 账户上预订、获取和取消景点门票。
托管 MCP 服务器
npx add-mcp 'https://cotlet.dev/mcp/v1/tiqets'可安装到 Claude Code、Codex、Cursor 等客户端
文档
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
Tiqets API and MCP server: Let your AI agent sort out your Tiqets tickets.
Tiqets has no MCP server and no API for your own account (checked 27 Oct 2026). Its free Distributor API is built for travel agencies and gifting platforms, and its order list shows only orders that partner placed. Cotlet runs 9 Tiqets tools hosted, over MCP for agents and REST for scripts.
Book, fetch and cancel attraction tickets on your Tiqets account. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.
- Free 7-day trial, no card
- Unofficial, not affiliated with Tiqets
- Page: https://cotlet.dev/integrations/tiqets-api-mcp-server
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Tiqets. Tiqets is a trademark of its owner. If Tiqets's own integrations cover what you need, use them first.
What can you automate in Tiqets?
- Compare attractions in one city
- Check timeslots across several dates
- Prepare a checkout link you pay
- Track free cancellation deadlines
- Save the trip's e-tickets
- Move or cancel a visit
Does Tiqets have an MCP server or an API?
- A new partner key opens only the catalog and availability endpoints. The Booking API starts at "around 200 orders a month" and a screen-recorded demo.
- Expedia Group has owned Tiqets since early 2026. Its apps in ChatGPT and Claude cover hotels and flights, and its Rapid Activities API with Tiqets inventory is a beta for select partners.
- No webhooks and no Zapier or n8n app. Tiqets tells you about an order by email and text message.
| What you need | Distributor API | Apify scraper | Cotlet |
|---|---|---|---|
| Search attractions with prices | Yes, Content API | Public listings | Yes |
| Timeslots and day prices | Availability API | Listing data only | Yes, per date |
| Your own orders and e-tickets | Partner orders only | No | Yes |
| Reschedule or cancel your order | Partner orders only | No | Yes, after your OK |
| Book on your account | Books for the partner | No | Checkout link, you pay |
| What you need first | Partner signup, then 200 orders a month and a demo | An Apify account | A free Tiqets account |
Checked 27 Oct 2026. Sources: Tiqets API program for partners, Tiqets Distributor API: API keys, Tiqets Distributor API: list orders, Expedia TAAP launches beta Rapid Activities API (Travolution), Tiqets terms and conditions
How does Cotlet connect to Tiqets?
- Sign in to Tiqets. 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 keep your Tiqets password, the agent never pays, and no visit is moved or cancelled before you approve it.
Connect Tiqets 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.
- Open Tiqets in a Cloud Browser. Make a Cotlet account, sign in to the Tiqets account you book with in its Cloud Browser, then press Enable for agents.
- Add the Cotlet address. Paste https://cotlet.dev/mcp/v1 into the MCP server or connector field of your agent.
- Approve the link. Chat apps show a Cotlet sign-in page. Editors, n8n and scripts send an API key you create in the console.
https://cotlet.dev/mcp/v1 serves every app you enable on Cotlet, Tiqets too. Enabled Tiqets after you connected? Refresh the connector and its tools appear.
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: tiqets_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: tiqets_write
How to use the Tiqets REST API
Create your Cotlet API key
Create a Cotlet API key with access to Tiqets and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Connect Tiqets in Cotlet and enable it for agents. Account access: Your own Tiqets account (the account you booked with).
Make your first Tiqets API request
REST:
curl "https://cotlet.dev/api/v1/tiqets/bookings?when=all" \
-H "Authorization: Bearer $COTLET_API_KEY"
Read bookings and apply the operation limits
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": "tiqets",
"tool": "list_bookings",
"result": {
"bookings": [
{
"order_id": "71204583",
"product": "Sagrada Familia: Fast Track Ticket",
"visit_date": "2026-10-24",
"tickets": 2,
"status": "confirmed"
}
]
}
}
Lists the bookings of the signed-in account, soonest visit first. Use order_id in get_booking, download_tickets and cancel_booking.
Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.
Tiqets workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | One booking: tickets, price paid and whether it can be cancelled or rescheduled. Use get_booking in your configured travel brief. |
| Make | HTTP > Make a request | Download links for the e-tickets of one booking. Use download_tickets in your configured travel brief. |
| Python or Node.js | REST API | Product page: what is included, meeting point, instructions and cancellation terms. Use get_experience in your configured travel brief. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads Tiqets; 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.
Tiqets API endpoints and MCP tools
Attractions, dates and checkout
Prices can change by season, weekday and time of day, so check each date. A checkout link holds the order for 30 minutes once details are in; you pay on Tiqets.
- Search experiences (
search_experiences, read): Attractions, museums and tours on Tiqets by text and city, with price from. - Get experience (
get_experience, read): Product page: what is included, meeting point, instructions and cancellation terms. - Check availability (
check_availability, read): Ticket types, timeslots and prices for a product on a date. - Start checkout (
start_checkout, write): Fill the order and return the Tiqets checkout link. Nothing is charged until you pay there yourself.
Your orders and e-tickets
Orders stored in the Tiqets account you signed in with. Ticket links belong to you; do not forward them.
- List bookings (
list_bookings, read): Your bookings with product, visit date, tickets and status. - Get booking (
get_booking, read): One booking: tickets, price paid and whether it can be cancelled or rescheduled. - Download tickets (
download_tickets, read): Download links for the e-tickets of one booking.
Changes and cancellations
Reschedule only where Tiqets shows the option. Cancel works on whole orders with free cancellation, until 23:59 the day before in the venue's time zone.
- Reschedule booking (
reschedule_booking, write, asks first): Move a booking to another date or timeslot, where Tiqets offers rescheduling. - Cancel booking (
cancel_booking, write, asks first): Cancel a whole booking, where Tiqets allows it.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/tiqets-api-mcp-server#tools
Who can see my Tiqets session, and how do I revoke it?
- What we store. Your signed-in Tiqets profile, AES-256-GCM encrypted, in Finland. Not the password.
- What your agent gets. 9 Tiqets tools. No cookie, no card details.
- What the session sees. Your orders, visit dates, travel party names and ticket files.
- What no tool touches. Payment, saved cards, promo codes, reviews and account details.
- If Tiqets signs you out. We email you a link to sign in again. We never sign in for you.
- How to cut access. Disable Tiqets for agents, reset the browser or delete the key. The next call fails.
E-tickets carry barcodes that let anyone in, so download_tickets hands links only to your agent and never to a third party. The Cotlet site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Approvals, undo and mistakes
- Finds the trip's orders. Every order with a visit date inside the days you name.
- Reads each policy. Free to cancel, needs Tiqets support, or already cancelled.
- Waits for your OK. Each cancellation sits in your Cotlet console, earliest deadline first.
- Reports back. Refunds due, and a drafted note to Tiqets support for the rest.
| Action | Undo |
|---|---|
| Start a checkout | Nothing to undo; an unpaid order expires after 30 minutes with no charge |
| Reschedule a visit | Move it again if Tiqets still offers Reschedule; the old slot may be gone |
| Cancel an order | No, book again at today's price; the refund goes to the card you paid with |
2 of the 3 write tools ask first: reschedule_booking and cancel_booking. start_checkout runs at once because it charges nothing and nobody else sees it. Reads never wait. For a scheduled run you can switch the wait off per tool.
Tiqets cancels whole orders only. If one person of four drops out, the agent asks whether to cancel all and rebook three, and does neither on its own.
MCP call:
{
"name": "cancel_booking",
"arguments": {
"order_id": "71204583"
}
}
REST:
curl -X POST https://cotlet.dev/api/v1/tiqets/orders/71204583/booking/cancel \
-H "Authorization: Bearer $COTLET_API_KEY"
Response:
{
"order_id": "71204583",
"status": "cancelled",
"product": "Sagrada Familia: Fast Track Ticket",
"visit_date": "2026-10-24",
"refund": {
"amount": 66,
"currency": "EUR"
}
}
A trip planner script or a weekly cron job calls the same tools over REST at /api/v1/tiqets, with one key and one price. A cancel Tiqets refuses, for example past the deadline, returns an error and costs nothing. Each tool row above shows its REST path.
How much does the Tiqets MCP server cost?
About $12 a month for a month with one family city trip, 2,060 credits. Tickets are still paid on Tiqets, and a Tiqets account is free.
| Job | Calls | Credits |
|---|---|---|
| Compare 3 dates for one attraction | 5 × 4 | 200 |
| Checkout link for the slot you pick | 1 × 4 | 40 |
| Bookings and cancel deadlines, weekly | 5 × 4 | 200 |
| Save the e-tickets before you fly | 5 × 1 | 50 |
| Move one visit to another day | 5 × 1 | 50 |
| Cancel one visit in time | 2 × 1 | 20 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 2,060 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
The month is our example: a family of four, four attractions compared over three dates each, one visit moved and one cancelled. Tiqets publishes no tickets per order, so most months are quieter and the Cloud Browser is most of the bill. Dollars at the $29 pack rate.
Tiqets MCP server on GitHub, Apify or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| richardvenneman/tiqets | A Ruby wrapper for the partner API, MIT. 0 stars, last push 17 Aug 2018. | Needs a partner key, sees partner orders only, no MCP. |
| RobChooses/ex_tiqets | An Elixir wrapper for the same API, MIT. 0 stars, last push 13 Nov 2019. | Same limits, unmaintained. |
| Apify Tiqets Scraper | Titles, prices, ratings and images for a city, callable from Apify's MCP server. | Public listings, no sign-in; $0.002 a result plus $0.005 a run. |
| Expedia Rapid Activities API | Shopping and booking of Expedia activities, Tiqets included, for travel businesses. | Beta for select partners since 1 Oct 2026, general release planned for early 2027. |
A travel business that sells tickets should apply for the Tiqets partner API. For prices across many cities, a scraper costs less. If your agent should check dates, keep an eye on your own orders, and move or cancel them, Cotlet does that hosted.
Who runs Cotlet
Cotlet is run by Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273) and working since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Tiqets tools go to contact@cotlet.dev.
Tiqets API and MCP: questions
How do I get access?
Sign up free at https://cotlet.dev, open Tiqets under Integrations in the console and sign in to Tiqets in its Cloud Browser. The trial starts when you sign up and needs no card.
How do I connect Tiqets to ChatGPT or Claude?
Sign up at cotlet.dev, log in to Tiqets 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 Tiqets account through Cotlet, in their phone apps too.
What can ChatGPT do in Tiqets?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Tiqets: find attraction tickets for a date and timeslot; list upcoming bookings and cancellation deadlines; download e-tickets for a trip. You ask in plain words, and anything that reaches other people waits for your OK first.
Can my agent pay for tickets?
No. start_checkout returns the Tiqets checkout link and charges nothing; you pay on Tiqets yourself.
Does it see orders I placed without an account?
The tools read the orders stored in the Tiqets account you sign in with. Tiqets lets you order without an account, and the terms say an account is what stores "all Tickets purchased via us", so book while signed in if your agent should see the order.
Is Tiqets part of Expedia now?
Yes. Expedia Group announced the purchase on 10 Dec 2025 and closed it in early 2026. Expedia's apps in ChatGPT and Claude cover hotels and flights; none of them reads or changes your Tiqets orders.
Does Tiqets have webhooks?
Not for visitors. Tiqets sends order updates by email and text message. To react to changes, run your agent on a schedule with list_bookings.
Is the MCP server different from the REST API?
Only in how you call it. Both expose the same 9 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and cron jobs use REST.
Is Cotlet affiliated with Tiqets?
No. Cotlet is independent and not affiliated with Tiqets or Expedia Group.
Can I use the Tiqets 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.
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.