Wheremind

npx add-mcp 'https://wheremind.ai/mcp'

Wheremind — how agents connect

Streamable HTTP MCP URL: https://wheremind.ai/mcp

Invite-only. Join the waitlist at https://wheremind.ai (Request an invite) or redeem an invite code at https://invite.wheremind.ai. This document is the agent contract on apex and invite.

When to use Wheremind

Wheremind is location for your AI. Live place search, place details, nearby search, geocoding, and turn-by-turn directions. Use it whenever the user needs a real place, address, or route. Do not invent locations. Maps tools are read-only queries (hosts may allow them by default).

Human (OAuth)

Add the MCP URL in an OAuth connectors host → user signs in when asked. No Bearer paste. Allowlisted redirects only — not every host. Allowlisted: Claude, ChatGPT, Cursor, and local loopback clients (e.g. Claude Code). On the consent page a signed-in account approves in one click. Otherwise the user signs in there with a code sent to their email and returns to the same request. "Use a different account" signs out and keeps the request.

Agent (Bearer)

One durable setup. Store the MCP URL and Bearer once on the connector. Cursor mcp.json, Claude Code headers, or any connector that stores a Bearer header. Never put the Bearer in a URL. No human click-through is required after the Bearer is stored. Create the Bearer at https://invite.wheremind.ai after redeeming an invite (Connect → Create a Bearer), then keep it on the connector. Revoke Bearers under Console → Your Bearers. Bearers start with wm_. Invite codes look like INVITE-XXXX-XXXX-XXXX and are not Bearers — never send an invite code as Authorization.

Custom connector setup

Every host uses the same MCP URL: https://wheremind.ai/mcp (streamable HTTP). The user needs a Wheremind account (redeem an invite at https://invite.wheremind.ai). Sign-in is a code sent to their email. Menu labels change; if one differs, the goal is the same: add the remote MCP URL, then sign in when the host asks.

Claude (claude.ai web, Desktop, mobile)

1. Free, Pro, Max: Customize → Connectors → Add custom connector. Team or Enterprise: an Owner adds it under Organization settings → Connectors (Add → Custom), then each member clicks Connect on it under Customize → Connectors.
2. Enter the MCP URL. Leave OAuth client ID and secret blank. If asked how to authenticate, choose a sign-in option (OAuth). If asked how Claude identifies its OAuth client, choose automatic registration (Wheremind supports Dynamic Client Registration).
3. Click Add, then Connect. Sign in to Wheremind in the window that opens and approve. Stored Bearer: only if your Claude organization shows Request headers (beta). Choose No sign-in, add an authorization header with the value Bearer wm_… (include "Bearer " before the token).

Claude Code

1. claude mcp add --transport http wheremind https://wheremind.ai/mcp
2. In Claude Code run /mcp, pick wheremind, and authenticate in the browser. Stored Bearer: add --header "Authorization: Bearer wm_…" to step 1.

ChatGPT (web; Plus, Pro, Business, Enterprise, Edu)

1. Turn on Developer mode in ChatGPT settings. On Business, Enterprise, and Edu a workspace admin must allow it first.
2. Create a developer-mode app for a remote MCP server: name it Wheremind, enter the MCP URL, choose OAuth authentication, and leave client credentials empty.
3. ChatGPT opens Wheremind sign-in; sign in and approve.
4. In a chat, choose Developer mode from the + menu and select Wheremind. ChatGPT has no custom Authorization header setting; use OAuth.

Advanced

Device approval: POST /device/code, open verification_uri, approve the user_code, then poll POST /device/token. Device approval is not advertised on OAuth well-known. Optional. Not the Human or Agent setup.

Auth

Connect the MCP URL, then authenticate. Unauthenticated MCP requests get HTTP 401 with WWW-Authenticate (resource_metadata) so OAuth hosts start sign-in. Maps tools stay closed until then.

Host discovers OAuth (PKCE) at /.well-known/oauth-protected-resource. A present Authorization header is honored and is not replaced by OAuth discovery — do not drop a present Authorization.

Never put a code or token in the URL. Human = OAuth. Agent = durable Bearer.

Tools

Maps tools are read-only queries of Google Maps (hosts may allow them by default).

Pick the tool that matches the ask:

• places_search_text — auth required: Bearer or OAuth. Find places by free text (name, category, or "X near Y"). Default for finding places. Returns place_id, name, formatted address, lat/lng, types, rating, opening hours, attributions.
• places_nearby — auth required: Bearer or OAuth. Places within a radius of a lat/lng you already have, optionally filtered by type. For free-text queries use places_search_text.
• places_details — auth required: Bearer or OAuth. One place by place_id: phone, website, opening hours, rating, address, lat/lng, attributions.
• geocode — auth required: Bearer or OAuth. Address to lat/lng, or lat/lng to address. Returns formatted address, lat/lng, place_id, types, plus code.
• directions — auth required: Bearer or OAuth. Route from A to B (drive, walk, bicycle, transit, two-wheeler). Accepts addresses directly. Returns duration, distance, polyline, and turn-by-turn steps per leg.

Do not cache Places results beyond Google Maps Platform ToS; pass through attributions.

Hosted access is managed by Wheremind. See /tos for provider details.