Whereabot

io.whereabotPublished by whereabot.ioOfficial publisherv0.1.0Updated Nov 7, 2026

Ask the user's phone where they are now. The phone answers each request with consent.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle Communication & Collaboration

Server details

Identifier: io.whereabot/whereabot
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Oct 31, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to whereabot.io, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.whereabot%2Fwhereabot.svg)](https://sourceweft.com/mcp/io.whereabot%2Fwhereabot?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Whereabot lets an AI assistant ask the user's phone for its current location on demand, with the phone answering each request after consent.

What you can do: Request the user's current location: the assistant pings the phone, which takes a fresh GPS fix and returns it.
Rely on consent per request: the phone answers each location request only with the user's approval.
Connect over MCP or HTTP to a relay that the phone keeps a WebSocket connection to.
Optionally let another person's agent ask for the user's location, per the documented sharing flow.
When to use it: Useful when an assistant needs the user's real, current whereabouts rather than a typed address — for example location-aware answers, nearby suggestions, or checking in on where someone is. Best suited to users willing to install a companion phone app and sign in.
Requirements: Remote relay endpoint reached over streamable HTTP; OAuth sign-in is required. The user must install the Whereabot phone app (Android or iOS) and sign in with Apple or Google, using the same account in the agent client. On Android the app must stay open while the agent asks; iOS can answer in the background via push.

Before you install

It shares the user's live location with the connected agent and, through the relay, with the hosted service; sign-in and user data live in Supabase. The relay is described as keeping no location history, but review the privacy documentation before use. The project is an early beta MVP, and Android only answers while the app is open. Self-hosting is possible but requires running your own relay and Supabase project.

Installation

In SourceWeft

Open Whereabot in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.whereabot%2Fwhereabot/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "whereabot": {
      "type": "http",
      "url": "https://relay.whereabot.io/mcp"
    }
  }
}

README

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.

mermaid

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

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.

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

Install the app: see Get started on whereabot.io, or install from the browser.
Sign in with Apple or Google on the phone.

Add the relay to your agent:

In Claude Code run /mcp and sign in with the same Apple or Google account as on the phone. You never paste a token.
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:

Architecture: components, sign-in and ping flow, security, limits
Protocol: HTTP, MCP and WebSocket at intent level
Request flow: every state, notification and agent result of one request
Location sharing: let another person's agent ask for your location
Privacy: what is stored, retention, who sees your location
Operations and infrastructure: how it runs, deploys and releases
Prior art and roadmap
Listings: MCP directories, server.json, how to publish

Community

Contributing: local setup, hooks, rules, adding a migration
Security policy: report vulnerabilities privately
Code of conduct

License

MIT. Third-party material: THIRD_PARTY_NOTICES.md.

Source: README.md at commit 34e90bc

Tools

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v0.1.0LatestOct 31, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts