Find attraction and day-trip guides with sources and fact-check dates, read published travel advice, and create TicketGlide search links.
Encrypted at rest, isolated from the model
Resolved from an AES-256-GCM vault at the moment of the call and attached to the request — the model never sees the secrets.
Try asking
Find published TicketGlide city, attraction and day-trip guides. Searches editorial metadata, not supplier inventory.
Read a published guide path from search_guides, including source links and factual check dates when present. No drafts or supplier reviews. TicketGlide MCP documentation: https://ticketglide.com/mcp.
Build a TicketGlide website search URL. Destination is a supported destination ID/name or worldwide. Categories include all, attractions, tours and day-trips. This does not execute a search or check availability.
One endpoint, the same key, whichever client you use.
~/Library/Application Support/Claude/claude_desktop_config.json (Mac) · %APPDATA%\Claude\claude_desktop_config.json (Windows)
Replace API_KEY with your own key.
Already have an "mcpServers" section in your config? Just add the server entry inside it.
Discovery, routing, credentials, tool scoping and execution logs all happen at the gateway→connections stay ACTIVE with no work from you
Ticketglide MCP runs through a gateway that holds the credentials, scopes the access and records every call.
Managed auth, hosted MCP servers, and every Ticketglide MCP tool your agent needs.
Free to start.