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.
{
"mcpServers": {
"writ-google-maps": {
"url": "https://api.usewrit.app/mcp/your-workspace",
"headers": { "Authorization": "Bearer wt_8f2c...a91" }
}
}
} 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.
- 1Record 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.
- 2Publish 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.
- 3Call 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.
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.
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
{
"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"]
}
} Add the server to any MCP client
Copy the config into your client and authenticate with a wt_ key. Tools appear automatically.
{
"mcpServers": {
"writ-google-maps": {
"url": "https://api.usewrit.app/mcp/your-workspace",
"headers": { "Authorization": "Bearer wt_8f2c...a91" }
}
}
} {
"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.
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.
Collect Google Maps data you have the right to access and respect Google's Terms of Service and rate limits.
Other ways to work with Google Maps
Google Maps MCP questions
Is there an official Google Maps MCP server?
Are there ready-made Google Maps MCP tools I can install?
How is this different from a read-only website-to-MCP tool?
Does it work with Google Maps login and 2FA?
Which MCP clients can use these Google Maps tools?
Is it allowed to use Google Maps this way?
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.