Default
Google Maps MCP connector
The Google Maps connector lets Claude, ChatGPT, Cursor, and the Elaichi Agent validate street addresses and compute routes and drive times through Elaichi, with each request logged under the person who made it.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
3 tools
How to connect
How to connect Google Maps to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Google Maps once
-
Open Connections, choose Add connection, and pick Google Maps.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Google Maps API key. One person generates a token in Google Maps and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
Google Maps
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Google Maps to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Google Maps to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Google Maps to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Google Maps to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Google Maps through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Operations
Clean up shipping addresses before labels print
Paste a batch of customer addresses and have Google Maps confirm each one is real, deliverable, and formatted the way carriers expect, with corrections suggested where a unit number or postal code is missing.
-
Sales
Check drive time before booking a visit
Ask how long it takes to get from the office to a prospect's site at a given departure time, then pick a meeting slot that actually works.
-
Support
Confirm an address while the customer is on the line
Read back a corrected, validated address during a ticket so a replacement order goes to the right door the first time.
-
Logistics
Plan the day's delivery stops
Give the agent the morning's stops and get a route with distances and travel times between them, ready to hand to the driver.
-
Field service
Route technicians between appointments
Work out travel time between a technician's jobs so the schedule leaves room to get from one site to the next.
-
Data quality
Tell Google Maps when a correction was wrong
When a validated address turns out to be right or wrong in practice, send that feedback back to Google Maps so future checks improve.
Try asking
- “Validate these 40 delivery addresses and flag the bad ones.”
- “Compute routes from the depot to today's five stops.”
- “Which addresses failed validation for the Logistics team this week?”
AI tools
Google Maps tools for your AI agents
3 tools are ready to call through Elaichi's MCP endpoint the moment you connect Google Maps, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Google Maps gets you
6 screens from the product, each doing one job for your Google Maps account.
The agent
Ask about addresses and routes in plain words.
Type a question and get answers from live Google Maps address and route records.
- addresses
- routes
- waypoints
- validation results
Ask Elaichi to work across your apps.
Validate these 40 delivery addresses and flag the bad ones.
Compute routes from the depot to today's five stops.
Which addresses failed validation for the Logistics team this week?
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor share one endpoint.
Connect Google Maps from any MCP client over OAuth, no SDK, no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
3 Google Maps tools ready without custom code.
Browse every Google Maps tool name, resource and method in one catalog.
- Google Maps address validation validate address
- Google Maps address validation provide validation feedback
- Google Maps routes compute routes
ElaichiToolsToolboxes
Every team gets its own Google Maps toolbox.
Scope address validation and route tools to the teams that actually need them.
- Logistics
- Field Service
- Sales Ops
- Customer Support
ElaichiToolboxesShared connections
Teammates use Google Maps without seeing a credential.
See who connected each account and how many teams and members share it.
- Logistics EMEA
- Field Service US
- Sales Ops
- Support
ElaichiConnectionsAudit log
Every address check and route call is recorded.
Read when, who, what happened, type and resource for each Google Maps call.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule validates addresses and posts results back.
Six steps fetch Google Maps records, group them, draft a digest, then wait for approval.
Google Maps digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch addresses
Google Maps
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Google Maps
Queued
Collections and dashboards
Google Maps numbers computed, no model involved.
Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.
Google Maps health
Refreshed 4 minutes ago · every 15 minutes · from the addresses collection
Addresses
1,284 ↓ 12%
Routes
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Addresses created
Last 14 days
By team
Share of activity
Logistics EMEA 34%
Field Service US 27%
Sales Ops 21%
Support 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Google Maps to Claude?
Connect Google Maps in Elaichi first: you paste in your Google Maps API key, and there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in to Elaichi when Claude asks, and Google Maps address validation and routing are available in your conversation.
Does Google Maps work with ChatGPT and Cursor as well as Claude?
Yes. Once Google Maps is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent. You connect Google Maps once and every client you sign in to can use it.
What can an AI agent actually do with Google Maps?
Through this connector an agent can check whether a street address is real and complete, suggest the corrected version, and work out routes with distance and travel time between two or more places. It can also send feedback to Google Maps about whether a suggested address correction turned out to be right. It cannot search for businesses or edit anything in Google Maps, because this connector only covers address validation and routing.
Does connecting Google Maps give the AI unlimited use of my API key?
No. Requests to Google Maps run through the key the connecting person supplied, so anything that key cannot do, the agent cannot do either. Elaichi can narrow that further by turning off individual actions such as route computation or address feedback for a team, and it never widens what the key allows.
Can I stop an agent from doing certain things in Google Maps?
Yes. Restrictions in Elaichi work per action, so you can allow address validation while blocking route computation or validation feedback, for example. A blocked action is never shown to Claude, ChatGPT, or Cursor at all, so no prompt can reach it.
What happens to a Google Maps connection when someone leaves?
Offboarding the person in Elaichi ends their access to Google Maps at once, across every client they used. If they connected Google Maps and shared it with a team, the shared connection keeps working for everyone else. Disconnecting Google Maps once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client in one step.
Put Google Maps in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.