Geocoding, truck routing, traffic, weather, and place search via MCP — 11 hosted tools.
Use this profile to copy client config, check auth requirements, review tools and resources, and compare related MCP servers before adding it to an AI client.
Get practical integration notes and launch examples for MCP servers like geo.
https://geo.thinair.co/mcpHeaders: Authorization
Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"co-thinair-geo": {
"url": "https://geo.thinair.co/mcp"
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
Paste an API key, bearer token, or session value from the provider. It is used once to list inventory and discarded after the request.
Paste `Bearer ta_live_...` (or `Bearer ta_trial_...`). Get a free key — 15 req/day, no card — at https://geo.thinair.co/connect.
geo is an MCP server for Geocoding, truck routing, traffic, weather, and place search via MCP — 11 hosted tools.. It supports HTTP transport.
Use the generated config in Install. It points your client at the advertised remote endpoint shown on this page.
Choose the Claude Desktop tab in Install, copy the config, and add it to Claude Desktop's MCP server settings. Endpoint: https://geo.thinair.co/mcp.
Choose the Claude Code tab in Install, copy the config, and add it to Claude Code's MCP server settings. Endpoint: https://geo.thinair.co/mcp.
Choose the Codex tab in Install, copy the config, and add it to Codex's MCP server settings. Endpoint: https://geo.thinair.co/mcp.
Choose the Cursor or VS Code tab in Install, copy the config, and add it to Cursor or VS Code's MCP server settings. Endpoint: https://geo.thinair.co/mcp.
geo uses HTTP transport. Endpoint: https://geo.thinair.co/mcp.
geo inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
geo is marked with Auth required by registry metadata auth. You may need provider login, an API key, a bearer token, or a session header.