Ext Ops Panel
Open dashboard
Comparison

exa vs Ticketglide Ticketing Agent

exa is a plugin bundle for AI coding tools published by exa-labs. Marketplaces we read that list it: 4 (Claude Code: claude-plugins-official, Official MCP Registry, Docker MCP Catalog, Claude: knowledge-work-plugins). Ticketglide Ticketing Agent is an MCP server published by ticketglide.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceexaTicketglide Ticketing Agent
Claude Code: claude-plugins-official Listed
Version: 3.4.1
Forks (GitHub): 412
Stars (GitHub): 5 217
Not marked · First seen
Not listed
Official MCP Registry Listed
Version: 3.4.1
Forks (GitHub): 412
Stars (GitHub): 5 217
Not marked · First seen
Listed
Version: 0.1.1
No figure published
Not marked · First seen
Docker MCP Catalog Listed
Version: sha256:d88edd571d98
Forks (GitHub): 412
Pulls (Docker Hub): 37 787
Stars (Docker Hub): 7
Stars (GitHub): 5 217
Not marked · First seen
Not listed
Claude: knowledge-work-plugins Listed
Version: 3.4.1
Forks (GitHub): 412
Stars (GitHub): 5 217
Not marked · First seen
Not listed

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

exa vs Ticketglide Ticketing Agent
FactexaTicketglide Ticketing Agent
Marketplaces that list it (differs)4 (better)1 (worse)
Stars (GitHub) (differs)5 217No figure on GitHub
Pulls (Docker Hub) (differs)37 787No figure on Docker Hub
Forks (GitHub) (differs)412No figure on GitHub
Last release (differs)Not published2026-10-18
Where it runs (differs)Remote server or your machineRemote server (ticketglide.com/api/mcp)
Transport (differs)Streamable HTTP, stdioStreamable HTTP
Tools it declares (differs)2Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)3Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/exa-labs/exa-mcp-serverNot stated
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-17
Endpoint at the last checkStatus out of date: last check 2 days ago returned HTTP 405Status out of date: last check 2 days ago returned HTTP 405

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

exa

In its own words, on Claude Code: claude-plugins-official:

Exa AI web search, deep research, and content extraction. Provides MCP tools and research skills for comprehensive web search, people discovery, company research, academic papers, and more.

Ticketglide Ticketing Agent

In its own words, on Official MCP Registry:

TicketGlide travel comparison and tickets: attraction and day-trip guides and tailored search links.

How to run each

exa As a Claude Code plugin

Claude Code
/plugin install exa@claude-plugins-official

Ticketglide Ticketing Agent As a remote MCP server

Claude Code
claude mcp add --transport http travel-guides https://ticketglide.com/api/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Both endpoints responded at the last daily check. How we check endpoints

Tools each declares

Only exa has

  • web_fetch_exa
  • web_search_exa

Only Ticketglide Ticketing Agent has

  • create_search_link
  • read_guide
  • search_guides

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Ticketglide Ticketing Agent as of 2026-10-23). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

The marketplaces of Ticketglide Ticketing Agent publish no settings it asks for, so we do not compare settings.

What it can do: exa · What it can do: Ticketglide Ticketing Agent · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built