location-platform
Integrates with Google Maps Timeline and Location Sharing to provide tools for querying historical visits, trips, activities, distance traveled, and live location data, including place names and dwell times.
Provides optional integration with OpenAI Secure MCP Tunnel services to connect ChatGPT to the MCP servers via an outbound-only connection without exposing services to the internet.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
📍 location-platform
Ask your AI assistant where you've been — and where you are right now.
Self-hosted MCP servers that turn your Google Maps Timeline and live location into tools for Claude, ChatGPT, or any MCP client.
Why
Google stopped offering Timeline on the web, and your location history now lives only on your phone (plus an encrypted cloud backup). This project pulls that history back out, keeps it on your own server, and lets an LLM answer questions about it — alongside a separate live feed for "where am I right now?".
Related MCP server: Google Workspace MCP Server
What you can ask
"Where was I last Tuesday around 3pm?" →
where_was_ifinds the visit or trip covering that moment.
"How much time did I spend at the gym in September?" →
search_places+time_at_placetotals every visit.
"Summarize my week." →
summarize_weekreturns days, top places, distance, and how you got around.
"When was the last time I went to that taco place downtown?" →
visit_historylists every visit, newest first.
"How far did I drive this month vs. walk?" →
distance_traveledbreaks it down by activity.
"Where am I right now, and have I moved since noon?" →
where_am_i+movement_sincefrom the live feed, with data age shown.
How it works
flowchart LR
subgraph google["Google"]
TB[(Timeline<br/>cloud backup)]
LS[(Maps Location<br/>Sharing)]
end
subgraph server["Your server (Docker)"]
TS[timeline-sync<br/><sub>Python · every 6 h</sub>]
TJ[/Timeline.json/]
TM[timeline-mcp<br/><sub>13 tools</sub>]
LP[live poller<br/><sub>every 60 s</sub>]
LD[(live.sqlite)]
LM[live-location-mcp<br/><sub>5 tools</sub>]
AUTH{{OAuth 2.1}}
end
TB --> TS --> TJ --> TM
LS --> LP --> LD --> LM
TM & LM --- AUTH
AUTH --> C[Claude]
AUTH --> G[ChatGPT]History and live are deliberately two separate systems. Timeline is Google's semantic reconstruction (visits, trips, activities, Place IDs) and arrives hours late. Live Location Sharing is raw point observations, seconds old. They live in separate databases behind separate MCP servers and are never merged. The model picks the right tool, and every answer says how old its data is.
Features
🗺️ Full Timeline history | Syncs straight from Google's encrypted Timeline backup (no phone export, no Takeout) and follows every backup corpus, so nothing is cut off. |
🏷️ Real place names | Resolves Place IDs to names automatically after each sync. |
📡 Live location | Polls Google Maps Location Sharing through a dedicated recipient account. The session refreshes itself with cookie rotation and a persistent browser profile. |
🔁 Hands-off re-auth | When Google revokes the Timeline token, a persistent browser signs back in. The password is sealed by the host's TPM 2.0 ( |
🔐 Two auth layers | Google credentials never leave the server. MCP clients get only short-lived, audience-bound OAuth 2.1 tokens (RFC 9728 discovery, PKCE, JWKS verification). |
🎚️ Precision controls | Three levels with a per-server cap on what an LLM may see: |
🧾 Logs that can't leak | Structured logs with automatic redaction of tokens, cookies, keys, and anything that looks like a coordinate. |
🧪 Synthetic by default | Every test and fixture uses invented coordinates. A leak scanner checks the repo for secrets and real locations. |
🐳 One | OAuth server, both MCP servers, the poller, the sync scheduler, and noVNC browser views. Ports bind to |
💬 ChatGPT without exposure | Optional OpenAI Secure MCP Tunnel services: an outbound-only connection, with nothing published to the internet. |
Tools
Tool | |
| A point in time |
| A day or range |
| Digests |
| Find a place |
| Total dwell time |
| Radius search |
| Movement |
| Distance by mode |
| Data freshness |
Tool | |
| Latest fix |
| Points in a window |
| Nearest fix to a time |
| Distance and moves |
| Poller health |
Every tool is read-only and annotated as such. There is no SQL, file access, or bulk-export tool.
Quick start
Try it with synthetic data. No Google account needed.
git clone --recurse-submodules https://github.com/blakepennel/location-platform.git
cd location-platform
npm install
cd timeline-sync && python -m venv .venv && .venv/bin/pip install -e ".[dev]" && cd ..
cp .env.example .env
npm run seed # invented Timeline + live observations
npm run dev # OAuth :8700 · timeline-mcp :8701 · live-location-mcp :8702Point an MCP client at http://localhost:8701/mcp or http://localhost:8702/mcp. It discovers
the OAuth server and opens a sign-in page. For Claude Code, the stdio transport skips OAuth
entirely; see DEVELOPMENT.md.
Running it for real (a home server, your own Google data):
docker compose up -d --buildDOCKER.md walks through the one-time Google steps, the noVNC browser logins, TPM setup for automatic re-auth, and connecting Claude and ChatGPT.
Project layout
location-platform/
├── timeline-sync/ Python · syncs + decrypts the Timeline backup (wraps arkenoi/timeline-export)
├── timeline-mcp/ TypeScript · historical MCP server over its own SQLite index
├── live-location-mcp/ TypeScript · live poller + MCP server
├── mcp-auth/ OAuth 2.1 resource-server verifier + local dev authorization server
├── shared/ logging/redaction, time/geo, sqlite, HTTP host
├── schemas/ export contract + status JSON schemas
├── tools/ dev runner, e2e harness, seed data, leak scanner, re-auth driver
└── docker/ container entrypoints (noVNC, sync loop, Google browser)Testing
npm test # 246 Node + ~125 Python tests
npm run test:e2e # full stack: OAuth + both servers + a real MCP client
npm run leak-scan # secrets and real-coordinate scanDocs
Diagrams and data flow | |
Deploying on a server | |
Local setup and real Google onboarding | |
The two authentication layers | |
What's protected, and from whom | |
Per-project READMEs |
Disclaimer
This is a personal project that reads your own data through undocumented Google endpoints: the Timeline cloud backup via arkenoi/timeline-export (a pinned submodule under its own MIT license), and Maps Location Sharing. Google can change or block them at any time, and using them may conflict with Google's Terms of Service. It is not affiliated with or endorsed by Google. Use it only with accounts you own, at your own risk.
License
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Hosted MCP server with managed OAuth for 15+ toolkits: Google Workspace, Fitbit, Oura, Kalshi, etc.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Hosted MCP server for marketing agencies: connect Google Ads, GA4, Search Console, Meta, LinkedIn and more to Claude or ChatGPT. Pull reports and make changes via OAuth login, no setup.
Multi-tenant hosted MCP server for Oura Ring — 21 read-only tools, OAuth per user.
Related MCP Servers
- AlicenseBqualityBmaintenanceA local-first MCP server that enables AI agents to read user-authorized Google Health API v4 data from Fitbit, Pixel Watch, and partners via OAuth, with tokens never leaving the machine.26875 npm84MIT
- AlicenseNot gradedqualityDmaintenanceA self-hosted MCP server providing Claude with authenticated access to Google Calendar, Gmail, Drive, Docs, Sheets, and Slides via 43 tools and secure OAuth2.528 npmMIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that gives Claude Code write access to a personal Google account — Gmail, Drive, Calendar, Sheets, and YouTube — backed by a self-owned Google Cloud OAuth client.528 npmMIT
- AlicenseNot gradedqualityBmaintenanceSelf-hosted fitness tracking MCP server that gives AI assistants access to your nutrition, training, weight, sleep, and accomplishment data via 77 tools and 5 resources. Enables natural-language logging and querying of personal health metrics through Claude or ChatGPT.12 npm1BSD 2-Clause "Simplified"