gmap-place-saver

Resolve a place from a social or Google Maps URL (or free text), confirm one candidate, and save it to the correct regional Google Maps saved list — with optional source/recommendation notes. Ships as an MCP server (usable by any MCP-capable agent) plus a CLI.

It automates the manual flow of "I saw a place on Instagram/Threads/Facebook → which of my regional saved lists does it belong in → save it there → keep the source link and why it was recommended."

How it works

resolve_place(url|text)  ->  ONE candidate + a reusable savePayload   (no writes)
        |  (you/the agent confirm the candidate)
        v
save_place(savePayload)  ->  saves to the EXACT regional list
        |  (optional)
        v
attach_note(...)         ->  note on the exact place, else a local sidecar record

Resolution prefers a fast, cache-friendly path: high-confidence social posts (place name + address + region) resolve from metadata in tens of milliseconds and skip the browser. Weaker cases fall back to a Playwright lookup on Google Maps using a persistent, logged-in browser profile.

Requirements

• Node.js >= 18 (uses the global fetch).

• A Google account and a persistent Chromium profile logged into it (see One-time login).

• Playwright's Chromium: npx playwright install chromium.

Install

git clone https://github.com/bolin8017/gmap-place-saver.git
cd gmap-place-saver
npm install
npx playwright install chromium
cp .env.example .env   # then edit GOOGLE_MAPS_PROFILE

One-time login

Saving to personal lists requires a logged-in Google session. Create one once into a persistent profile (needs a display — a desktop, or Xvfb/noVNC on a server):

GOOGLE_MAPS_PROFILE=/path/to/google-maps-profile npm run login

Sign in, open Google Maps, then press Enter. Every later run reuses that profile headlessly. No Google credentials are ever passed to or stored by this tool.

Headless server (no display): use the noVNC wrapper, which starts a virtual display and exposes it in your browser:

sudo apt-get install -y xvfb x11vnc novnc websockify   # one-time prereqs
GOOGLE_MAPS_PROFILE=/path/to/google-maps-profile ./scripts/login-server.sh

It prints a 127.0.0.1:6080 noVNC URL (tunnel it over SSH), where you sign in; then press Enter in the terminal to save and shut everything down. Tool paths are overridable via env (X11VNC, NOVNC_PROXY, NODE_BIN, DISPLAY_NUM, ports).

Configuration

All paths and tuning come from environment variables (see .env.example). Nothing is hardcoded.

Region config

Routing is driven by a JSON file whose keys are your Google Maps saved-list names and whose values are address substrings that route an address to that list. Ship your own (kept private — it is gitignored); see config/region-lists.example.json:

{
  "Taipei": ["台北市", "臺北市", "新北市"],
  "Kaohsiung": ["高雄市"],
  "Hong Kong": ["香港"]
}

If a place's region is ambiguous or its list is missing, the tool asks for confirmation or fails clearly — it never silently saves to the wrong list.

Use it from an AI agent (MCP)

The server is named gmap and speaks MCP over stdio. Point your agent at mcp/server.js with the env it needs.

Claude Desktop — claude_desktop_config.json:

{
  "mcpServers": {
    "gmap": {
      "command": "node",
      "args": ["/absolute/path/to/gmap-place-saver/mcp/server.js"],
      "env": {
        "GMAP_HOME": "/absolute/path/to/gmap-place-saver",
        "GOOGLE_MAPS_PROFILE": "/absolute/path/to/google-maps-profile"
      }
    }
  }
}

Claude Code:

claude mcp add gmap -- node /absolute/path/to/gmap-place-saver/mcp/server.js
# then set GMAP_HOME and GOOGLE_MAPS_PROFILE in the server's environment

Generic MCP / Hermes (mcp_servers) — a real, working example:

mcp_servers:
  gmap:
    # Use an ABSOLUTE node path. With nvm it is version-specific, e.g.
    #   /home/<you>/.nvm/versions/node/v20.19.0/bin/node
    command: /home/<you>/.nvm/versions/node/v20.19.0/bin/node
    args:
      - /path/to/gmap-place-saver/mcp/server.js
    env:
      # GMAP_HOME is the data dir: caches, logs, sidecar, and the default
      # config/region-lists.json resolve under it. Point it at an existing
      # data dir to reuse your caches AND your real saved-list config.
      GMAP_HOME: /path/to/your/gmap-data-dir
      GOOGLE_MAPS_PROFILE: /path/to/google-maps-profile
      # Optional: set explicitly if your region config lives elsewhere.
      GMAP_REGION_CONFIG: /path/to/your/region-lists.json
    timeout: 180
    connect_timeout: 60

PATH and HOME are inherited automatically, so Playwright finds its browser cache and yt-dlp (if installed) works. After editing the config, reload without restarting the gateway by sending /reload-mcp in Hermes.

Tools

CLI

gmap-place resolve '<instagram/maps url | place text>'
PLACE_QUERY='…' LIST_NAME='Taipei' EXPECTED_NAME='…' DRY_RUN=1 gmap-place save
EXPECTED_NAME='…' LIST_NAME='彰化' SOURCE_URL='…' RECOMMENDATION='…' gmap-place attach
EXPECTED_NAME='…' LIST_NAME='彰化' gmap-place clear-note
gmap-place regions
gmap-place benchmark 100

Safety guarantees

• A candidate is always confirmed before any save (resolve and save are separate).

• Saves go only to the exact matching regional list — never a silent fallback.

• A note is attached only when the page title and the note field's nearest ancestors both confirm the exact place; otherwise it is written to a local sidecar JSONL record or refused.

• No Google credentials are requested or stored; a persistent profile is used.

• Tool output is compact JSON with privacy-safe snippets only.

Development

npm test            # unit tests + MCP integration test + syntax gate
npm run smoke:resolve   # needs network (and the profile for the slow path)
npm run mcp         # run the MCP server on stdio

Architecture: pure logic (config, social parsing, note scoring, recommendation) lives in small unit-tested modules; browser automation (candidate, save, note) are importable async functions; the MCP server and CLI both call the same core — no child-process spawning between layers.

License

MIT