Google Maps MCP server: places and routes for every agent

Place data works best when the agent resolves the location before comparing options. A business name can exist in several cities. Give the city, address or Maps URL, then ask for the resolved Place ID and source link before route calculations.

For planning, distinguish a travel estimate from an appointment. An agent can compare walking and driving duration to a meeting location, but the answer is not live navigation. Weather context can help a planning decision without changing a calendar event.

Experimental resolution tools should be treated as discovered capabilities rather than a permanent universal catalog. If a tool is not available for the authorized account, the agent should say so and use a supported lookup instead of inventing coordinates or route results.

Google Maps MCP server options

Google’s Grounding Lite documentation defines the supported place, route and weather surface. google-maps-mcp and HasData’s server are separate community routes with their own data and credential choices; do not assume equivalent output.

A direct official connection is simpler for Maps-only work. AIPx adds another service processing location requests, while making the connection reusable alongside calendar or spreadsheet tools. Follow the provider’s attribution requirements when presenting results.

Connect Google Maps to Claude, Claude Code, Cursor or Codex

Choose Google Maps and complete its supported OAuth connection. Google service enablement, credentials, quotas and any provider billing requirements remain separate from AIPx.

1. Open the AIPx dashboard, choose Google Maps under Integrations and complete its connection form or authorization.
2. Create an MCP agent, enable that connection and choose the tools this particular agent needs. Save the rules before opening your AI client.
3. Copy the agent’s complete URL. The examples below use AGENT_ID; replace it with the actual value from your dashboard.

An endpoint identifies the AIPx agent, not a provider API key. Client authentication to AIPx is separate from connecting Google Maps; adding the URL does not grant extra provider permissions. Our MCP gateway guide explains how several approved connections can share that endpoint.

Connect Claude to Google Maps

In Claude, open Customize → Connectors and add a custom connector with your AIPx URL. Continue through AIPx sign-in, then check the tools available in a conversation. Custom connector access depends on account and workspace policy; administrators can restrict it. The Claude MCP setup guide covers the current controls. A direct vendor connection can be simpler when Google Maps is the only service you need.

Google Maps MCP in Claude Code

claude mcp add --transport http aipx https://dash.aipx.run/mcp/AGENT_ID

Authorize with /mcp, then resolve the intended place before asking for a route. Show the Place ID, source link and travel mode. Claude Code MCP setup covers endpoint registration.

Google Maps MCP in Cursor

Add this server to .cursor/mcp.json for the project or ~/.cursor/mcp.json for your user:

{
  "mcpServers": {
    "aipx": { "url": "https://dash.aipx.run/mcp/AGENT_ID" }
  }
}

Sign in to AIPx from Cursor and inspect the available place-resolution tools. Start with one address so a similarly named place is not selected silently. The Cursor MCP guide covers configuration.

Google Maps MCP in Codex

codex mcp add aipx --url https://dash.aipx.run/mcp/AGENT_ID
codex mcp login aipx
codex mcp list

Codex uses the HTTP endpoint and browser OAuth; it does not need a copy of the Google Maps credential in its config. See Codex MCP setup for TOML configuration and project trust requirements.

Where ChatGPT supports custom MCP, use the endpoint for places, weather and driving or walking estimates. It does not provide live navigation. ChatGPT MCP setup explains client and administrative access requirements.

Scope Maps context per agent

A meeting planner can use place search and route estimates while a weather-only assistant needs only weather lookup. Hide location tools that are irrelevant to the agent’s job; a read tool still sends its query to an external service.

Read tools generally default to Allow. If you also connect a calendar, keep event changes on Confirm or Hide separately. Maps lookup does not need calendar mutation authority. MCP access control lets you make that distinction at the account and tool level.

Google Calendar supplies a meeting address, Google Sheets can hold a venue shortlist, and Gmail can provide the invitation. Use Exa for broader source research while Maps remains the place-specific tool.

Maps route, attribution and billing limits

Driving and walking estimates are supported; transit navigation, live traffic and turn-by-turn instructions are outside this advertised surface. Say which travel mode was used and avoid describing a duration estimate as a guaranteed arrival time.

Google quotas and billing are independent of AIPx Free. Place and route results also need the attribution the provider requires. A resolved location should be checked before a route is used in an important plan, particularly where several places share a name.

Browse all MCP integrations to choose another connection for this agent.

The Google Maps connection can use AIPx Free with 3 active accounts and 1 agent; check AIPx pricing for gateway plans and keep provider or client charges separate.