Skip to content
Elaichi Elaichi

Default

Google Maps

Connect Google Maps once and hand every teammate a governed MCP endpoint with 3 tools ready to call from Claude, ChatGPT, Cursor, or any MCP client, inside the same permissions they already have, with every call checked and logged.

Google Maps

Automations & dashboards

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 ship on the Black plan.

Automations

Put Google Maps work on a schedule.

A trigger starts a sequence of steps: call a Google Maps tool, transform the result, branch, wait, and ask a person when it matters.

Google Maps digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch routes compute routeses

    Google Maps

    1.4s
  3. Group by owner

    Transform

    0.1s
  4. Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Google Maps

    Queued

Collections and dashboards

Report on Google Maps without asking.

Collections hold your own data, written by an automation and read by a dashboard that refreshes on a schedule.

Google Maps health

Refreshed 4 minutes ago · every 15 minutes · from the routes compute routeses collection

Live

Routes compute routeses

1,284 ↓ 12%

Address validation validate addresses

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Routes compute routeses created

Last 14 days

By workspace

Share of activity

Engineering 34%

Product 27%

Support 21%

Sales 18%

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.

googlemaps_address_validation_validate_address

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).

googlemaps_address_validation_provide_validation_feedback

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.

googlemaps_routes_compute_routes

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.

How it works

From Google Maps account to governed MCP endpoint

Connect

Link a Google Maps account through Elaichi's hosted connect flow. Credentials are vaulted, so nobody, including the AI, ever sees them.

Compose

The connection becomes a toolbox instantly. Curate which Google Maps tools are exposed, rename them, or freeze arguments.

Authorize

Point Claude, ChatGPT, Cursor, or any MCP client at the one Elaichi endpoint and sign in with OAuth, governed by roles, restrictions, and audit logs.

Put your agents to work in the tools you already use

Start a 14-day Gold trial. Connect a product, curate a toolbox, and paste a governed MCP endpoint into Claude, ChatGPT, or Cursor in minutes.