FreeTicket MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FT_API_KEY | No | API key for authentication (required for CI/headless). | |
| FT_API_URL | No | Base URL of the FreeTicket API (without '/api/v1'). Default is the production URL. | |
| FT_WORKSPACE_ID | No | Workspace ID (required for CI/headless if FT_API_KEY is used). | |
| FT_ADMIN_SESSION | No | Admin session token to enable admin tools (superadmin). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| public_events_listA | Catálogo público de eventos publicados (GET /public/events). Descubrimiento B2C, sin login. |
| public_events_getA | Detalle público de un evento por slug (GET /public/events/{slug}). |
| public_events_availabilityA | Stock en vivo por fecha y tipo de ticket (GET /public/events/{slug}/availability). Consultar antes de armar una orden. |
| public_orders_createA | Crea una orden B2C y devuelve el link de pago de Mercado Pago (POST /public/orders). El agente NUNCA procesa el pago: entrega la |
| public_orders_getA | Estado de una orden B2C — pending | paid | expired | cancelled — y los tickets al pagar (GET /public/orders/{id}). |
| public_tickets_resendA | Reenvía el QR/email de un ticket al correo del comprador (POST /public/tickets/{code}/resend). Rate-limited; el email va siempre al correo original de la compra. |
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 6 tools
Each tool targets a distinct resource-action pair (events availability, events detail, events list, orders create, orders get, tickets resend) with no functional overlap.
All tools follow a consistent 'public_{resource}_{action}' pattern using snake_case, making it predictable for an agent.
With 6 tools, the server is well-scoped for B2C event browsing and order management, covering the essential workflows without bloat.
The set covers the main user journey (browse, check stock, create order, check status, resend ticket) but lacks a cancel order tool, which is a minor gap.