Repository navigation
MCP
Find+ ships an MCP server over the local daemon API.
It runs over stdio and speaks to the daemon at http://127.0.0.1:8647 by default.
Add to claude_desktop_config.json:
{"mcpServers": {"findplus": {"command": "findplus", "args": ["mcp"]}}}With write tools enabled:
{"mcpServers": {"findplus": {"command": "findplus", "args": ["mcp", "--allow-writes"]}}}Optional: unlock automatically at startup. Prefer FINDPLUS_PIN_FILE in env, pointing at a
file that contains only the PIN and is readable by you alone (chmod 600); an MCP client config
is usually world-readable and often ends up in a git repository. FINDPLUS_PIN still works and
takes precedence. Either way Find+ reads the value once and removes it from its own environment,
so no child process inherits it.
Run once in your project directory:
claude mcp add findplus -- findplus mcp
With write tools: claude mcp add findplus -- findplus mcp --allow-writes
Alert rule definitions and label configurations are deliberately not exposed over MCP to keep the tool set focused on read-only data queries and exports.
| Tool | Description |
|---|---|
get_status |
Daemon status, poll schedule, provider health |
list_devices |
All tracked devices |
list_groups |
All groups |
list_places |
All saved places |
get_latest |
Most recent fix per device |
get_timeline |
Location history for a day |
get_trips |
Stays, trips and no-sighting gaps for one device and day (approximate) |
get_place_events |
Place ENTER/EXIT event log |
get_group_presence |
Group presence verdict |
list_people |
People and pets with where each likely is now |
where_is |
Where one person (name or id) likely is now, how sure, how old |
get_person_day |
One person's local day in plain words: left, arrived, stops, gaps, left behind |
get_people_suggestions |
Preview people suggested from tracker names (saves nothing) |
export |
Export history as CSV, JSON, GPX or KML (capped at 5 MB) |
unlock |
Unlock the app with a PIN |
| Tool | Description |
|---|---|
poll_now |
Trigger an immediate poll |
add_place |
Create a new place. Pass notify: true to also create an arrive/leave alert rule; the default is false |
remove_place |
Delete a place |
add_group |
Create a group |
set_group_members |
Replace a group's member list |
accept_people_suggestions |
Create people from suggestions (as you edit them) and dismiss others; nothing is applied without this call |
set_tracker_role |
Set what a tracker is attached to (bag, shoes, phone) and its carry weight |
lock |
Lock the app |
Never exposed, on any tool: PIN set/change/reset, history deletion, alert channel credentials.
Every tool returns a JSON object. Failures use one shape:
{"error": {"code": "locked", "message": "Find+ is locked", "hint": "call unlock(pin)"}}| Code | When |
|---|---|
daemon_down |
The daemon is not running or cannot be reached. |
locked |
The app lock is on. Call unlock first; no tool returns data while locked. |
not_found |
The place, group or device id does not exist. |
validation |
An argument is out of range or the wrong type. |
upstream |
The daemon answered with an error or did not answer in time. |
Without --allow-writes the write tools are not registered at all, so a client never sees them.
Find+ is not affiliated with Apple or Google. Find Hub and Find My are their trademarks.
Every tool response includes a notice field with the following text:
This history consists of locations reported through Google's Find Hub network. Your trackers use nearby participating Android devices to report their location. Location updates can therefore be delayed, sparse, or unavailable, and this application should not be treated as real-time emergency or child-safety GPS tracking.