MCP Google Maps

Created By
ArtixZa year ago
MCP Google Maps server that can be used by claude, cursor, chatgpt, etc.
Overview

what is MCP Google Maps?

MCP Google Maps is a Model Context Protocol (MCP) server that provides Google Maps functionalities such as places search, geocoding, directions, and more through the MCP interface.

how to use MCP Google Maps?

To use MCP Google Maps, install the package globally using npm and run the server with npx. Configure your MCP client with the necessary parameters including your Google Maps API key.

key features of MCP Google Maps?

  • Places Search
  • Place Details
  • Geocoding and Reverse Geocoding
  • Distance Matrix
  • Directions
  • Elevation Data
  • Static Maps Generation

use cases of MCP Google Maps?

  1. Searching for nearby places based on user location.
  2. Getting detailed information about specific locations.
  3. Converting addresses to geographic coordinates and vice versa.
  4. Calculating distances between multiple locations.
  5. Generating static map images for display in applications.

FAQ from MCP Google Maps?

  • What is the purpose of MCP Google Maps?

It provides a server interface to access various Google Maps functionalities easily.

  • How do I configure my MCP client?

You need to add specific parameters to your MCP configuration file, including your Google Maps API key.

  • Is there a limit on the number of requests?

Yes, you can set limits on requests per second and per day in the configuration.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ArtixZ
Star
0
Language
TypeScript
License
-
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago