Can my team share one Google Maps connection?

Yes. One person connects Google Maps with the API key and shares the connection with a team in Elaichi, and nobody else ever sees or handles the key. Each teammate still signs in to Elaichi as themselves, so every address check and route request in the audit log names the person who made it.

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.

Connect on Elaichi How to connect

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

All categories

Google Maps

1Password

360learning

7shifts

Acquire

Active Ants

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.

Google Maps MCP connector for 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.

Google Maps MCP connector for 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.

Google Maps MCP connector for 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.

Connect Google Maps on Elaichi See pricing

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?”

See all 3 Google Maps tools below

Compare

Elaichi vs Zapier MCP vs Composio for Google Maps

All three can connect Google Maps to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Google Maps, by what to check
What to check	Elaichi	Zapier MCP	Composio
Where the AI connects	One address for the whole organization. `https://api.elaichi.ai/mcp`	A server per member, created at sign-in.	An MCP endpoint per team, or an SDK.
Control over Google Maps tools	Allow or restrict single Google Maps tools, per role or user.	App and action restrictions on the account.	Role permissions, down to the action.
Record of calls	One audit entry per Google Maps call.	A History tab of tool calls.	A log of every tool call.
Single sign-on	SAML or OIDC, plus SCIM, on Gold.	SAML on Enterprise.	SAML and OIDC on Enterprise.
Price	$15 per user per month.	2 tasks per successful call.	Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

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.

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 clients

Claude

ChatGPT

Cursor

Copy the endpoint

https://api.elaichi.ai/mcp

Client	Connected by	Status	Last used
Claude	E Emily Carter	• Connected	4 minutes ago
Cursor	M Megan Brooks	• Connected	2 hours ago
ChatGPT	R Ryan Hayes	• Connected	Yesterday

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

ElaichiTools

Tool	Action	Description
Google Maps address validation validate address	Validate	Validate a postal address using Google Maps Address Validation API. Returns the validation result including verdict flags, the post-processed address with components, geocode with coordinates and place ID, deliverability metadata, and USPS data for US/PR addresses. Required: address (with addressLines).
Google Maps address validation provide validation feedback	Action	Provide feedback about the outcome of a sequence of address validation attempts in Google Maps Address Validation API. This should be the last call made after a sequence of validation calls for the same address, and should be called once the transaction is concluded. Returns an empty 204 response on success. Required: conclusion, responseId.
Google Maps routes compute routes	Action	Compute routes between an origin and a destination using the Google Routes API. Returns: duration, distanceMeters, polyline, legs, warnings, routeLabels. Required in body: origin, destination. Select fields with field_mask.

Toolboxes

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

ElaichiToolboxes

Name	Source template	Tools	Created
Logistics toolbox Google Maps · routes and waypoints	Google Maps starter	18	Mar 4, 2026
Field Service toolbox Google Maps · technician routes and stops	—	9	Mar 2, 2026
Sales Ops toolbox Google Maps · account addresses and territories	—	24	Feb 27, 2026
Customer Support toolbox Google Maps · delivery address corrections	Google Maps starter	6	Feb 19, 2026
Finance toolbox Google Maps · billing address validation	—	31	Jan 30, 2026
Data Quality toolbox Google Maps · addresses and validation feedback	—	12	Jan 22, 2026

Shared 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

ElaichiConnections

Connection	Scope	Status	Access
GO Google Maps (Logistics EMEA) Connected by Emily Carter	Personal	• Active	1 team · 6 members
GO Google Maps (Field Service US) Connected by Jake Morgan	Organization	• Active	3 teams · 24 members
GO Google Maps (Sales Ops) Connected by Megan Brooks	Organization	• Active	2 teams · 11 members
GO Google Maps (Support) Connected by Tyler Reed	Personal	• Needs re-auth	1 team · 3 members
GO Google Maps (Data Quality) Connected by Ryan Hayes	Personal	• Active	Not shared
GO Google Maps (Finance) Connected by Ashley Parker	Personal	• Active	2 teams · 9 members

Audit 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 log

When	Who	What happened	Type
2 minutes ago Mar 6, 2026, 3:10 PM	E Emily Carter emily.carter@northwind.io	Restriction Created	Access
8 minutes ago Mar 6, 2026, 3:04 PM	J Jake Morgan jake.morgan@northwind.io	Restriction Updated	Access
14 minutes ago Mar 6, 2026, 2:58 PM	M Megan Brooks megan.brooks@northwind.io	Role Assigned	Access
20 minutes ago Mar 6, 2026, 2:52 PM	T Tyler Reed tyler.reed@northwind.io	Google Maps Users Updated	MCP
26 minutes ago Mar 6, 2026, 2:46 PM	R Ryan Hayes ryan.hayes@northwind.io	Google Maps Addresses Created	MCP
32 minutes ago Mar 6, 2026, 2:40 PM	A Ashley Parker ashley.parker@northwind.io	Google Maps Addresses List	Toolbox

Launching 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 Emily Carter

Run now

✓

Schedule

Every weekday at 8:00 AM

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

Live

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

Browse all 600+ connectors →

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.

Does the Google Maps MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Google Maps is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Google Maps?

Yes. Both let Claude, ChatGPT or Cursor use Google Maps. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Google Maps call.

How is Elaichi different from Composio for Google Maps?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Google Maps: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Google Maps in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Connect Google Maps Talk to us

Works with: and any other MCP client, or the Elaichi Agent.
When the trial ends: Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.