local-mcp: 2GIS, Yandex Geo and Google Places SEO server
local-mcp
A self-hosted MCP server on Cloudflare Workers for local SEO: organization search and cards in 2GIS, Yandex Geocoder and Google Places
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- Only reads public organization data from the three services; it does not change or publish anything
Install
Manual install
wrangler deployDeploys the Worker to your own Cloudflare account, normally triggered automatically by GitHub Actions on a push to main.
This is third-party code. Review the repository files before installing.
What it does
The server deploys to the owner's own Cloudflare Workers account and gives the agent ten tools across three sources: 2GIS Catalog API search and organization cards, a review summary and a raw API call; Yandex geocoding and organization search, which need two separate keys; and Google Places (New) text search, place details and reviews. The protocol is JSON-RPC 2.0 over HTTP POST, and instead of an auth header the secret is baked into the connector URL path. Deployment is automatic: a push to main runs GitHub Actions with wrangler deploy.
Who it is for. For people doing local SEO for a Russian business who want one MCP instead of three separate integrations with 2GIS, Yandex and Google.
Good fit when
- You need to compare an organization's card across 2GIS, Yandex and Google Places in one request
- You do local SEO and need coordinates, categories, reviews and hours for competitors
- You have your own Cloudflare account and keys for at least one of the three services
Not a fit when
- You have no Cloudflare Workers account: there is no public server, you deploy your own
- The 2GIS Catalog API key is currently issued by request only, so without it only part of the tools work
- You need analytics or the ability to edit an organization's card, not just search and read
Example request
Compare the cards of the three nearest coffee shops in 2GIS and Yandex: rating, hours, categoriesLimitations
A single-author project with 0 stars and one source file, src/index.js. You need your own keys for three services: DGIS_KEY (2GIS, currently issued by request), YANDEX_GEO_KEY and YANDEX_ORG_KEY (two separate Yandex keys), and GOOGLE_PLACES_KEY. Without a key, that specific tool returns a clear error instead of the whole server failing. It requires deploying to your own Cloudflare Workers with CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID secrets in GitHub Actions.
How to disable. Remove the server from your MCP client configuration and stop or delete the Worker in the Cloudflare dashboard.
MCP
- Transport
- http
- Authentication
- API key
| Environment variables | |
|---|---|
| DGIS_KEY secret | 2GIS Catalog/Places API key from dev.2gis.ru, currently issued by request. |
| YANDEX_GEO_KEY secret | Yandex HTTP Geocoder key for the ya_geocode tool. |
| YANDEX_ORG_KEY secret | A separate Yandex organization search API key for ya_org_search. |
| GOOGLE_PLACES_KEY secret | Google Places API (New) key from Google Cloud Console. |
| MCP_SECRET required, secret | The connector path secret, generated at deploy time. |
Security check
- Only reads public organization data from the three services; it does not change or publish anything
README in short
The Russian README describes a local-SEO MCP server on Cloudflare Workers using JSON-RPC 2.0 over HTTP POST, gives the connector URL with a path secret, tool tables for each of the three sources, the list of required keys and where to get them, the behavior without a key, and the GitHub Actions deploy process using wrangler-action.
FAQ
Can I use just one of the three services?
Yes, keys are set independently, and without a key that specific tool group returns an error saying the secret is missing.
How is the connector secured?
By a secret baked into the URL path; any other path returns 404.
Related
Official DataLens (Yandex) skills for Claude Code, Codex and OpenCode: SDK, HTML reports and RLS resolution
A Yandex Metrika MCP server generated from the API spec: 108 methods, 10 tools declared by default, transparent filters and response metadata
An open MCP server and agent skill set for SEO: keyword research, competitors, backlinks and site audits powered by DataForSEO
A Claude Code plugin for SEO audits: technical SEO, E-E-A-T, schema, local and AI search via parallel subagents