src ▸ site opened 0

Turn Google Maps into MCP tools

Give your AI agent Google Maps tools. Writ turns your Google Maps workflows into authenticated MCP tools your agent can call, taking real actions on your own account.

Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
claude_desktop_config.jsonMCP · writ-google-maps
json
{
  "mcpServers": {
    "writ-google-maps": {
      "url": "https://api.usewrit.app/mcp/your-workspace",
      "headers": { "Authorization": "Bearer wt_8f2c...a91" }
    }
  }
}
MCP server any client authenticated
new ▸ tool minted 01
02
create

No Google Maps MCP server yet? Build one in minutes

Record the Google Maps task once, or describe it to an AI session, and Writ turns it into an MCP tool your agent can call, taking real actions on your own Google Maps account.

  1. 1
    Record a Google Maps action once

    Open the recorder and search a place or area on Google Maps in a real browser. Writ captures the steps, login and 2FA included, into a workflow.

  2. 2
    Publish it as an MCP tool

    One click exposes the workflow as an MCP tool with a typed input schema, alongside a REST endpoint. Your agent picks it by its description.

  3. 3
    Call it from any MCP client

    Point Claude Desktop, Claude Code, Cursor, or any MCP client at your Writ server. The Google Maps tool acts on your own account and returns structured output.

Browse supported MCP clients, see what's possible on workflows, or search for another site. Free to start. See pricing.

gap ▸ no official mcp 02
03
why

Google Maps has no MCP server

Read-only website-to-MCP tools can summarize a Google Maps page, but they can't do anything on it. Writ turns the Google Maps workflows you build into MCP tools your agent calls to take real actions (search, extract, submit), authenticated, on your own Google Maps account.

Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.

tools ▸ actions named 03
04
named tools

Google Maps tools your agent can call

Each tool is a real Google Maps workflow with a typed input schema and structured output. Your agent picks the right one by its description.

{ }maps.search_placesSearch a place or area and return businesses with key fields.

Example tool schema

maps.search_places.jsonschema
json
{
  "name": "maps.search_places",
  "description": "Search a place or area and return businesses with key fields.",
  "input_schema": {
    "type": "object",
    "properties": {
      "query": { "type": "string", "description": "What to look up on Google Maps." }
    },
    "required": ["query"]
  }
}
wire ▸ any client 04
05
connect

Add the server to any MCP client

Copy the config into your client and authenticate with a wt_ key. Tools appear automatically.

Your key (wt_)
json
{
  "mcpServers": {
    "writ-google-maps": {
      "url": "https://api.usewrit.app/mcp/your-workspace",
      "headers": { "Authorization": "Bearer wt_8f2c...a91" }
    }
  }
}
Downstream caller (csk_)
json
{
  "mcpServers": {
    "writ-google-maps": {
      "url": "https://api.usewrit.app/mcp/your-workspace",
      "headers": { "Authorization": "Bearer csk_3a90...f4d" }
    }
  }
}
>_

Per-client setup. Step-by-step config for each client lives on the per-client pages: Claude Desktop, Claude Code, Cursor, Windsurf.

auth ▸ logged-in web 05
06
authenticated

Your agent acts on your own Google Maps account

Google Maps place pages are public; Writ renders them in real Chromium to capture details and reviews that load dynamically.

PersonasTOTP & mailbox OTP Scoped wt_ / csk_ keysStructured output

Collect Google Maps data you have the right to access and respect Google's Terms of Service and rate limits.

faq ▸ questions answered 07
08
faq

Google Maps MCP questions

Is there an official Google Maps MCP server?
Google Maps does not publish an MCP server. Writ lets you turn the Google Maps workflows you build (recorded, described, or discovered) into MCP tools your agent can call. They take real actions, not just read page text.
Are there ready-made Google Maps MCP tools I can install?
Record the Google Maps task once in the recorder, or describe it to an AI session, then publish it. Writ exposes it as both an MCP tool and a REST endpoint, usually in minutes.
How is this different from a read-only website-to-MCP tool?
Most website-to-MCP tools are readability crawlers that return page text. Writ tools act and transact: they log in, fill forms, click, extract, and complete multi-step Google Maps tasks, then return structured output your agent can use.
Does it work with Google Maps login and 2FA?
Google Maps place pages are public; Writ renders them in real Chromium to capture details and reviews that load dynamically. Because each MCP tool is a real browser workflow, it runs inside your own authenticated Google Maps session, with TOTP and mailbox-OTP two-factor handled by Personas.
Which MCP clients can use these Google Maps tools?
Any MCP-compatible client: Claude Desktop, Claude Code, Cursor, Windsurf, and others. Point the client at your Writ MCP URL and authenticate with a wt_ key (or a csk_ consumer key for downstream callers).
Is it allowed to use Google Maps this way?
Collect Google Maps data you have the right to access and respect Google's Terms of Service and rate limits. Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
rec ▸ ready

Give your agent Google Maps tools

Build a workflow, publish it as an MCP tool, and call it from any MCP client. Get started free.