Geo vs Thinair Geo

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

G
GeoLocation Services
Geocoding, truck routing, traffic, weather, and place search via MCP — 11 hosted tools.37FairAuth: not declared
Thinair Geo logoThinair GeoLocation Services · Local subprocess (stdio)Location & routing intelligence for AI agents — geocoding, truck routing with hazmat/dimension constraints, traffic, weather, isochrones, place search. Full planet coverage. Hosted MCP server with OAuth 2.0 + Bearer auth.61GoodAuth: oauth 2.0

Verdict: choose Geo for location services work; choose Thinair Geo for location services as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

G
Choose Geo when

  • You need dedicated capabilities in the Location Services domain.
Explore Geo

Thinair Geo logoChoose Thinair Geo when

  • You need dedicated capabilities in the Location Services domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: OAuth 2.0.
  • You want tools like geocode, reverse_geocode, batch_geocode.
Explore Thinair Geo

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
G
Geo
Thinair Geo logoThinair Geo
CategoryLocation ServicesLocation Services
Quality signal37/100 · Fair61/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredOAuth 2.0
PricingNot declaredFreemium
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—1
Directory activity 0 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listed19

Tools & capabilities

Geo tools

No tool names declared yet. Check the project README from the listing page.

Thinair Geo tools 19

  • geocodeConvert addresses, place names, or intersections to coordinates
  • reverse_geocodeConvert coordinates to addresses
  • batch_geocodeGeocode up to 50 addresses in one call (returns `geojson` FeatureCollection)
  • directionsTurn-by-turn routing — auto, truck, bicycle, pedestrian, motorcycle
  • isochroneTravel-time / -distance reachability polygons (multi-band)
  • trafficReal-time traffic conditions
  • weatherCurrent conditions and forecasts
  • search_placesFind nearby POIs by category (gas, charging, food, lodging, …)
  • exploreBrowse cities, neighborhoods, and venues by region
  • geocode_structuredGeocode from discrete address components (form / CRM fields) instead of free text
  • resolve_intersectionResolve a named cross-street (street1 × street2) to a coordinate with a confidence score
  • distance_matrixRoad distances + travel times for every origin → destination pair (≤ 625 pairs)
  • +7 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.

Geo

No confirmed install command for Geo yet — follow the setup steps linked from its listing page rather than a guessed package name.

Thinair Geo

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "thinairtelematics-thinair-geo": {
      "command": "npx",
      "args": [
        "-y",
        "@thinairtelematics/geo"
      ]
    }
  }
}

Frequently asked questions

Geo is categorized under Location Services and uses an install path we have not confirmed yet. Thinair Geo belongs to Location Services and uses a local stdio subprocess. Pick Geo for location services work and Thinair Geo for location services.

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. Geo has no confirmed install command yet — follow its own setup instructions.

Geo has no declared pricing — check the project's own site. Thinair Geo is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. 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 geo and thinairtelematics-thinair-geo as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Geo has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Thinair Geo has 61/100 (Good) with 2 views, 0 installs and 1 GitHub stars.