Ticketglide Ticketing Agent

Claude Code

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

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:

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 (opens in a new tab)

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 (opens in a new tab)

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

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

VS Code

Install in VS Code (opens in a new tab)

Or from a terminal:

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:

{
  "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):

{
  "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

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

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

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

Gemini CLI

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.

{
  "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.

README badge

[![Ticketglide Ticketing Agent on mcp.tc](https://mcp.tc/i/ticketglide-ticketing-agent/badge.svg)](https://mcp.tc/i/ticketglide-ticketing-agent)

<a href="https://mcp.tc/i/ticketglide-ticketing-agent"><img src="https://mcp.tc/i/ticketglide-ticketing-agent/badge.svg" alt="Ticketglide Ticketing Agent on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

<script src="https://mcp.tc/w/ticketglide-ticketing-agent.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

<iframe src="https://mcp.tc/embed/ticketglide-ticketing-agent" title="Ticketglide Ticketing Agent on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/ticketglide-ticketing-agent.json

What each field means