Tomtom vs Cesium MCP

A side-by-side look at the Tomtom and Cesium MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Tomtom logoTomtomLocation Services · Local subprocess (stdio)TomTom MCP — wraps the TomTom Search & Routing APIs (api.tomtom.com)59GoodAuth: not declaredCesium MCP logoCesium MCPData Visualization · Local subprocess (stdio)AI-powered 3D globe control via MCP. Connect any MCP-compatible AI agent to CesiumJS — camera flight, GeoJSON/3D Tiles layers, markers, spatial analysis, heatmaps, and more through 19 natural language tools.69GreatAuth: no auth required

Verdict: choose Tomtom for location services work as a local process; choose Cesium MCP for data visualization as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Tomtom logoChoose Tomtom when

  • You need dedicated capabilities in the Location Services domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like geocode, search_poi, reverse_geocode.
Explore Tomtom

Cesium MCP logoChoose Cesium MCP when

  • You need dedicated capabilities in the Data Visualization domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like flyTo, setView, getView.
Explore Cesium MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecTomtom logoTomtomCesium MCP logoCesium MCP
CategoryLocation ServicesData Visualization
Quality signal59/100 · Good69/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars0145
Directory activity 2 views 0 installs 0 upvotes 10 views 0 installs 0 upvotes
Tools433

Tools & capabilities

Tomtom tools 4

  • geocodeGeocoding: convert an address, place name, or free-text location query into geographic coordinates (latitude/longitude). Returns formatted address, country, lat, lon, type, and match score. Example: geocode({ query: "350 5th Ave, New York" })
  • search_poiSearch for points of interest (POIs) — businesses, landmarks, restaurants, gas stations, etc. — by name or category, optionally near a lat/lon center within a radius. Returns name, category, address, coordinates, phone, url, and distance. Example: search_poi({ query: "coffee", lat: 40.748, lon: -73.985, radius: 1000 })
  • reverse_geocodeReverse geocoding: convert latitude/longitude coordinates into a human-readable street address. Returns the freeform address, country, municipality, street name, postal code, and position. Example: reverse_geocode({ lat: 40.748, lon: -73.985 })
  • routeTraffic-aware routing / directions: calculate the best route between two points and return distance plus travel time computed with live traffic. Reports traffic delay so you get realistic ETAs, not free-flow estimates. Supports car, truck, pedestrian, and bicycle travel modes. Example: route({ from_lat: 40.748, from_lon: -73.985, to_lat: 40.689, to_lon: -74.044 })

Cesium MCP tools 33

  • flyToAnimate the camera to a geographic location. Use for visible navigation requested by the user. Returns { success: boolean, message?: string, error?: string }.
  • setViewSet the camera position immediately without animation. Use for deterministic setup or instant view changes. Returns { success: boolean, message?: string, error?: string }.
  • getViewGet the current camera position and orientation. Returns { success, data: { longitude, latitude, height, heading, pitch, roll }, message? }.
  • zoomToExtentAnimate the camera to a west/south/east/north bounding box. Returns { success: boolean, data?: unknown, message?: string, error?: string }.
  • saveViewpointSave the current camera state under a page-local name. Returns { success: boolean, data?: unknown, message?: string, error?: string }.
  • loadViewpointRestore a previously saved page-local camera state. Returns { success: boolean, data?: unknown, message?: string, error?: string }.
  • listViewpointsList camera viewpoints saved in the current page. Returns { success: boolean, data?: unknown, message?: string, error?: string }.
  • exportSceneExport the current view, layer, and entity state as JSON. Returns { success: boolean, data?: unknown, message?: string, error?: string }.
  • addMarkerAdd a point marker at geographic coordinates. Returns { success, data: { entityId }, message? }; keep entityId for removeEntity.
  • addLabelAdd property-based text labels for GeoJSON features. Returns { success, data: { labelCount: integer }, message? }.
  • addModelAdd a glTF or GLB model at geographic coordinates. Returns { success: boolean, data?: unknown, message?: string, error?: string }.
  • addPolygonDraw a polygon area from geographic coordinate tuples. Returns { success, data: { entityId }, message? }; keep entityId for removeEntity.
  • +21 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Tomtom

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "tomtom": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-tomtom"
      ]
    }
  }
}

Cesium MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "gaopengbin-cesium-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "cesium-mcp-runtime"
      ]
    }
  }
}

Frequently asked questions

Tomtom is categorized under Location Services and uses a local stdio subprocess. Cesium MCP belongs to Data Visualization and uses a local stdio subprocess. Pick Tomtom for location services work and Cesium MCP for data visualization.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Tomtom has no declared pricing — check the project's own site. Cesium MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add tomtom and gaopengbin-cesium-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Tomtom has a quality signal of 59/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Cesium MCP has 69/100 (Great) with 10 views, 0 installs and 145 GitHub stars.