People and access
MCP tools to find people, explain their access, erase their data and simulate purchase events.
These tools let an agent look up the people using your app, explain why they have or lack a perk, and play lifecycle events on simulated purchases.
People
Key access: Customers, Entitlements for access explanations, and Erase customers and their data to erase.
| Tool | What it does |
|---|---|
find_persons | Finds people by exact email, distinct ID or person ID, or lists the newest. |
get_person | A person's profile, perks and what grants each, subscriptions, purchases, flag overrides and recent events. |
explain_person_access | Why a person has or lacks a perk, where the chain breaks, and the fix. |
update_person | Changes a person's email, name or attributes. |
create_person | Adds a person by the distinct ID your app will identify them by. |
erase_person | Erases a person's personal data for good. Asks first. |
get_person_erasure | The progress of an erasure. |
Simulated purchases
Key access: Test purchases. These tools change only simulated purchases from debug builds; see Simulate renewals, expiry and refunds.
| Tool | What it does |
|---|---|
get_sandbox_purchases | A person's simulated subscriptions and purchases, and the access they grant. |
simulate_sandbox_event | Plays renew, expire, grace_period (3 days), refund or revoke on a simulated purchase. |
reset_sandbox | Deletes every simulated purchase in the project. Asks first. |
Example
Someone says they paid for Pro but have no access. Their email is ada@example.com.
The agent calls find_persons to find them, then explain_person_access to show where the chain from purchase to perk breaks.
Next steps
- People and identity: distinct IDs and merges.
- Test purchases (Help center): every way to test a purchase.
- Catalog and payments: products and store mappings.
Something wrong or missing on this page? Tell us by email or on Discord.