Available in your account

Family context. In your assistant.

MCP is a standard for connecting AI tools to your data. Geopapa helps your assistant understand family plans and act within the permissions you choose.

8 scenarios and ready-to-use prompts for your assistant

  1. You ask “Where is Lisa now?”
  2. Assistant requests ChatGPT, Claude or another MCP client
  3. Geopapa checks Is this child selected? Is it permitted? Is the subscription active?
  4. Answer with evidence Permitted data only, with observation times and gaps
The assistant never connects to your child’s phone: every request passes through Geopapa’s checks. Permitted data is sent to the AI service you chose.

01 / Connect the server

  1. 1Add the URLIn your client’s connection settings
  2. 2Sign in to GeopapaYour client opens the sign-in page
  3. 3Choose accessTick children and permissions
  4. 4Start a chatEnable the connection and ask
Connecting takes four steps. Your Geopapa password is entered only on Geopapa, never in the chat.

In a compatible client, add a remote MCP server using Streamable HTTP. If your client supports OAuth, choose to sign in through Geopapa.

MCP requests require at least one active paid subscription in your family. When it expires, data access pauses until renewal.

MCP URLhttps://mcp.geopapa.com/mcp

Geopapa shows the client name and lets you select children and permissions. OAuth access lasts up to 90 days; the client automatically refreshes its short-lived access token.

Simplified consent screen. No child is preselected and permissions that change data start switched off — you tick them yourself.

ChatGPT and Claude

ChatGPT

  1. Plugins
  2. Add custom MCP server
  3. URL and OAuth
  4. Geopapa sign-in

Open Plugins → Add custom MCP server. Enter the URL above and select OAuth. Create the connection, sign in to Geopapa and approve children and permissions. After installing it, select the connection in a new chat.

OpenAI connection guide

Claude

  1. Customize
  2. Connectors
  3. Add custom connector
  4. URL
  5. Connect
  6. Geopapa sign-in

Open Customize → Connectors → Add custom connector. Enter the URL above. OAuth supports published client identity or automatic registration. Click Connect, sign in to Geopapa and approve access. Enable the connection in your chat through + → Connectors.

Anthropic connection guide

Availability depends on your plan and workspace settings; menu names may change. If a client asks for Client ID and Client secret, use a registered OAuth client — these are not your Geopapa API token. Start with “Which children are available in Geopapa?” and check that only your selected children appear.

If your assistant cannot see all capabilities

The capability catalog and your permissions are separate. If a client shows the old 11-tool list or cannot submit an approved app-control preview, use its supported connection refresh and check the list again. New consent alone does not guarantee a catalog refresh. App changes without a valid preview will be rejected.

For every change, approve the child and exact terms, including pause, archive and restore. Creating a one-off task attempts a push but does not confirm delivery. Rewards are issued only through completion in the app.

02 / Or use an API token

Sign in through Geopapa (OAuth) If your client supports it
How to connect
Sign in and approve access
Lifetime
Up to 90 days
Secret
Nothing to copy
API token For other clients
How to connect
Create in your account and add a header
Lifetime
30, 90 or 365 days
Secret
Save at once in the client’s secure field
Both are limited to the children and permissions you select, and both can be revoked in your account.

Open Connections in your account, create a separate token for your client and save it immediately. Use the same server URL and add this header in the client:

Authorization: Bearer YOUR_GEOPAPA_TOKEN

Keep the secret in your client’s secure field or secret store. Do not paste it into chat messages. Setting names vary by client; remote MCP with OAuth PKCE S256 or a Bearer header is required.

Open Connections

03 / Start with a useful question

How is Lisa doing today? My timezone is Europe/Berlin

  • LocationLast point measured at 14:30.
  • TasksOne done, one due at 19:00.
  • GapNo points from 10:00 to 11:30. This does not mean the phone was off.
Sample answer with made-up data. Wording depends on the assistant, but observation times and gaps are stated explicitly.

Built-in MCP prompts: family_briefing, screen_time_review and plan_family_tasks. The catalog contains 19 tools: 14 reads and 5 writes. Each call requires its corresponding permissions. Approve any additional access in Geopapa when prompted.

Comparing daily observations

For example: “Compare my child’s observations on 17 October 2026 with 26 September, 3 and 10 October, from 08:00 to 10:00, Asia/Yerevan. Show differences and missing evidence.” Location history and places permissions are required. You choose the earlier dates and timezone; matching weekdays are used by default.

Measurements are aligned to the same local-clock slots: more frequent reports do not gain extra weight. Each 15-minute window needs three separated measurements in every selected day. Old unknown timestamps, server substitutes, gaps and coordinate jumps do not become evidence of a new route. Results include times and references to the source observations.

  • Measurement
  • No measurement
  • Compared
  • Not enough data
Each column is a 15-minute window. It is compared only when every selected day has three measurements. A single gap removes the whole window.

Choose up to six earlier dates within eight weeks and a window of up to four hours, with boundaries at 00, 15, 30 or 45 minutes. Repeated observations require at least three comparable earlier days; one pair does not establish a habit. Unfinished windows and ambiguous clock-change windows are not compared. Different coordinates do not prove changed behavior: GPS accuracy, phone clocks and sampling bias may be unknown. The comparison does not calculate complete travel, dwell time or causes.

Screen time and reversible controls

Ask to compare equal periods, such as 1–7 and 8–14 October, and specify the timezone used to interpret the phone’s dates. Your assistant shows coverage, provenance and receipt times. Only comparable snapshots are compared; missing days or apps are not zero. Even a past day can be incomplete, and app totals may differ from the device counter.

For example: “Prepare a 30-minute daily limit for this game; show me the changes first.” You can also preview blocking selected apps, a study-time schedule or paused controls. Before saving, review old and new rules, conflicts and inventory suitability. Preview changes nothing; approval is valid for 10 minutes.

  1. PreviewChanges nothing. Valid for 10 minutes
  2. Your approvalWithout it the change is rejected
  3. Rule savedA command is queued for the phone
  4. Device reportShown separately if it arrives
  5. Check on the phoneThe only proof that blocking works
No step proves the next one. Undo follows the same path: preview, approval, save. Writing is available for Android only.

Writing requires an Android report received within 15 minutes and app read/write permissions. Schedules use the phone’s clock; automatic “undo after an hour” is not available. After saving, ask to “Preview undoing this change.” The server restores prior rules only if no later policy change occurred and restoration remains supported. Undo also requires approval.

Saving and queuing synchronization do not prove that blocking works. An exact-version device report is shown separately; actual enforcement needs a phone check. iOS selects apps through its own Screen Time mechanism; changing those selections through MCP is unsupported.

Why are device reports not updating?

Ask: “Check my child’s battery, location and app-control evidence. What is known, and what should I check on the phone?” Family access covers battery; location and app evidence require their respective permissions. Diagnostics do not change settings or send commands.

Server receipt time and device observation time are shown separately. Phones do not yet report battery measurement time, so a recently received percentage does not guarantee a recent measurement. Older records may have unknown timestamps. A server timestamp or repeated anchor location is not a new GPS measurement.

DataServer receivedPhone measured
Battery 64%14:32unknown
Location14:3214:30
Repeated old point14:32not a new measurement
Example with made-up data. A recently received report is not necessarily a recent measurement, so the two times are shown separately.

Saved restrictions, commands and device reports are separate: they do not prove enforcement on the phone. iOS uses a different Screen Time mechanism. When an older client cannot distinguish a disabled permission from an omitted flag, the assistant asks you to check the setting instead of claiming it is off. Missing reports do not establish a connectivity failure or its cause.

Recurring family tasks

For example: “Preview a routine for Lisa: pack the school bag on weekdays by 19:00, from 19 October to 30 November 2026, timezone Europe/Berlin, reward 10 coins.” Your assistant first shows the dates and terms. Preview creates nothing; approve the plan and allow task read and write access to save it.

Repeat daily or on selected weekdays for up to 90 days. The chosen time is the deadline. A task appears in the app within the preceding 24 hours, at the next maintenance check, normally every 5 minutes. Automatic tasks have no creation push notification; coins come only from completion in the app.

  1. Mon19:00
  2. Tue19:00
  3. Wed19:00
  4. Thu19:00
  5. Fri19:00
  6. Sat—
  7. Sun—
  1. 1. Mon, from 19:00The task appears a day before the deadline: the server normally checks every 5 minutes. No push is sent
  2. 2. CompletionCoins are issued only through the app
  3. 3. Tue, 19:00The deadline. Expired dates are not backfilled
How a “weekdays by 19:00” routine works, using Tuesday’s task as an example.

Ask to list routines, change future tasks, skip a date or pause a routine. Calculated dates and existing tasks are shown separately. Pausing does not archive existing tasks; edit them separately. Expired deadlines are not backfilled. After resume, upcoming deadlines within 24 hours can still produce tasks. During clock changes, nonexistent local times are skipped and repeated local times use their first occurrence once.

Revoking access, expiry of consent or loss of the subscription stops task creation. Explicitly resume the routine after restoring access. A new connection does not take it over automatically.

Geofences and notifications

Ask to list your child’s geofences or preview a rule: “Notify me about entering and leaving school on weekdays from 08:00 to 20:00, timezone Europe/Berlin.” First save the place in the Geopapa mobile app. Your assistant offers your saved places, previews the rule and asks you to approve saving. Preview changes nothing and lasts 10 minutes; a changed place requires a new preview. Do not send coordinates or addresses in the command.

If your connection cached the old geofence format, refresh its tool catalog. Existing zones and events are preserved.

To save, separately allow geofence read and write access when connecting Geopapa. You can change the schedule, pause, archive and restore a rule. The zone radius is 50 metres. Only the rule owner receives notifications through Geopapa. A push attempt does not guarantee delivery.

Events use multiple fresh GPS observations: inside up to 35 metres from the center, outside from 65 metres, uncertain in between. At least two samples must span 30–180 seconds. Creation, changes, resume or a long gap first establish a baseline without an arrival alert. Each rule allows at most one arrival and one departure notification per day. GPS can be wrong; an event does not prove a physical visit.

35 m 50 m 65 m
  • Inside — up to 35 mCan confirm an arrival
  • Uncertain — 35–65 mNo notification
  • Outside — from 65 mCan confirm a departure
Drawn to scale. The dashed line is the 50 m zone radius. An event needs at least two samples spanning 30–180 seconds.

Current observations require location permission; events require history permission. Earlier events are not reconstructed. Revoked access or an expired subscription stops processing; explicitly resume after restoring access. Editing a guarded rule in the mobile app pauses it for review.

Access stays in your control

PermissionReadChange
Family
Location
Location history
Places and geofences
Tasks
Apps
Not available through MCP
  • Listening
  • Payments
  • Passwords
  • Administrator functions
Each permission is switched on separately for each connection and applies only to the children you selected.

Each connection is restricted to selected children. Newly added children are never included automatically. Location, history, places, tasks and app permissions are separate. Your account shows expiry dates, recent calls and a revoke button. Removing a family link also removes the assistant’s access.

A location is the last stored point with its timestamp source, not proof that the device is online. Missing screen time days are not counted as zero. MCP app control works with Android; iOS Screen Time uses a different mechanism. Saved rules require phone synchronization, with application status reported separately.

MCP does not expose listening, payments, passwords or administrator functions. Data you authorize your assistant to access is also processed under your chosen AI service’s policies.