MCP Google Map Server

Created By
cablatea year ago
A powerful Model Context Protocol (MCP) server providing comprehensive Google Maps API integration with LLM processing capabilities.
Overview

What is MCP Google Map Server?

MCP Google Map Server is a powerful Model Context Protocol (MCP) server that provides comprehensive integration with the Google Maps API, enhanced with LLM processing capabilities.

How to use MCP Google Map Server?

To use the MCP Google Map Server, install it via NPM and run it from the command line. For integration with Dive Desktop, add the MCP server configuration in the application settings.

Key features of MCP Google Map Server?

  • Location search and information retrieval
  • Geocoding and reverse geocoding
  • Detailed place information

Use cases of MCP Google Map Server?

  1. Integrating Google Maps functionalities into applications.
  2. Providing location-based services and information retrieval.
  3. Enhancing applications with geocoding capabilities.

FAQ from MCP Google Map Server?

  • How do I set up the Google Maps API?

You need to create a project in Google Cloud Console, enable Google Maps API services, obtain an API key, and set the GOOGLE_MAPS_API_KEY environment variable.

  • Is there a community for contributions?

Yes! Community participation is welcome, and you can contribute by reporting issues, submitting pull requests, or providing suggestions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
cablate
Star
25
Language
TypeScript
License
MIT 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