# Ticketglide Ticketing Agent MCP server

> Search and read TicketGlide travel guides for cities, attractions and day trips, and build website search links.

- Listing: https://mcp.tc/i/ticketglide-ticketing-agent
- Connect: use the server's own URL `https://ticketglide.com/api/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: none
- Category: [Travel & Maps](https://mcp.tc/c/travel-maps)
- Vendor: Mubboo LLC
- Homepage: <https://ticketglide.com/>

## About

Connects to TicketGlide's published editorial guides for cities, attractions, tours and day trips. You can search guides, read a full guide with source links and factual check dates, and build a TicketGlide website search URL for a destination and category. Guides are available in English, French, German and Spanish.

The server is hosted at a streamable HTTP endpoint and needs no sign-in or API key. It is read-only: it has no live inventory, bookings, payments, accounts or reviews, and editorial prices are not live quotes.

## What it can do

- Search published city, attraction and day-trip guides
- Read a guide with source links and check dates
- Build a TicketGlide search link by destination and category
- Choose guide language and display currency
- Read-only, no booking or payment

## Tools (3)

- `search_guides`: Find published city, attraction and day-trip guides by editorial metadata. (read-only)
- `read_guide`: Read a published guide by path, with source links and factual check dates. (read-only)
- `create_search_link`: Build a TicketGlide website search URL for a destination, query and category. (read-only)

## Example prompts

- "Find TicketGlide guides for day trips from Rome."
- "Read the guide for the Eiffel Tower and summarize the visiting tips."
- "Create a TicketGlide search link for food tours in Tokyo in USD."
- "Search for Barcelona attraction guides in Spanish."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http ticketglide-ticketing-agent https://ticketglide.com/api/mcp
```

2. Start Claude Code and type `/mcp`. **ticketglide-ticketing-agent** should show as connected.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **Ticketglide Ticketing Agent** and paste this URL:

```url
https://ticketglide.com/api/mcp
```

3. Click **Add**. Its tools appear in the chat’s tools menu.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Ticketglide%20Ticketing%20Agent&connectorUrl=https%3A%2F%2Fticketglide.com%2Fapi%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://ticketglide.com/api/mcp` and click **Add**.

3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://ticketglide.com/api/mcp` as the server URL, then for authentication choose **No authentication**.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=ticketglide-ticketing-agent&config=eyJ1cmwiOiJodHRwczovL3RpY2tldGdsaWRlLmNvbS9hcGkvbWNwIn0%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "ticketglide-ticketing-agent": {
      "url": "https://ticketglide.com/api/mcp"
    }
  }
}
```

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=ticketglide-ticketing-agent&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fticketglide.com%2Fapi%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"ticketglide-ticketing-agent","type":"http","url":"https://ticketglide.com/api/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "ticketglide-ticketing-agent": {
      "type": "http",
      "url": "https://ticketglide.com/api/mcp"
    }
  }
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "ticketglide-ticketing-agent": {
      "serverUrl": "https://ticketglide.com/api/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add ticketglide-ticketing-agent --url https://ticketglide.com/api/mcp
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.ticketglide-ticketing-agent]
url = "https://ticketglide.com/api/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http ticketglide-ticketing-agent https://ticketglide.com/api/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "ticketglide-ticketing-agent": {
      "type": "http",
      "url": "https://ticketglide.com/api/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://ticketglide.com/api/mcp`.

## Recent changes

- 2026-10-17 16:22 UTC: Tracking started: 3 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/ticketglide-ticketing-agent#history (Atom feed: https://mcp.tc/i/ticketglide-ticketing-agent/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 0.1.0
- MCP protocol version: 2026-07-28
- Last checked: 2026-11-12 (reachable)
- Listed: 2026-10-17
- Updated: 2026-10-17

---
Source: https://mcp.tc/i/ticketglide-ticketing-agent (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report