[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 MCP tools

> The Tripleseat MCP tools on the Cotlet server: every operation with its input schema, a tools/call example and an example result.

Source: https://cotlet.dev/docs/mcp/tripleseat

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Tripleseat has 15 operations on the Cotlet MCP server, in tripleseat_read and tripleseat_write. Your agent picks one in `operation`; the tool carries each operation's input schema. Open an operation for its schema and an example call.

- MCP server: `https://cotlet.dev/mcp/v1`
- MCP tools: `tripleseat_read`, `tripleseat_write`
- Connects with: Your own Tripleseat user on your venue account. What your agent can do follows your user role (Settings > User roles). You sign in once in your own browser and keep your 2-step verification or SAML sign-in.
- Integration page: https://cotlet.dev/integrations/tripleseat-api-mcp-server

## Read

Return data and change nothing in the account.

| Operation | Description |
|---|---|
| [`list_leads`](https://cotlet.dev/docs/mcp/tripleseat/list_leads.md) | Leads from your lead forms and manual entry, filtered by Conversion Status. |
| [`get_lead`](https://cotlet.dev/docs/mcp/tripleseat/get_lead.md) | One lead with the full request, contact details and lead source. |
| [`list_events`](https://cotlet.dev/docs/mcp/tripleseat/list_events.md) | Events by status, date range, room or location, with guest count and amount due. |
| [`get_event`](https://cotlet.dev/docs/mcp/tripleseat/get_event.md) | One event with its booking, rooms, contact, guest count and financials. |
| [`list_bookings`](https://cotlet.dev/docs/mcp/tripleseat/list_bookings.md) | Bookings with their events, filtered by status and date. |
| [`get_booking`](https://cotlet.dev/docs/mcp/tripleseat/get_booking.md) | One booking with its events, contact, account and lead. |
| [`list_rooms`](https://cotlet.dev/docs/mcp/tripleseat/list_rooms.md) | Rooms in each location, with the room IDs other tools need. |
| [`check_room_availability`](https://cotlet.dev/docs/mcp/tripleseat/check_room_availability.md) | Events and calendar blocks that are in the way of a room on a date and time. |
| [`search_contacts`](https://cotlet.dev/docs/mcp/tripleseat/search_contacts.md) | Contacts and accounts by name, email or company. |

## Write

Change the account. Calls marked Confirm wait for the user to approve them.

| Operation | Description |
|---|---|
| [`create_lead`](https://cotlet.dev/docs/mcp/tripleseat/create_lead.md) (Confirm) | Add an inquiry to Leads with the guest, date, guest count and request. |
| [`convert_lead`](https://cotlet.dev/docs/mcp/tripleseat/convert_lead.md) (Confirm) | Convert a lead to a Prospect event, a booking or a contact. |
| [`turn_down_lead`](https://cotlet.dev/docs/mcp/tripleseat/turn_down_lead.md) (Confirm) | Mark a lead as turned down. |
| [`create_event`](https://cotlet.dev/docs/mcp/tripleseat/create_event.md) (Confirm) | Create an event in a room, on a date, for a contact. |
| [`set_event_status`](https://cotlet.dev/docs/mcp/tripleseat/set_event_status.md) (Confirm) | Move an event to Prospect, Tentative, Definite, Closed or Lost. |
| [`create_task`](https://cotlet.dev/docs/mcp/tripleseat/create_task.md) (Confirm) | Add a task with an assignee, due date and priority to a lead, event, booking, contact or account. |

---

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.