Skip to main content
Glama
whereabot

whereabot

Official
by whereabot

Whereabot

Let your AI agent ask your phone where you are, on demand. You host the relay. Sign-in and user data live in Supabase.

flowchart LR
  Agent["AI agent"] -->|"MCP or HTTP"| Relay["Relay (Rust)"]
  Relay -->|WebSocket| Phone["Phone app (Tauri)"]
  Phone -->|"GPS fix"| Relay
  Relay -->|"answer"| Agent

The relay keeps no location history. It sends a ping, the phone reads its GPS now, and the answer goes back to the agent. What is stored, for how long, and who sees your location: privacy.

Status

Early MVP, in beta. iOS answers in the background through push. Android answers only while the app is open. See the roadmap.

Related MCP server: onsense

Repo layout

Path

What

server/

Rust relay (axum). Agents call it over HTTP or MCP; the phone holds a WebSocket to it.

app/

Tauri v2 phone app (Android / iOS). Signs in, then answers pings with a GPS fix.

supabase/

Database migrations and tests.

infra/

OpenTofu for the dev and prod environments.

scripts/

Local dev, end-to-end check, deploy, hook install.

docs/

Source of the docs site.

site/

Landing page and OAuth consent page.

docs-site/

VitePress build of the docs site.

design-system/, brand/

Shared CSS tokens and components; logo files and usage rules.

Connect your agent

  1. Install the app: see Get started on whereabot.io, or install from the browser.

  2. Sign in with Apple or Google on the phone.

  3. Add the relay to your agent:

    claude mcp add --transport http whereabot https://relay.whereabot.io/mcp
  4. In Claude Code run /mcp and sign in with the same Apple or Google account as on the phone. You never paste a token.

  5. On Android, keep the app open while the agent asks, until Android push ships.

Relay URLs: live URLs. The tool and its arguments: protocol.

Self-host

Run your own relay and Supabase project with the OpenTofu code in infra/. Steps: infra/README.md. Build the app with your Supabase and relay values (app/.env.example), and add your relay to your agent. To run everything on one computer first: local quick start.

Docs

All docs, with the generated MCP and wire references: whereabot.io/docs. In this repo:

Community

License

MIT. Third-party material: THIRD_PARTY_NOTICES.md.

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Turn your Android phone into an MCP server. AI assistants connect on demand, query your health data, notifications, app usage, and take actions on your device — all end-to-end encrypted, no cloud sync.
    12
    Apache 2.0
  • A
    license
    Not graded
    quality
    D
    maintenance
    OAuth token broker for AI agents to securely act on a user's behalf across third-party APIs (Gmail, Slack, GitHub, Notion, etc.) by vaulting tokens server-side and never exposing them to the LLM.
    1
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Self-hosted multi-user Google Health OAuth broker and read-only Agent API with remote MCP support. Enables users to connect their Google account and grant agents secure access to activity, sleep, heart, HRV, SpO2, and other health metrics via revocable per-token authentication.
    3
    MIT