Billetto MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | API key created in the Cotlet.dev console, used to authenticate with the Cotlet.dev MCP service. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Billetto through Cotlet.dev. Call billetto_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| billetto_guideA | How to work in Billetto (manage events, orders and attendees): its screens and the sign-in link. Call this first. |
| billetto_statusB | Check that your Cotlet.dev account and Billetto are ready: account, credits and Billetto connection. |
| billetto_openB | Open a Billetto page in your signed-in Cloud Browser (default https://billetto.com) to work with manage events, orders and attendees. |
| billetto_readA | Read the current Billetto page: its text and numbered buttons, links and fields. |
| billetto_clickB | Click a numbered element on the current Billetto page. |
| billetto_typeB | Type text into a numbered field on the current Billetto page. |
| billetto_closeA | Close the Billetto browser session when the work is done, so credits stop running. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.