ThinAir Dataofficial
A
licenseA
qualityB
maintenanceConnect any AI to PostgreSQL, MySQL, or SQL Server — 24 dialect-aware tools for query, schema, optimization, and more.
23
30 npm
1
MIT
ThinAir Geo
OfficialRelated Servers
Alternatives to ThinAir Geo
Related Servers
- AlicenseAqualityDmaintenanceGeospatial API tools for AI agents — geocoding, reverse geocoding, routing, isochrone, distance matrix, static maps, H3 hexagons, elevation, GPS map-matching, point-in-polygon, address normalisation, timezone lookup, and batch geocoding. Built on OpenStreetMap infrastructure. Cost-effective alternative to Google Maps API.1814 npmMIT
Magic Lane MCP Serverofficial
AlicenseBqualityCmaintenanceEnables AI agents to become geospatially intelligent assistants with tools for location search, smart routing, round trip planning, reverse geocoding, isochrone analysis, route visualization, geofence management, and interactive map display.85 npm7Apache 2.0
Mapbox MCP Serverofficial
AlicenseAqualityAmaintenanceProvides geospatial intelligence to AI agents through Mapbox APIs, enabling geocoding, routing, POI search, map images, and offline spatial calculations.282,984 npm363MIT
FoundryNet Geoofficial
FlicenseNot gradedqualityFmaintenanceEnables geocoding (address to coordinates and reverse) and distance calculations for AI agents with per-call micropayments in USDC, no API keys required.-- AlicenseNot gradedqualityDmaintenanceProvides AI applications with geospatial intelligence through Mapbox APIs, enabling geocoding, POI search, routing, travel time analysis, isochrone generation, and static map creation for location-aware functionality.2,984 npmBSD 3-Clause
- AlicenseAqualityBmaintenanceProvides AI agents with structured search results, place details, ratings, and contact info from Google Maps without requiring any API keys.22MIT
TDQS
A3.9/5.0
Scored across 19 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: geocoding variants (free-text, structured, batch, reverse, intersection), routing (directions, map matching, trace, distance matrix), search (places vs explore), and utilities (traffic, weather, locate, geofence, place_get, quota, issue_api_key). No overlapping functionality.
Naming Consistency4/5
Most tools use a verb_noun pattern (reverse_geocode, search_places, resolve_intersection, etc.), though a few are single-word verbs (directions, traffic, weather, explore, locate, quota, geocode). The convention is lower_snake_case throughout, and the pattern is predictable despite minor inconsistency.
Tool Count4/5
19 tools is slightly above the ideal range but justified given the breadth of geo functionality: geocoding, routing, traffic, weather, POI search, map matching, geofencing, and account management. Each tool earns its place; the set is not bloated.
Completeness5/5
The tool surface covers the full lifecycle for geographic queries: input (various geocoding), routing (directions, distance matrix, isochrones), map matching, POI search, traffic, weather, geofencing, and account management. No obvious gaps for a query-only geo API.
Maintenance
ActivityMaintained
ResponsivenessNo issues