Billetto MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Billetto MCP Server List my upcoming events"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Billetto MCP server for ChatGPT and Claude
Billetto connects to ChatGPT, Claude, Codex and Claude Code through Cotlet.dev, so your AI agent can work with events, orders and attendees in your own Billetto organiser account. This repository provides a Python MCP stdio adapter for the hosted Cotlet.dev browser tools.
Unofficial, not affiliated with, endorsed by or sponsored by Billetto.
What can an AI agent do in Billetto?
The live Billetto integration page describes 14 hosted workflow tools:
Read events, ticket types, campaigns, orders and attendees.
Add order notes and request refunds for current events.
Cancel free tickets or resend ticket PDFs.
Email guest reports, create access codes and clone events.
The page lists seven read and seven write operations. Write operations ask for approval by default; approval settings can be changed per tool. Review recipients, ticket IDs, refund amounts and report contents before approving a change or send. A cloned event needs its date and review before publication.
Related MCP server: The Events Calendar MCP Server
How do I connect Billetto to ChatGPT or Claude?
Open
billetto.comin your Cotlet.dev Cloud Browser and sign in to your organiser account yourself.In ChatGPT, add an MCP connector. In Claude, add a custom connector. Use
https://cotlet.dev/mcp/v1/connectand sign in through Cotlet.dev.Enable Billetto for agents and ask your agent to list your events.
How do I connect Codex or Claude Code?
Create an API key in the Cotlet.dev console and set COTLET_API_KEY in your environment.
Codex configuration:
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"Claude Code:
claude mcp add --transport http cotlet https://cotlet.dev/mcp/v1 --header "Authorization: Bearer $COTLET_API_KEY"How do I run the local MCP adapter?
Use Python 3.10 or newer. The adapter uses the standard library.
git clone https://github.com/cotlet-connect/billetto-mcp.git
cd billetto-mcp
python3 billetto_agent.py serveFor a client that starts local MCP servers, use an absolute path to the downloaded adapter:
{"mcpServers":{"billetto":{"command":"python3","args":["/absolute/path/billetto-mcp/billetto_agent.py","serve"],"env":{"COTLET_API_KEY":"your-key"}}}}The local adapter exposes seven browser helpers: billetto_guide, billetto_status, billetto_open, billetto_read, billetto_click, billetto_type and billetto_close. These are browser helpers, distinct from the hosted workflow catalog on the integration page. Call the guide first. Without an API key, listing tools works and tool calls return setup instructions.
python3 billetto_agent.py connect
python3 billetto_agent.py guide
python3 billetto_agent.py statusThe adapter forwards calls to https://cotlet.dev/mcp/v1; it requires a Cotlet.dev account and a signed-in Billetto Cloud Browser. At a sign-in page, sign in yourself. Close the browser session when finished.
Does Billetto have an official API or MCP server?
The live Cotlet.dev page reports a public Billetto API v3 that reads events, orders and attendees and sends webhooks, but no official MCP server or refund, cancellation or ticket resend endpoints, checked 27 October 2026. Use Billetto's own documented integration when it covers your task.
What should I ask first?
Start with a read, such as "List my upcoming events" or "Show attendees for the event I select". Refunds apply to current events; free tickets use cancellation. Ask your agent to prepare the proposed changes and review them before approval.
Source: Billetto on Cotlet.dev. Source page retrieved 20 November 2026.
Available Tools
7 toolsbilletto_clickB
Click a numbered element on the current Billetto page.
Inputs: element (required).
billetto_closeA
Close the Billetto browser session when the work is done, so credits stop running.
Inputs: no named parameters.
billetto_guideA
How to work in Billetto (manage events, orders and attendees): its screens and the sign-in link. Call this first.
Inputs: task.
billetto_openB
Open a Billetto page in your signed-in Cloud Browser (default https://billetto.com) to work with manage events, orders and attendees.
Inputs: url.
billetto_readA
Read the current Billetto page: its text and numbered buttons, links and fields.
Inputs: element.
billetto_statusB
Check that your Cotlet.dev account and Billetto are ready: account, credits and Billetto connection.
Inputs: no named parameters.
billetto_typeB
Type text into a numbered field on the current Billetto page.
Inputs: text (required), element (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Each tool has a clearly distinct role: guide, status check, open session, read page, click, type, and close. The split between setup/help and browser interaction is unambiguous, so an agent can select tools without likely confusion.
All tools consistently use the billetto_ prefix, which makes them easy to recognize as one set. However, guide and status are noun-style names while open/read/click/type/close are action verbs, a minor deviation from a strict verb_noun pattern.
Seven tools is well-scoped for a browser-automation workflow: onboarding, readiness check, session lifecycle, and core page interactions. Each tool earns its place without obvious redundancy.
The set covers the essential lifecycle from opening and reading a page through clicking and typing, then closing the session. Minor gaps exist around navigation, scrolling, waiting, or explicit select/submit actions, but these may be workable through numbered-element interactions.
Related MCP Connectors
Event ticketing: create and publish events, read orders, attendees and sales analytics.
Run in-person events from your AI: create events, manage tickets, attendees, broadcasts.
Enables AI assistants to retrieve event data and execute event management operations in Nunify.
Read Humanitix events, orders, tickets and live check-in counts, and check tickets in or out.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceIntegrates with the Eventbrite API to provide AI-assisted event management capabilities for viewing events, tracking attendees, and generating analytics reports.3MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to manage events, venues, organizers, and tickets on WordPress sites via CRUD operations.32ISC
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to generate ticket IDs with QR codes, send tickets via email/SMS/WhatsApp, and retrieve event details through the Ticket Generator API.MIT
- AlicenseAqualityCmaintenanceEnables MCP clients like Claude and ChatGPT to query and manage TicketSource box office data, including events, performances, bookings, customers, and seats, through natural language.7MIT