Provides tools for searching places using the Google Maps Places API and retrieving place photos, enabling location lookup, business information queries, and address validation.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Google Maps Places MCPfind coffee shops with outdoor seating near Central Park"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
google-maps-places-mcp
MCP server for Google Maps Places API - search for places and get photos.
Use Cases
Meeting coordination: Someone emails "Let's meet at Nando's near the office - what time works best for you?" → your AI assistant looks up the location, checks opening hours, and adds it to your calendar with the address.
Local recommendations: Ask "find a quiet café with WiFi near King's Cross for a 2-hour work session" → get places with ratings, hours, and photos to help you decide.
Address validation: Confirm or autocomplete partial addresses before sending mail or booking deliveries.
(These are just examples - any workflow that needs place search or business info can use this.)
Setup
1. Create Google OAuth credentials
Go to Google Cloud Console
Create a new project (or use existing)
Enable the Places API (New)
Go to APIs & Services → OAuth consent screen, set up consent screen
Go to APIs & Services → Credentials → Create Credentials → OAuth client ID
Choose Web application
Add
http://localhost:3000/callbackto Authorized redirect URIsNote your Client ID and Client Secret
2. Run the server
The server runs on http://localhost:3000 by default. Change with PORT=3001.
3. Add to your MCP client
Architecture
This server acts as an OAuth proxy to Google:
Server advertises itself as an OAuth authorization server via
/.well-known/oauth-authorization-server/registerreturns the Google OAuth client credentials/authorizeredirects to Google, encoding the client's callback URL in state/callbackreceives the code from Google and forwards to the client's callback/tokenproxies token requests to Google, injecting client credentials/mcphandles MCP requests, using the bearer token to call Places API
The server holds no tokens or state - it just proxies OAuth to Google.
Tools
Tool | Description |
| Search for places by text query (e.g., "coffee shops near me") |
| Get a photo URL for a place |
OAuth Scope
cloud-platform- Access to Google Cloud APIs (required for Places API New)
Contributing
Pull requests are welcomed on GitHub! To get started:
Install Git and Node.js
Clone the repository
Install dependencies with
npm installRun
npm run testto run testsBuild with
npm run build
Releases
Versions follow the semantic versioning spec.
To release:
Use
npm version <major | minor | patch>to bump the versionRun
git push --follow-tagsto push with tagsWait for GitHub Actions to publish to the NPM registry.