ClickBus MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLICKBUS_ALLOW_MUTATIONS | No | Enable gated pay tools (clickbus_book, clickbus_cancel). Must be enabled (and explicit_user_intent true) for mutations to work. | false |
| CLICKBUS_MCP_ALLOWED_ORIGIN | No | Allowed Origin for the optional HTTP transport. Defaults to http://127.0.0.1:<port>. |
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 |
|---|---|
| clickbus_connection_statusC | Local doctor: token present, mutations off by default, unofficial ClickBus consumer surface. |
| clickbus_capabilitiesB | What this unofficial MCP can read and which writes stay gated. |
| clickbus_privacy_auditA | Shows redaction defaults (street/phone/GPS) and that book is off unless both gates are set. |
| clickbus_search_placesA | Read-only place search (terminals/cities). Does not book a ticket. |
| clickbus_search_trips_v5B | Read-only GET /api/v5/trips (JSON 200). Does not book. |
| clickbus_price_previewC | Prices and installments from live GET /api/v4/trips. Dedicated preview URL 404/405. |
| clickbus_boarding_pointsB | Terminals from live trip JSON. Dedicated boarding URLs 404/500. |
| clickbus_seat_availabilityB | availableSeats/totalSeats from live trip JSON. Full seat map HTTP 500 is an honest gap. |
| clickbus_search_tripsA | Read-only trip search on /api/v4/trips. Does not book. GPS/street redacted. |
| clickbus_booking_historyB | Past consumer bookings. Read-only. Street/phone/GPS redacted. |
| clickbus_track_bookingB | Status only. Does not return GPS polylines or passenger documents. |
| clickbus_bookA | Fail-closed. Needs CLICKBUS_ALLOW_MUTATIONS and explicit_user_intent. Guest tokens cannot charge. Default examples never enable this. |
| clickbus_cancelA | Fail-closed. Needs CLICKBUS_ALLOW_MUTATIONS and explicit_user_intent. Guest tokens cannot charge. |
| clickbus_logoutA | Deletes ~/.clickbus-mcp/tokens.json. Requires explicit_user_intent. |
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 14 tools
Several tools overlap or could be confused: clickbus_search_trips and clickbus_search_trips_v5 appear to do nearly the same thing, clickbus_price_preview overlaps with trip search pricing, and clickbus_boarding_points vs clickbus_search_places both relate to terminals/cities. The descriptions help, but the boundaries are not always crisp.
All tools share the clickbus_ prefix and snake_case style, but the naming pattern is mixed: some are verb_noun (search_trips, track_booking), some are noun-only (boarding_points, seat_availability), and some are bare verbs (book, cancel, logout). Consistent prefix helps, but the overall convention is not uniform.
14 tools is within a reasonable range for a travel/booking domain covering search, pricing, availability, booking, cancellation, history, and account/status operations. A few tools are diagnostic or meta-oriented (connection_status, capabilities, privacy_audit), but they do not make the count feel bloated.
The set covers the core ClickBus workflow: place search, trip search, pricing, boarding points, seat availability, booking, cancellation, history, and tracking. There are notable gaps such as full seat map selection and detailed booking document access, but the main lifecycle is present and usable.