Geo

co.thinairPublished by thinair.coOfficial publisherv2.2.4Updated Oct 24, 2026

Geocoding, routing, isochrones, traffic, weather, and place search for AI agents. 19 MCP tools.

The publisher's own server: Data

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Remote MCP server giving AI assistants geocoding, routing, isochrones, traffic, weather and place search through 19 tools.

What you can do
  • Convert addresses and place names to and from coordinates (geocoding)
  • Search for places and points of interest
  • Compute routes and travel directions between locations
  • Generate isochrones showing areas reachable within a time or distance
  • Retrieve traffic conditions and weather information
When to use it
Useful when an assistant needs location intelligence: resolving addresses, planning or explaining routes, mapping reachable areas, or combining traffic and weather context with place data.
Requirements
A remote MCP endpoint at geo.thinair.co over streamable HTTP. OAuth authentication is required; most clients complete it at first use. Non-OAuth clients must supply an Authorization header with a Bearer token (live or trial).
Before you install
The Authorization header carries a secret token; keep it private and avoid exposing it in logs or shared configs. Trial tokens may have limited scope or expiry. Location queries and addresses are sent to a third-party service.

Installation

In SourceWeft

  1. Open Geo in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/co.thinair%2Fgeo/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "geo": {
      "type": "http",
      "url": "https://geo.thinair.co/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

4
  1. v2.2.4LatestOct 7, 2026
  2. v2.2.3Oct 7, 2026
  3. v2.2.2Sep 30, 2026
  4. v2.2.1Sep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Thinair integrations