Ext Ops Panel
Open dashboard
Comparison

Mapbox vs tickadoo Experiences and Events

Mapbox is an MCP server published by mapbox. Marketplaces we read that list it: 1 (Docker MCP Catalog). tickadoo Experiences and Events is an MCP server published by tickadoo. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-15. 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
MarketplaceMapboxtickadoo Experiences and Events
Docker MCP Catalog Listed
Version: sha256:298701beaeed
Forks (GitHub): 44
Pulls (Docker Hub): 35 397
Stars (Docker Hub): 2
Stars (GitHub): 360
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.1.1
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen

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

Mapbox vs tickadoo Experiences and Events
FactMapboxtickadoo Experiences and Events
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)360 (better)2 (worse)
Pulls (Docker Hub) (differs)35 397No figure on Docker Hub
Forks (GitHub) (differs)44 (better)0 (worse)
Last release (differs)Not published2026-10-12
Where it runs (differs)On your machine (mcp/mapbox)Remote server (mcp.tickadoo.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)28Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle8
LicenceMITMIT
Repository (differs)github.com/mapbox/mcp-servergithub.com/tickadoo/tickadoo-mcp
Changes in the last 7 days (differs)03
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

Mapbox

In its own words, on Docker MCP Catalog:

Transform any AI agent into a geospatially-aware system with Mapbox APIs. Provides geocoding, POI search, routing, travel time matrices, isochrones, and static map generation.

tickadoo Experiences and Events

In its own words, on Official MCP Registry:

Discover and book theatre, tours, attractions, and live experiences worldwide. No API key required.

How to run each

Mapbox As a local MCP server: Docker image

Claude Code
claude mcp add --env "MAPBOX_ACCESS_TOKEN=<YOUR_MAPBOX_ACCESS_TOKEN>" --transport stdio mapbox -- docker run -i --rm -e MAPBOX_ACCESS_TOKEN mcp/mapbox

Requires: MAPBOX_ACCESS_TOKEN (secret)

tickadoo Experiences and Events As a remote MCP server

Claude Code
claude mcp add --transport http tickadoo-mcp https://mcp.tickadoo.com/mcp

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

Tools each declares

The marketplaces of tickadoo Experiences and Events publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of tickadoo Experiences and Events publish no settings it asks for, so we do not compare settings.

What it can do: Mapbox · What it can do: tickadoo Experiences and Events · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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