1
Current time and IANA timezone conversion — the first-party MCP that tells an agent what time it actually is.
time, timezone, clock, iana
Best Maps, Location & Weather MCP Servers in 2026
Maps, location, and weather MCP servers for AI agents: geocoding, routing, live weather, and timezone conversion — verified for 2026.
Top Maps, Location & Weather MCPs
- 1.Time—Current time and IANA timezone conversion — the first-party MCP that tells an agent what time it actually is.
- 2.Mapbox—Official Mapbox MCP — geocoding, directions, isochrones, search, and tiles across the Mapbox API surface.
- 3.Google Maps—Geocoding, place search, directions, and travel times from Google Maps.
Ranked by top-mcps.com — data verified Aug 2026.
About Maps, Location & Weather MCP servers
The best MCP servers for maps, location, and weather ground an AI agent in physical space and time — geocoding addresses, computing routes, looking up points of interest, returning current or forecast conditions for a place, and answering the question an LLM cannot answer on its own: what time is it, and what is that in another timezone. The category covers the commercial mapping providers (Mapbox and Google Maps), a dedicated places database (Foursquare Places), a weather source (OpenWeatherMap), and the keyless Time server for current time and IANA timezone conversion. Together they supply the geocode-route-forecast-and-clock loop most travel and logistics agents need.
Choose by precision and licensing. Mapbox is the strongest official surface: geocoding, directions, isochrones (drive-time polygons), and place search behind one API token, over stdio or streamable-http, with a free tier for prototyping. Google Maps brings the place data and travel-time estimates people expect, but the MCP servers around it are community-built and every call bills against your key — restrict the key to the specific APIs the agent uses and set a quota cap. Foursquare Places is the specialist for point-of-interest work: category and proximity search, address-to-venue resolution (GeoTagging), and metadata like hours, photos, and ratings across 100M+ places. OpenWeatherMap is the weather default — an API key, a three-minute setup, a free tier that covers prototyping. The Time server (uvx mcp-server-time) needs no key and runs locally; install it for any agent that schedules across zones, because models reliably get DST and offset math wrong. Lock the agent to one map provider — mixing two invites coordinate-order bugs and attribution mistakes.
Common mistakes: confusing latitude/longitude order across APIs, forgetting that geocoding is approximate (store the formatted address alongside the coordinates), letting the model do timezone arithmetic instead of calling a Time tool (it will miss daylight-saving boundaries), and skipping rate-limit handling — maps APIs throttle hard, and an agent that retries aggressively can burn a day's quota in minutes. Start with Time: two minutes, no key, and it immediately fixes the class of bug where an agent schedules a call for 3 a.m. Then add Mapbox for one well-scoped job — a single route or geocode flow — and OpenWeatherMap when forecasts enter the picture. Let the agent loop only after each tool behaves on single calls.
All Maps, Location & Weather MCPs
5 MCPs ranked by popularity. Filter by attribute or search by name.
5 of 5 MCPs
| # | MCP | Tags | Setup | Complexity | Labels | |
|---|---|---|---|---|---|---|
| 1 | Time Current time and IANA timezone conversion — the first-party MCP that tells an agent what time it actually is. | time, timezone | 2 min | Low | ||
| 2 | Mapbox Official Mapbox MCP — geocoding, directions, isochrones, search, and tiles across the Mapbox API surface. | mapbox, maps | 5 min | Low | Official | |
| 3 | Google Maps Geocoding, place search, directions, and travel times from Google Maps. | maps, geocoding | 5 min | Low | ||
| 4 | Foursquare Places Official Foursquare Places MCP — POI search, GeoTagging, and rich place metadata across 100M+ places. | foursquare, places | 5 min | Low | Official | |
| 5 | OpenWeatherMap Real-time and forecast weather data via the OpenWeatherMap API. | weather, forecast | 3 min | Low |
Choose the right MCP
Quick decision guide based on your use case.
| If you need… | Start with |
|---|---|
| The agent needs the current time or timezone conversion | Use Time — no key, two-minute install |
| Geocoding, directions, or drive-time polygons | Use Mapbox |
| Point-of-interest search and venue enrichment | Use Foursquare Places |
| You specifically need Google's place data or travel-time estimates | Use Google Maps with a restricted, quota-capped key |
| Trip or event planning that mixes forecasts and timezones | Pair OpenWeatherMap with Time |
Top Maps, Location & Weather MCPs ranked
Detailed cards with setup time, complexity, and key labels.
Official
Official Mapbox MCP — geocoding, directions, isochrones, search, and tiles across the Mapbox API surface.
mapbox, maps, geocoding, directions
Geocoding, place search, directions, and travel times from Google Maps.
maps, geocoding, places, directions
Official
Official Foursquare Places MCP — POI search, GeoTagging, and rich place metadata across 100M+ places.
foursquare, places, poi-search, geocoding
Real-time and forecast weather data via the OpenWeatherMap API.
weather, forecast, openweathermap, lifestyle
Also in the ChatGPT Apps directory
2 Maps, Location & Weather brands are available as one-click ChatGPT Apps. These are not ranked alongside the editorial picks above — they're listings from chatgpt.com/apps surfaced here for brand-search continuity.
FAQ: Maps, Location & Weather MCPs
What is the best MCP server for geocoding and directions?
Mapbox. It is the official server, covers geocoding, directions, isochrones, and place search behind a single API token, and runs over stdio or streamable-http. Google Maps is the alternative when you specifically need Google's place data or travel-time estimates, but the servers around it are community-built and every call bills against your key.
Do I need an API key to give my agent weather data?
Yes — OpenWeatherMap authenticates with an API key, with a free tier that covers prototyping and setup in about three minutes. Have the agent pass a resolved location plus explicit units on every call; a bare city name like Springfield geocodes ambiguously and quietly returns the wrong town's forecast.
Why does my agent get timezone math wrong, and what fixes it?
Models do offset arithmetic from memorized rules and miss daylight-saving boundaries, so cross-zone meetings land an hour off twice a year. The Time server fixes it: no API key, a two-minute local install (uvx mcp-server-time), and tools for current time and IANA timezone conversion. Make the agent call it instead of reasoning about clocks.
Which MCP should I use for point-of-interest search?
Foursquare Places. The official server searches 100M+ places by category, feature, or proximity, resolves an address or coordinate to a venue (GeoTagging), and returns hours, photos, and ratings for enrichment. Use Mapbox or Google Maps for routing to the venue once Foursquare Places has found it.
Is it safe to give an agent my Google Maps API key?
Treat it like a payment credential: every call bills your account. Restrict the key to the specific APIs the agent uses, set daily quota caps and billing alerts, and add backoff so a retry loop cannot burn the quota in minutes. Never let the agent echo the key into chat or logs.