Geo
Add geocoding, routing, traffic, weather, and place search to your app or agent workflow through ThinAir Geo’s 11 hosted MCP tools.
Overview
co.thinair/geo is an MCP server for the Build phase that exposes geocoding, truck routing, traffic, weather, and place search through 11 hosted tools.
What is this MCP server?
- 11 hosted MCP tools for geocoding, truck routing, traffic, weather, and place search
- Streamable HTTP remote at https://geo.thinair.co/mcp
- Free trial key path: 15 requests/day, no card, via https://geo.thinair.co/connect
- Bearer ta_live_ or ta_trial_ Authorization header
- Server version 2.1.4 with public website at geo.thinair.co
- Free trial: 15 requests per day, no card (per connect docs)
What problem does it solve?
Shipping location-aware features stalls when every agent task requires separate API docs for geocode, routes, traffic, and weather.
Who is it for?
Indie builders adding logistics, maps, or weather-dependent UX who want one MCP endpoint for multiple geo capabilities.
Skip if: Products with zero location needs, teams requiring on-prem map tiles only, or workflows that cannot use a hosted third-party geo API.
What do I get? / Deliverables
Once the MCP remote and Bearer key are configured, your assistant can call unified geo tools while you integrate results into your app.
- Agent-accessible geocoding, routing, traffic, weather, and search calls
- Faster Build-phase integration of location backends
- Trial-friendly path to validate geo features before scaling usage
Recommended MCP Servers
Journey fit
Build is where map, logistics, and location features get wired into prototypes and shipping products via third-party APIs. Integrations reflects a hosted geo API surface exposed to agents rather than custom map UI implementation.
How it compares
ThinAir hosted geo API MCP—not an open-source map renderer or mobile SDK substitute.
Common Questions / FAQ
Who is co.thinair/geo for?
Solo developers building delivery, travel, operations, or field apps who want agents to call geocoding, routing, traffic, weather, and search APIs via MCP.
When should I use co.thinair/geo?
Use it during Build when you are integrating location features, validating routes, or enriching agent prompts with real-world place and weather data.
How do I add co.thinair/geo to my agent?
Get a Bearer ta_trial_ or ta_live_ key at https://geo.thinair.co/connect, add it as the Authorization header for https://geo.thinair.co/mcp, and register the remote in your MCP client.