ChatGPT MCP profiles
Dayze exposes two ChatGPT-facing MCP profiles. Use the compact Directory URL for everyday read access; use personal only when you intentionally want ChatGPT to create or edit life-graph records.
Install hub →Which profile?
| Profile | URL | Read / write | Use when |
|---|---|---|---|
| Compact (Directory) | https://dayze.com/api/mcp?tools_profile=compact | Read only | Default ChatGPT Apps / Directory install. The only Directory URL. |
| Personal (write) | https://dayze.com/api/mcp/personal | Read + write (scoped) | Private connector when you want ChatGPT to create or edit life-graph records. Not for the public Directory listing. |
| API key | https://dayze.com/api/mcp/key | Per key scopes | Cursor / CLI with a Bearer dayze_k_* key |
| Unscoped MCP | https://dayze.com/api/mcp | Auth required for private tools | Full catalog metadata may appear in tools/list; calling private tools needs OAuth or an API key. Prefer compact or personal for ChatGPT. |
Compact tools (eight, read-only)
Live tools/list on the compact URL returns these eight tools. They never mutate records.
- get_context_pack
- search_dayze
- get_events
- get_people_context
- get_finance_context
- get_travel_context
- search
- fetch
OAuth scopes
| Scope | Compact | Personal | Meaning |
|---|---|---|---|
| openid | Yes | Yes | Sign-in identity |
| Yes | Yes | Account email on the grant | |
| context.read | Yes | Yes | Read life-graph packs (events, people, finance, travel, …) |
| context.write | No | Yes | Create and edit records |
| context.delete | No | Yes | Reviewed, reversible contact deletion |
| offline_access | Yes | Yes | Refresh tokens so the connector stays connected |
Neither profile grants mail or sensitive PII scopes. Personal contact deletion requires a preview and remains undoable for 30 days. Revoke anytime in Dayze Settings → Connected apps.
Claude, Cursor, Gemini and API keys
Every other AI app gets only the access you give it. A new connection can read and add to your records by default. The rest stays off until you tick it on the consent screen or allow it later for that connection in Settings → Agent access → Connected apps, where you can also take access away. A change applies on the app's next request.
| Scope | New connection | Meaning |
|---|---|---|
| context.read | Yes | Read your records |
| context.write | Yes (you can untick it) | Add and edit records |
| context.delete | Only if you allow it | Remove and reorganize records (previewed or archived) |
| mail.read | Only if you allow it | Read the Gmail accounts you connected |
| pii:read | Only if you allow it | Contacts' private emails and phone numbers |
| travel_secrets:read | Only if you allow it | Booking references and other travel details |
| financial_details:read | Only if you allow it | Individual expenses and financial details |
An app never gets a scope it didn't ask for at consent. Connections made before this change keep their scopes. API keys hold the scopes you pick when you create them (Read only, Read + write, or custom); older keys with scope context keep full access and are labelled Full access in Settings. A tool beyond a connection's scopes is left out of its tool list, and calling it returns 403 INSUFFICIENT_SCOPE naming the scope.
Support tips
- Directory installs must stay on the compact URL. Writing requires a separate personal connector install.
- If ChatGPT can't write, check the MCP URL and that consent includes
context.writeandcontext.delete. - Prefer
get_context_packfirst on compact (week bootstrap). Personal writes still need a clientrequest_id. - More install recipes: Agents & MCP · /mcp