Sign in Book a demo
Back to Tools
Search API Key BYOCPro
Build Your Agent View Google Maps Docs
google-maps logo

Google Maps MCP Tools for AI Agents

Let an agent get directions between addresses or latitude and longitude coordinates through Arcade's MCP gateway.

Available Tools

3 tools available in this integration

GoogleMaps.GetDirections

Get directions between two places from Google Maps.

GoogleMaps.GetDirectionsBetweenAddresses

Get directions from Google Maps.

GoogleMaps.GetDirectionsBetweenCoordinates

Get directions from Google Maps.

Why agent-optimized tools matter

Built for intent, not API schemas

Ask the agent to "get driving directions from our office to the client site." Arcade picks the right Google Maps action without guessing whether the request uses places, addresses, or coordinates.

Up to 100x fewer tokens

Google Maps direction responses return the route information needed for the request instead of making the agent load a broader map or places dataset into the model.

Complete the workflow end to end

Read the request, identify the origin, identify the destination, request directions, and return the route through one toolkit designed around the complete directions task.

Make actions predictable and controlled

Arcade tools return structured results and useful errors across users and runs. Teams can apply scope restrictions, redaction, and approval policies so agents follow the same controls every time.

Securing Google Maps

The more capabilities agents get, the more useful they are. However, more capabilities bring more risks of undesired effects such as data loss and exfiltration.

This is why Arcade provides you with contextual rules that dictate how and when a tool is allowed to run. Arcade’s contextual access lets you govern tool visibility and behavior at every stage of execution and control who can see a tool, what inputs are allowed, and what comes back.

Learn about Contextual Access Policies

For Google Maps, you can implement some of these policies:

Access when tools are listed for a user
  • Decide which tools an agent is allowed to see at all. A tool that is never listed cannot be called, whoever is asking.
Pre-execution before each tool call
  • Inspect the inputs a call is about to run with, and block it or send it for human approval when they fall outside what the agent should do unsupervised.
Post-execution after the tool returns
  • Redact street numbers and apartment or unit details from GoogleMaps.GetDirectionsBetweenAddresses results before the model sees them, so an agent cannot retain precise residential locations in its context.
  • Strip exact latitude and longitude from GoogleMaps.GetDirectionsBetweenCoordinates results before the model sees them, so route guidance does not expose a person's precise location.

How to use Google Maps with your agent

Pick your MCP client below and follow the setup to connect Google Maps and start asking for directions.

Your questions, answered

A Google Maps MCP server exposes directions capabilities as structured tools that an AI agent can call through the Model Context Protocol. With Arcade, an agent can request directions between places, addresses, or coordinates.

This is not a Google first-party MCP server. Arcade hosts the Google Maps integration and adds the runtime around it, including credential brokering, approval and redaction policies, and access from supported clients.

Arcade agents can get directions between two places, between street addresses, or between latitude and longitude coordinates. The integration is read-only and does not search places, create routes, or change Google Maps data.

Arcade uses a shared API key or secret configured once for the integration. That credential must have access to the Google Maps directions capability; this integration does not use a separate per-user OAuth permission grant.

No. One shared API key or secret is configured once and brokered by Arcade rather than handed to the model, so users do not each connect an individual Google Maps account.

Yes. Contextual Access policies can require human approval before a directions request, although all available Google Maps actions are read-only and do not modify data. The call proceeds only after the policy's conditions have been satisfied.

Arcade proxies Google Maps API calls and does not persist your content as part of normal tool execution. The shared credential is brokered and stored encrypted at rest, and the model never receives it.

Any framework or client that can connect to Arcade's MCP gateway or tool APIs works, including LangChain, OpenAI Agents, CrewAI, Claude Desktop, Claude Code, Cursor, Visual Studio Code, Microsoft Copilot Studio, and GitHub Copilot.

Arcade continues using the shared credential while it remains valid. If the key or secret is revoked, rotated, or can no longer be used, directions calls stop until the credential is reconnected or updated.

Google Maps platform quotas and rate limits apply to directions requests made through Arcade. The integration does not remove or replace limits enforced by Google Maps.

Ready to actually ship your agent?

Connect your agent to Google Maps with a shared API key, agent-optimized tools and approval controls for consequential actions.

Build Your Agent Read the Google Maps Quickstart