Google Maps MCP Cloudrun MCP Server

Google Maps MCP Cloudrun MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Google Maps MCP Server for Cloud Run - Simple Public Access.

What you get

A Google Maps Model Context Protocol (MCP) server designed for deployment on Google Cloud Run with public access. This server provides Google Maps functionality to Claude Desktop clients through a secure, rate-limited API.

• Route Calculation — Optimal driving routes with real-time traffic data
• Route Comparison — Compare multiple routing alternatives with different options
• Live Traffic — Current traffic conditions and travel time analysis
• Cost Estimation — Trip cost calculations including fuel and toll estimates
• Public Access — No authentication required for easy sharing
• Rate Limiting — 50 requests per hour per IP address

Configuration and credentials

You will need 3 environment variables: GOOGLE_MAPS_API_KEY, SERVICE_URL, YOUR_PROJECT_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Google Cloud Platform account with billing enabled - Google Cloud CLI (gcloud) installed and configured - Node.js 18+ for local development - Google Maps API key with required APIs enabled

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by arunrajece; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the google maps mcp cloudrun mcp server does with a few real requests.