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
Payai X402 Tools

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago