Family context. In your assistant.

01 / Connect the server

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.

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.

ChatGPT and Claude

ChatGPT

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

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

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:

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.

Connection settings will appear in your account at launch. Administrators and invited users already have early access.

03 / Start with a useful question

• “What do we know about my child’s day yesterday? Use Europe/Berlin.” — location history and places. Shows observations, possible stops and gaps; a zone match does not prove a visit.
• “How are the kids today? My timezone is Europe/Berlin.” — family, location and task read permissions. Ask for a morning or evening briefing; observation times and missing data are shown explicitly.
• “Where was my child last seen, and how recent is the location?” — location permission.
• “Compare screen time over the past 7 days.” — app read permission.
• “Suggest a plan of chores with rewards.” — task read permission. Allow task changes to create a task you approve.
• “Limit this game to 30 minutes a day.” — app read and write permissions; the assistant first confirms the rules.

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.

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.

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.

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.

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.” Your assistant confirms the center, previews the rule and asks you to approve saving. Preview changes nothing.

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.

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

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.