Merge Unified's Google Maps integration Merge Agent Handler's Google Maps MCP server

Connect your AI Agents to Google Maps in minutes

Merge lets you securely connect your agents to Google Maps and thousands of tools instantly

Start building for free

Read docs

Google Maps

Learn more about Merge Agent Handler

Available tools

geocode

Convert a street address to geographic coordinates (latitude/longitude). Use components filter for disambiguation (e.g., 'country:US').

reverse_geocode

Convert geographic coordinates (lat/lng) to a street address. Use resulttype to filter (e.g., 'streetaddress', 'locality').

text_search

Search places by text query with optional location bias, type/price/rating filters. Pagination via pagetoken from pageinfo. Returns up to 20 results per page.

nearby_search

Search places near a lat/lng within radius. Max 20 results, no pagination. Use included_types to filter (e.g., 'restaurant', 'cafe').

get_place_details

Get place details by ID including hours, reviews, photos, contact info. Use textsearch or nearbysearch to find place IDs.

autocomplete

Get place autocomplete suggestions for partial text input. Returns place IDs and display text. Use location bias for better results.

get_place_photo_url

Get a photo URL from a photo resource name found in place details. Specify maxwidth or maxheight to control size (1-4800px).

compute_routes

Get directions between origin and destination. Supports place IDs, addresses, or lat/lng. Options: travel mode, waypoints, avoidance, departure time.

compute_route_matrix

Compute distance/duration matrix for multiple origins and destinations. Each location needs place_id, address, or lat/lng.

get_elevation

Get elevation in meters for one or more coordinates. Provide pipe-separated lat,lng pairs (e.g., '36.578,-118.292|36.240,-116.832').

get_time_zone

Get time zone for a latitude/longitude. Returns time zone ID, name, and UTC/DST offsets. Defaults to current time if no timestamp given.

validate_credential

Validate Google Maps credentials by making a lightweight geocoding call. Returns {success, message}.

View all tools by creating a free account See more tools

How to set up Merge Agent Handler

In an mcp.json file, add the configuration below, and restart Cursor.

Learn more in the official documentation ↗

1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11

Copy Code

Open your Claude Desktop configuration file and add the server configuration below. You'll also need to restart the application for the changes to take effect.

Make sure Claude is using the Node v20+.

Learn more in the official documentation ↗

1{
2  "mcpServers": {
3    "agent-handler": {
4      "command": "npx",
5      "args": [
6        "-y",
7        "mcp-remote@latest",
8        "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
9        "--header",
10        "Authorization: Bearer ${AUTH_TOKEN}"
11      ],
12      "env": {
13        "AUTH_TOKEN": "yMt*****"
14      }
15    }
16  }
17}

Copy Code

Open your Windsurf MCP configuration file and add the server configuration below.
Click on the refresh button in the top right of the Manage MCP server page or in the top right of the chat box in the box icon.

Learn more in the official documentation ↗

1{
2    "mcpServers": {
3      "agent-handler": {
4        "command": "npx",
5        "args": [
6          "-y",
7          "mcp-remote@latest",
8          "https://ah-api.merge.dev/api/v1/tool-packs/<tool-pack-id>/registered-users/<registered-user-id>/mcp",
9          "--header",
10          "Authorization: Bearer ${AUTH_TOKEN}"
11        ],
12        "env": {
13          "AUTH_TOKEN": "<ah-production-access-key>"
14        }
15      }
16    }
17  }

Copy Code

In Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows), run "MCP: Open User Configuration".

You can then add the configuration below and press "start" right under servers. Enter the auth token when prompted.

Learn more in the official documentation ↗

1{
2  "inputs": [
3    {
4      "type": "promptString",
5      "id": "agent-handler-auth",
6      "description": "Agent Handler AUTH_TOKEN", // "yMt*****" when prompt
7      "password": true
8    }
9  ],
10  "servers": {
11    "agent-handler": {
12      "type": "stdio",
13      "command": "npx",
14      "args": [
15        "-y",
16        "mcp-remote@latest",
17        "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
18        "--header",
19        "Authorization: Bearer ${input:agent-handler-auth}"
20      ]
21    }
22  }
23}

Copy Code

FAQs on using Merge's Google Maps MCP server

What is a Google Maps MCP?

It's an MCP server that connects your agents to Google Maps location services via tools. Your agents can invoke these tools to geocode addresses, search for nearby places, calculate routes and travel times, retrieve business details, and more.

Google Maps offers an official MCP server, but you can also use one from a third-party platform, like Merge Agent Handler.

How can I use the Google Maps MCP server?

The use cases naturally depend on the agent you've built, but here are a few common ones:

Address validation on record creation: When a new contact or order is submitted in a CRM or e-commerce platform, an agent geocodes the address through Google Maps to validate and normalize it, then writes the corrected version back to the record

Field service route planning: When a technician is assigned a set of service appointments for the day, an agent calls Google Maps to calculate the optimal driving sequence and estimated travel times, then sends the itinerary to the technician's mobile app

Location-based lead enrichment: When a new account enters a CRM, an agent uses Google Maps to identify nearby competitor locations or relevant points of interest around the account's address, and appends that context to the record for the sales team

Customer-facing store locator: When a customer asks support for the nearest service location, an agent calls Google Maps to find nearby branches, retrieves their hours and contact details, and replies with the closest options

What are popular tools for Google Maps's MCP server?

Here are some of the most commonly used tools:

geocode: converts a text address into geographic coordinates (latitude and longitude). Use this when an agent needs to standardize or validate a location before storing or displaying it

reverse_geocode: converts a set of coordinates into a human-readable address. Helpful when an agent receives raw GPS data and needs to translate it into a usable location string

search_places: searches for places matching a text query near a given location, returning names, addresses, and ratings. Good for workflows that need to surface relevant businesses or landmarks based on a user's context

get_place_details: retrieves detailed information about a specific place, including hours, phone number, website, and reviews. Call this when an agent needs to present complete business info to a user or enrich a record

get_directions: calculates turn-by-turn directions between two or more points, with options for travel mode and departure time. Useful for agents that build itineraries or assign field tasks based on real driving routes

distance_matrix: computes travel distances and estimated times between multiple origin and destination pairs in a single call. Use this when an agent needs to rank or assign locations by proximity across a batch of records

What makes Merge Agent Handler's Google Maps MCP server better than alternative Google Maps MCP servers?

Building your own Google Maps MCP integration or relying on a community server means taking on auth, monitoring, and access control yourself. Here's why Merge Agent Handler is a better option:

Enterprise-grade security and DLP: Merge Agent Handler includes built-in data loss prevention controls that let you block or redact sensitive fields before they reach an agent. For Google Maps, this means you can prevent precise location data, route histories, and place details tied to specific users or assets from being exposed even when the agent has broad access

Managed authentication and credentials: Merge stores and manages your Google Maps API keys on your behalf. You never pass raw credentials into an agent or risk key exposure through misconfigured environment variables

Real-time observability and audit trail: Every tool call made against Google Maps is logged: the tool name, query parameters, and response data. You get a complete record of what the agent looked up or computed without writing any logging code yourself

Tool Packs and controlled access: Tool Packs let you bundle specific Google Maps tools with tools from other connectors into a single MCP endpoint, scoped to a specific use case. An agent gets exactly the tools it needs, nothing more

How can I start using Merge Agent Handler's Google Maps MCP server?

You can take the following steps:

1. Create or log into your Merge Agent Handler account and navigate to Tool Packs (collections of connector tools scoped to a specific use case).

2. Create a new Tool Pack, then find and enable the Google Maps connector. Pick the tools your use case requires: read tools like geocode, search_places, and get_directions cover most location lookup and routing workflows.

3. Add a Registered User inside the Tool Pack. This is the identity context under which your agent operates. Merge generates a unique MCP URL scoped to this user once it's created.

4. From the Registered User detail page, connect Google Maps by entering your API key. Merge stores and manages that credential going forward.

5. Copy the MCP URL from the Tool Pack detail page and generate an API key from Settings. You'll need both to connect your agent.

6. Add the MCP server to your agent or IDE using the MCP URL and API key. Your Google Maps tools are now accessible through that endpoint.