[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Tripleseat API and MCP server

> Tripleseat has a full REST API with an OpenAPI spec, but no official MCP server (checked 17 Oct 2026). The API covers leads, events, bookings, contacts, accounts, rooms and tasks. It authenticates with OAuth 2.0 only since OAuth 1.0 shut down on 1 July 2026, so you register an OAuth app in Settings > Tripleseat API & Webhooks, have a customer admin authorize it, and refresh the token every 2 hours.

Event and venue management software for restaurants, hotels and event spaces: leads from web forms, a booking calendar, proposals and contracts, payments and reports in one account.

## What is the Tripleseat API?

Cotlet's Tripleseat API exposes 15 endpoints for your own Tripleseat account: list leads, get lead, list events, get event, list bookings, get booking, list rooms, check room availability, search contacts and accounts, create lead, convert lead, turn down lead, create event, set event status and create task. The list_leads endpoint returns leads from your lead forms and manual entry, filtered by Conversion Status. Each endpoint takes simple JSON inputs like location_id, status or cursor and works both as an operation of the tripleseat_read or tripleseat_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Local services & SaaS](https://cotlet.dev/integrations/category/local-services-saas.md)
- **Endpoints:** 15 (9 read, 6 write)
- **Updated:** 2026-10-21

Tripleseat has a full REST API with an OpenAPI spec, but no official MCP server (checked 17 Oct 2026). Cotlet is a hosted MCP server and REST API for Tripleseat with 15 endpoints (9 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Tripleseat have an official API?

Tripleseat has a full REST API with an OpenAPI spec, but no official MCP server (checked 17 Oct 2026). The API covers leads, events, bookings, contacts, accounts, rooms and tasks. It authenticates with OAuth 2.0 only since OAuth 1.0 shut down on 1 July 2026, so you register an OAuth app in Settings > Tripleseat API & Webhooks, have a customer admin authorize it, and refresh the token every 2 hours.

| Task | Tripleseat official | Cotlet |
|---|---|---|
| List and read leads | Yes: Leads endpoints; you build OAuth, paging and the agent tool layer | Yes |
| Create a lead | Yes: Leads endpoint, public key or OAuth token | Yes |
| Convert a lead to an event, booking or contact, or turn it down | No: The spec has no endpoint; webhooks only report the conversion after you click | Yes |
| Search events and bookings by date, status and room | Yes: Search endpoints, 50 results per page | Yes |
| Check whether a room is free | Partly: Search events by room and date range; the spec lists no calendar notes that block a room | Yes |
| Create an event | Yes: Events endpoint; an event needs an account and a contact | Yes |
| Change an event status | Yes: Status is a field on the event update | Yes |
| Create a follow-up task | Yes: Task endpoint on leads, events, bookings, contacts and accounts | Yes |

Sources: [Tripleseat Help: API Overview & Resources](https://support.tripleseat.com/hc/en-us/articles/41942861771543-API-Overview-Resources), [Tripleseat Help: OAuth 2.0 Implementation](https://support.tripleseat.com/hc/en-us/articles/40652011678231-OAuth-2-0-Implementation), [Tripleseat Help: OAuth 1.0 to OAuth 2.0 Migration Guide](https://support.tripleseat.com/hc/en-us/articles/35211389645079-OAuth-1-0-to-OAuth-2-0-Migration-Guide-for-Tripleseat-API), [Tripleseat API OpenAPI specification](https://api.tripleseat.com/api-docs/v1/openapi.yaml)

## For AI agents

```text
Tripleseat has a full REST API with an OpenAPI spec, but no official MCP server (checked 17 Oct 2026). The API covers leads, events, bookings, contacts, accounts, rooms and tasks. It authenticates with OAuth 2.0 only since OAuth 1.0 shut down on 1 July 2026, so you register an OAuth app in Settings > Tripleseat API & Webhooks, have a customer admin authorize it, and refresh the token every 2 hours.
Cotlet provides a hosted MCP server and REST API for Tripleseat: 15 tools (9 read, 6 write).
Access       Sign up at https://cotlet.dev/app/signup?app=tripleseat, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    tripleseat_read, tripleseat_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/tripleseat, each operation at its own route, e.g. POST /api/v1/tripleseat/leads
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_leads, get_lead, list_events, get_event, list_bookings, get_booking, list_rooms, check_room_availability, search_contacts, create_lead, convert_lead, turn_down_lead, create_event, set_event_status, create_task
Confirm      create_lead, convert_lead, turn_down_lead, create_event, set_event_status, create_task (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/tripleseat-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=tripleseat, requests Tripleseat in the Cotlet console and creates an API key there.
2. The user signs in to Tripleseat once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Tripleseat for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Tripleseat server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Tripleseat MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Tripleseat in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Tripleseat only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Tripleseat login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Tripleseat's terms; Cotlet is not affiliated with Tripleseat.
```

## What can an AI agent do in Tripleseat?

Cotlet is best for venue sales managers and event coordinators who want an AI agent to work leads, holds and event statuses in Tripleseat without running or fixing a server.

- **[Convert qualified leads to prospect events](https://cotlet.dev/integrations/tripleseat-api-mcp-server/convert-leads-to-bookings.md)** (runs: daily): "Go through Tripleseat leads that are not converted yet. If the date is free in the room they asked for, convert the lead to a Prospect event. Turn down anything outside our capacity and leave the rest for me with a one-line reason." → `list_leads`, `get_lead`, `check_room_availability`, `convert_lead`, `turn_down_lead`
- **[Close finished events](https://cotlet.dev/integrations/tripleseat-api-mcp-server/close-finished-events.md)** (runs: weekly): "List Tripleseat events with status Definite whose date has passed. For each one with nothing due, show me the amount due and, once I say so, change the status to Closed." → `list_events`, `get_event`, `set_event_status`
- **[Follow up on tentative events](https://cotlet.dev/integrations/tripleseat-api-mcp-server/follow-up-tentative-events.md)** (runs: weekly): "List Tripleseat events that have been Tentative for more than 7 days. Create a high-priority follow-up task for the event owner to chase the signed contract and deposit, and list the ones within 14 days of the event date for me." → `list_events`, `get_event`, `create_task`, `set_event_status`
- **Check whether a date is free for an inquiry**: "A guest wants the Garden Room on Saturday 28 November from 18:00 to 23:00 for 40 people. Tell me whether it is free and which events are in the way." → `list_rooms`, `check_room_availability`, `list_events`
- **Summarize the event pipeline** (runs: weekly): "Every Monday, list Tripleseat events for the next 30 days by status, with guest counts, and show Prospect and Tentative events I still need to move forward." → `list_events`, `list_bookings`
- **Add leads from email or a spreadsheet**: "Take the inquiries in this spreadsheet and add each as a lead in Tripleseat. Skip anyone who already exists as a contact." → `search_contacts`, `create_lead`

## Can Tripleseat automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Tripleseat connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to convert qualified leads to prospect events, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/tripleseat/leads. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/tripleseat/leads with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 15 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Tripleseat.

### list_leads

Leads from your lead forms and manual entry, filtered by Conversion Status. Access: read. REST: `GET /api/v1/tripleseat/leads`. MCP: `tripleseat_read → list_leads`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversion_status` | string | no | Not Converted, Converted to Bookings/Events, Converted to Contacts or Turned Down. Default: Not Converted. |
| `created_after` | date | no | Only leads created after this date. |
| `location_id` | integer | no | Only this location. Needed if your account has more than one. |
| `limit` | integer | no | 1 to 50. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists leads with the guest, requested date, room preference and guest count. Filter by Conversion Status, the same filter as on the Leads page: Not Converted, Converted to Bookings/Events, Converted to Contacts or Turned Down. Each lead carries created_at, so your agent can sort by age. Pass lead_id to get_lead for the full request.

Example response:

```json
{
  "leads": [
    {
      "lead_id": 90412,
      "name": "Ife Okafor",
      "company": null,
      "event_description": "Birthday dinner for my sister",
      "event_date": "2026-11-14",
      "guest_count": 28,
      "location": "Harbor House",
      "conversion_status": "Not Converted",
      "created_at": "2026-10-16T21:12:00-04:00"
    }
  ],
  "next_cursor": null
}
```

### get_lead

One lead with the full request, contact details and lead source. Access: read. REST: `GET /api/v1/tripleseat/leads/{lead_id}`. MCP: `tripleseat_read → get_lead`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `lead_id` | integer | yes | Lead ID from list_leads. |

Returns the guest name, email, phone, company, event description, date, start and end time, guest count, contact preference, additional information, lead form and lead source. Use it before converting so your agent applies your rule to the whole request.

Example response:

```json
{
  "lead_id": 90412,
  "name": "Ife Okafor",
  "email_address": "ife@example.com",
  "phone_number": "555-0114",
  "event_description": "Birthday dinner for my sister",
  "event_date": "2026-11-14",
  "start_time": "18:30",
  "end_time": "22:30",
  "guest_count": 28,
  "contact_preference": "Email",
  "additional_information": "Two guests are vegetarian.",
  "lead_source": "Website",
  "location": "Harbor House",
  "created_at": "2026-10-16T21:12:00-04:00"
}
```

### list_events

Events by status, date range, room or location, with guest count and amount due. Access: read. REST: `GET /api/v1/tripleseat/events`. MCP: `tripleseat_read → list_events`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | Prospect, Tentative, Definite, Closed or Lost. |
| `date_from` | date | no | Events that touch this date or later. |
| `date_to` | date | no | Events that touch this date or earlier. |
| `room_id` | integer | no | Only events in this room, from list_rooms. |
| `location_id` | integer | no | Only this location. Needed if your account has more than one. |
| `limit` | integer | no | 1 to 50. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists events that overlap your date range, each with name, status, room, date, times, owner, contact and guest count, plus the grand total and amount due. Filter by one status: Prospect, Tentative, Definite, Closed or Lost. Results come 50 per page; use the cursor for the rest. Pass event_id to get_event for the full record.

Example response:

```json
{
  "events": [
    {
      "event_id": 5528840,
      "name": "Alvarez rehearsal dinner",
      "status": "Definite",
      "event_date": "2026-10-09",
      "start": "18:00",
      "end": "22:00",
      "room": "Garden Room",
      "owner": "Sam Reyes",
      "guest_count": 36,
      "grand_total": 4280,
      "amount_due": 0
    }
  ],
  "next_cursor": null
}
```

### get_event

One event with its booking, rooms, contact, guest count and financials. Access: read. REST: `GET /api/v1/tripleseat/events/{event_id}`. MCP: `tripleseat_read → get_event`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | integer | yes | Event ID from list_events. |

Returns the event name, status, booking, rooms, date and times including setup and teardown, account, contact, owner, guest counts and the money fields: food and beverage minimum, rental fee, deposit, grand total and amount due. A Lost event also returns its lost reason.

Example response:

```json
{
  "event_id": 5529012,
  "name": "Delgado rehearsal dinner",
  "status": "Tentative",
  "booking_id": 770231,
  "event_date": "2026-11-21",
  "start": "18:00",
  "end": "22:00",
  "rooms": [
    "Garden Room"
  ],
  "account": "Delgado family",
  "contact": "Marisol Delgado",
  "owner": "Sam Reyes",
  "guest_count": 40,
  "food_and_beverage_min": 2500,
  "rental_fee": 600,
  "deposit_amount": 1000,
  "grand_total": 4150,
  "amount_due": 4150,
  "updated_at": "2026-10-08T15:20:00-04:00"
}
```

### list_bookings

Bookings with their events, filtered by status and date. Access: read. REST: `GET /api/v1/tripleseat/bookings`. MCP: `tripleseat_read → list_bookings`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | Prospect, Tentative, Definite, Closed or Lost. |
| `starts_after` | date | no | Bookings starting on or after this date. |
| `ends_before` | date | no | Bookings ending on or before this date. |
| `location_id` | integer | no | Only this location. Needed if your account has more than one. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists bookings, the umbrella over one or more events such as a wedding with a rehearsal dinner, ceremony and reception. Each row has the status, start and end date, contact, account and its events. Filter by status or by the dates the booking starts and ends. Use get_booking for the full record.

Example response:

```json
{
  "bookings": [
    {
      "booking_id": 770231,
      "name": "Delgado wedding weekend",
      "status": "Tentative",
      "start_date": "2026-11-21",
      "end_date": "2026-11-22",
      "contact": "Marisol Delgado",
      "events": 2
    }
  ],
  "next_cursor": null
}
```

### get_booking

One booking with its events, contact, account and lead. Access: read. REST: `GET /api/v1/tripleseat/bookings/{booking_id}`. MCP: `tripleseat_read → get_booking`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `booking_id` | integer | yes | Booking ID from list_bookings. |

Returns the booking status, dates, contact, account, owner, every event inside it with its own status, and the lead it came from if there is one. The booking status and its events can differ, for example a Definite booking with one Tentative event.

Example response:

```json
{
  "booking_id": 770231,
  "name": "Delgado wedding weekend",
  "status": "Tentative",
  "start_date": "2026-11-21",
  "end_date": "2026-11-22",
  "contact": "Marisol Delgado",
  "account": "Delgado family",
  "owner": "Sam Reyes",
  "events": [
    {
      "event_id": 5529012,
      "name": "Delgado rehearsal dinner",
      "status": "Tentative"
    },
    {
      "event_id": 5529013,
      "name": "Delgado ceremony and reception",
      "status": "Tentative"
    }
  ],
  "lead_id": null
}
```

### list_rooms

Rooms in each location, with the room IDs other tools need. Access: read. REST: `GET /api/v1/tripleseat/rooms`. MCP: `tripleseat_read → list_rooms`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `location_id` | integer | no | Only this location. Needed if your account has more than one. |

Lists the rooms (event spaces) of your locations with room_id, name and location. Use room_id in list_events, check_room_availability and convert_lead. Your account may have several locations; pass location_id to see one.

Example response:

```json
{
  "rooms": [
    {
      "room_id": 3301,
      "name": "Garden Room",
      "location": "Harbor House"
    },
    {
      "room_id": 3302,
      "name": "Loft",
      "location": "Harbor House"
    }
  ]
}
```

### check_room_availability

Events and calendar blocks that are in the way of a room on a date and time. Access: read. REST: `GET /api/v1/tripleseat/rooms/{room_id}/availability/check`. MCP: `tripleseat_read → check_room_availability`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `room_id` | integer | yes | Room ID from list_rooms. |
| `date` | date | yes | Event date. |
| `start_time` | string | no | Start, for example 18:00. Default: whole day. |
| `end_time` | string | no | End, for example 23:00. Default: whole day. |

Returns the events that overlap the room, date and time you ask about, each with its status, and any calendar note set to prevent bookings. Tentative and Definite events hold the room; Prospect events can overlap each other, so they are listed as soft conflicts. Empty lists mean the room is free.

Example response:

```json
{
  "room": "Garden Room",
  "date": "2026-11-28",
  "hard_conflicts": [
    {
      "event_id": 5530018,
      "name": "Martin engagement party",
      "status": "Tentative",
      "start": "17:00",
      "end": "22:00"
    }
  ],
  "soft_conflicts": [
    {
      "event_id": 5530201,
      "name": "Reyes dinner inquiry",
      "status": "Prospect",
      "start": "18:00",
      "end": "21:00"
    }
  ],
  "blocking_notes": []
}
```

### search_contacts

Contacts and accounts by name, email or company. Access: read. REST: `GET /api/v1/tripleseat/contacts/search`. MCP: `tripleseat_read → search_contacts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | yes | Name, email or company. |
| `type` | string | no | contact or account. Default: both. |
| `cursor` | string | no | Next page cursor from the previous call. |

Searches your contacts, the people, and your accounts, the companies or families they belong to. Each hit returns the IDs that create_event needs and the owner. Use it before create_lead to see whether the guest is already known.

Example response:

```json
{
  "results": [
    {
      "type": "contact",
      "contact_id": 66120,
      "name": "Marisol Delgado",
      "email_address": "marisol@example.com",
      "account": "Delgado family",
      "account_id": 4410
    }
  ],
  "next_cursor": null
}
```

### create_lead

Add an inquiry to Leads with the guest, date, guest count and request. Access: write, asks the user first. REST: `POST /api/v1/tripleseat/leads`. MCP: `tripleseat_write → create_lead`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `first_name` | string | yes | Guest first name. |
| `last_name` | string | yes | Guest last name. |
| `email_address` | string | yes | Guest email. |
| `phone_number` | string | no | Guest phone. |
| `company` | string | no | Guest company. |
| `event_description` | string | no | What the guest wants to host. |
| `event_date` | date | no | Requested date. |
| `guest_count` | integer | no | Number only, for example 25. |
| `location_id` | integer | no | Required if your account has more than one location. |

Creates a lead in your Leads list. First name, last name and email are required; the guest count must be a number such as 25, not a range, and the location is required if your account has more than one. Your team sees the new lead and may be notified, so the call asks you first. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "lead_id": 90455,
  "status": "created",
  "conversion_status": "Not Converted",
  "created_at": "2026-10-17T10:05:00-04:00"
}
```

### convert_lead

Convert a lead to a Prospect event, a booking or a contact. Access: write, asks the user first. REST: `POST /api/v1/tripleseat/leads/{lead_id}/convert`. MCP: `tripleseat_write → convert_lead`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `lead_id` | integer | yes | Lead ID from list_leads. |
| `convert_to` | string | yes | prospect_event, booking or contact. |
| `room_id` | integer | no | Required for prospect_event and booking. From list_rooms. |
| `event_name` | string | no | Name of the new event or booking. Default: built from the lead. |
| `status` | string | no | Prospect, Tentative or Definite. Default: Prospect. |

Does what Convert this Lead does in Tripleseat: the lead details fill the new record. An event or booking needs a room (event space). A new event starts as Prospect unless you set another status. Tripleseat sends the guest no email on conversion. Converting changes what your team works on and is not reversed with one call. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "lead_id": 90412,
  "converted_to": "prospect_event",
  "event_id": 5530340,
  "booking_id": 770412,
  "event_name": "Okafor birthday dinner",
  "status": "Prospect",
  "room": "Garden Room",
  "converted_at": "2026-10-17T10:10:00-04:00"
}
```

### turn_down_lead

Mark a lead as turned down. Access: write, asks the user first. REST: `POST /api/v1/tripleseat/leads/{lead_id}/down-lead/turn`. MCP: `tripleseat_write → turn_down_lead`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `lead_id` | integer | yes | Lead ID from list_leads. |

Marks the lead Turned Down, the same as turning it down in Tripleseat. The guest gets no email or notification. Tripleseat suggests converting a lead you will not pursue to a contact instead, so you keep the details; use turn_down_lead when you do not want to store the guest. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "lead_id": 90433,
  "conversion_status": "Turned Down",
  "turned_down_at": "2026-10-17T10:12:00-04:00"
}
```

### create_event

Create an event in a room, on a date, for a contact. Access: write, asks the user first. REST: `POST /api/v1/tripleseat/locations/{location_id}/events`. MCP: `tripleseat_write → create_event`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Event name. |
| `status` | string | yes | Prospect, Tentative, Definite, Closed or Lost. |
| `location_id` | integer | yes | Location ID. |
| `room_id` | integer | yes | Room ID from list_rooms. |
| `event_start` | datetime | yes | Start date and time. |
| `event_end` | datetime | yes | End date and time. |
| `account_id` | integer | yes | Account ID from search_contacts. |
| `contact_id` | integer | yes | Contact ID from search_contacts. |
| `booking_id` | integer | no | Add the event to this booking instead of a new one. |
| `guest_count` | integer | no | Expected guests. |

Creates an event with a name, status, location, date, start and end time, account and contact. Without booking_id Tripleseat creates a new booking for it. Set status to Prospect for a first inquiry. Check the room first with check_room_availability. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "event_id": 5530402,
  "booking_id": 770420,
  "name": "Lindqvist team lunch",
  "status": "Prospect",
  "event_date": "2026-11-20",
  "room": "Loft"
}
```

### set_event_status

Move an event to Prospect, Tentative, Definite, Closed or Lost. Access: write, asks the user first. REST: `PUT /api/v1/tripleseat/events/{event_id}/status`. MCP: `tripleseat_write → set_event_status`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | integer | yes | Event ID from list_events. |
| `status` | string | yes | Prospect, Tentative, Definite, Closed or Lost. |
| `lost_reason` | string | no | Only for Lost. A reason from your Lost Reason dropdown. |

Changes the status, the same as Edit and Update on the event. Tentative and Definite hold the room, Closed ends editing, and Lost frees the room and keeps communication and documents. Lost takes an optional lost_reason; the reasons are the ones in Settings > Preferences > Dropdowns. Your user role needs the permissions for it. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "event_id": 5528840,
  "name": "Alvarez rehearsal dinner",
  "status": "Closed",
  "previous_status": "Definite",
  "amount_due": 0
}
```

### create_task

Add a task with an assignee, due date and priority to a lead, event, booking, contact or account. Access: write, asks the user first. REST: `POST /api/v1/tripleseat/records/{record_id}/tasks`. MCP: `tripleseat_write → create_task`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `record_type` | string | yes | lead, event, booking, contact or account. |
| `record_id` | integer | yes | ID of that record. |
| `body` | string | yes | What needs to be done. |
| `assignee_id` | integer | yes | User ID. For events and bookings, the owner or a manager. |
| `due_date` | date | no | Due date. |
| `priority` | string | no | low, medium or high. |

Does what Add Task does on the Tasks tab. The assignee on an event or booking must be its owner or a manager. Priority is low, medium or high. The task appears on the assignee's Tasks page, so the call asks you first. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "task_id": 881204,
  "record_type": "event",
  "record_id": 5529012,
  "body": "Chase signed contract and deposit for the Delgado rehearsal dinner on 21 Nov.",
  "assignee": "Sam Reyes",
  "due_date": "2026-10-20",
  "priority": "high",
  "completed": false
}
```

## How do I connect Tripleseat to Claude Code, Codex or Cursor?

Connecting Tripleseat takes three steps: sign up, sign in to Tripleseat once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Tripleseat to your agent.

1. **Create an account** Sign up and add Tripleseat in the console. Your API key is there too.

2. **Sign in to Tripleseat in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Tripleseat there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Tripleseat tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Go through Tripleseat leads that are not converted yet. If the date is free in the room they asked for, convert the lead to a Prospect event. Turn down anything outside our capacity and leave the rest for me with a one-line reason.
```

### Call Tripleseat from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/tripleseat with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/tripleseat/leads \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"first_name":"Ife","last_name":"Okafor","email_address":"ife@example.com","event_description":"Birthday dinner for my sister","event_date":"2026-11-14","guest_count":28,"location_id":1201}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "lead_id": 90455,
  "status": "created",
  "conversion_status": "Not Converted",
  "created_at": "2026-10-17T10:05:00-04:00"
}
```

## Why use Cotlet for Tripleseat?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Tripleseat yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Tripleseat changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Tripleseat to Cotlet?

Yes. You sign in to Tripleseat yourself, in your own Cloud Browser, and we never save your password. Your agents only get Tripleseat once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Tripleseat integration?**

No, Cotlet is independent of Tripleseat. Tripleseat's own API is too limited for this work. Cotlet works through your own Tripleseat account, the way you use Tripleseat in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Tripleseat in your console: your agents lose access at once and you stay signed in. Signing out of Tripleseat in the browser works too, and Reset browser deletes the whole profile.

## Is there a Tripleseat MCP server on GitHub?

Yes. Community Tripleseat MCP servers exist on GitHub, usually maintained by one person, and at least one is read-only. You install one yourself, register an OAuth app in Tripleseat, and fix the server when the API changes. Cotlet hosts the same kind of server for you, adds the writes the API lacks, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, deploy it, create an OAuth 2.0 app in Settings > Tripleseat API & Webhooks, store its secret, add the server to each MCP client | Sign up, sign in to Tripleseat once, add one MCP server or API key |
| When Tripleseat changes | It breaks until you or the maintainer fix it; the move from OAuth 1.0 to OAuth 2.0 in 2026 forced a rewrite of auth | Our team tests it daily and fixes it for you; failed calls are free |
| Your Tripleseat access | An OAuth client secret in your hosting settings, valid for every site of your account | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When the session expires | Access tokens last 2 hours and refresh by token; a revoked app stops everything until a customer admin authorizes it again | Your Cloud Browser keeps you signed in; if Tripleseat logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your server or serverless account, with the tools its author wrote | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Tripleseat changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Tripleseat API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Tripleseat API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Tripleseat account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Tripleseat yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Tripleseat only after you enable it. When Tripleseat signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Tripleseat, sign out of Tripleseat in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Tripleseat's terms:** You use your own Tripleseat account and stay responsible for following Tripleseat's terms. Cotlet is independent and not affiliated with Tripleseat. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Tripleseat in the console and press Request access. Then you create your API key and connect Tripleseat there.

**Do I need to be technical?**

No. You sign in to Tripleseat once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Tripleseat to Cotlet?**

Yes. You sign in to Tripleseat yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Tripleseat once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Tripleseat sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Tripleseat cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Tripleseat's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Tripleseat sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Tripleseat login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Tripleseat offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Do I need the Tripleseat API or an OAuth app?**

No. Cotlet works in your own Tripleseat user and does not use the API, so you register no OAuth app and no customer admin has to authorize one. What your agent can do follows your user role, set under Settings > User roles, and a Customer Admin can change the role.

**Does Tripleseat email the guest when my agent converts or turns down a lead?**

No. Tripleseat sends the guest no auto-response email or notification when a lead is converted or turned down. Emails to guests come from your lead form auto-response, Discussions and Automated Discussions, which these tools do not trigger.

**Can my agent post or send messages in Tripleseat without asking me?**

No. Every call to create_lead, convert_lead, turn_down_lead, create_event, set_event_status or create_task waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

**Can I use the Tripleseat API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/tripleseat from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

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.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.