Tripleseat API and MCP server

Tripleseat's API cannot convert a lead to an event or turn a lead down. Sign in to Tripleseat once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.

Not affiliated with Tripleseat.

Tripleseat has no API for this. So we run one for you.

Tripleseat's own API, a GitHub MCP server and Cotlet compared
What you need Tripleseat's APIGitHub MCP serverCotlet
Converting or turning down leads No Partly Yes, 15 tools
Acts as you, signed in 24/7 No No Yes, Cloud Browser
Fixed for you when Tripleseat changes N/A No Yes, tested every 6h
Runs with your laptop off N/A No Yes, hosted

Checked Oct 17, 2026. Sources: Tripleseat Help: API Overview & Resources · Tripleseat Help: OAuth 2.0 Implementation · Tripleseat Help: OAuth 1.0 to OAuth 2.0 Migration Guide · Tripleseat API OpenAPI specification

Your own Cloud Browser, on 24/7. Sign in once. We keep it connected.

  1. 01Sign in to Tripleseat in your own Cloud Browser

  2. 02Connect it for your agents

  3. 03Cotlet keeps it signed in and working

How do I connect Tripleseat to Claude, ChatGPT or my code?

AI agents connect over MCP, scripts call the REST API. Both reach the same 15 tools with one API key.

For AI agents: MCP

Add Cotlet to your agent once. Tripleseat and every other app you connect show up as its tools.

  • Claude
  • ChatGPT
  • OpenClaw
  • Hermes
  • GrokBot
  • Cursor
  • n8n
  • Any MCP client
  1. 1

    Add Cotlet to your agent

    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"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

For scripts: REST API

Every tool is an endpoint under /api/v1/tripleseat with its own method and path, such as POST /api/v1/tripleseat/leads, with the same API key. Our open-source repo has ready scripts to start from.

REST API docs

What can the Tripleseat API and MCP server do?

15 tools on your own Tripleseat account. Agents call them as operations of the MCP tools tripleseat_read and tripleseat_write; scripts call each one at its own REST endpoint, with the same inputs and answers.

Tripleseat tools in Cotlet's MCP server and REST API
Tool What it does Access
list_leads Leads from your lead forms and manual entry, filtered by Conversion Status. read
get_lead One lead with the full request, contact details and lead source. read
list_events Events by status, date range, room or location, with guest count and amount due. read
get_event One event with its booking, rooms, contact, guest count and financials. read
list_bookings Bookings with their events, filtered by status and date. read
get_booking One booking with its events, contact, account and lead. read
list_rooms Rooms in each location, with the room IDs other tools need. read
check_room_availability Events and calendar blocks that are in the way of a room on a date and time. read
search_contacts Contacts and accounts by name, email or company. read
create_lead Add an inquiry to Leads with the guest, date, guest count and request. writeasks first
convert_lead Convert a lead to a Prospect event, a booking or a contact. writeasks first
turn_down_lead Mark a lead as turned down. writeasks first
create_event Create an event in a room, on a date, for a contact. writeasks first
set_event_status Move an event to Prospect, Tentative, Definite, Closed or Lost. writeasks first
create_task Add a task with an assignee, due date and priority to a lead, event, booking, contact or account. writeasks first

Scroll the table for all 15 tools.

Ask in plain words. Your agent does the rest.

Is it safe to connect Tripleseat?

You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.

How much do the Tripleseat API and MCP server cost?

One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Most calls use 25 credits, and your Cloud Browser uses 50 credits a day while Tripleseat is enabled for agents, so 20 calls a day come to 550 credits.

Cotlet credit packs: price, credits and calls at 25 credits each
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.

Questions

Does Tripleseat have an 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.

How do I get access?

Sign up free, open Tripleseat under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.

Is the MCP server different from the API?

No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 15 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.

What is the Cloud Browser?

Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to Tripleseat yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so Tripleseat sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.

Can my agent act without asking me?

Not on anything that reaches other people: create_lead, convert_lead, turn_down_lead, create_event, set_event_status, create_task wait for your OK by default. You can switch that off per tool for scheduled runs.

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.

Should I use a Tripleseat MCP server from GitHub instead?

Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when Tripleseat changes. Pick Cotlet if you want it hosted and kept working for you.

Can I use it in n8n, Make or Zapier?

Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.

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 Cotlet affiliated with Tripleseat?

No. Cotlet is independent and not affiliated with Tripleseat.

Give your agent access to Tripleseat.

Free 7-day trial with 2,000 credits, no card needed.