AI access through MCP

AI access is in protected validation.

Google approved Uredan's read-only Calendar data-access review. ChatGPT and Codex validation remains limited to one approved production owner cohort while public connection setup, other client providers, and Uredan's separate assistant handoff actions remain unavailable.

  • Approved production owner cohort only
  • Host account model improvement is off
  • Google Calendar review approved

The planner remains available

What remains unchanged during validation

The protected MCP pilot does not change ordinary planning or the bounded read-only Calendar experience inside Uredan.

Plan normally in Uredan

Capture, organize, schedule, and complete tasks in the browser without adding an external AI client.

Keep Calendar inside Uredan

Connected Google Calendar events remain available read-only in Planner, Plan, and Timeline.

Use ordinary copy

Provider-neutral Markdown and plain-text copy remain available for your own deliberate use.

Why access is protected

One account control does not justify a global release.

A task created from a Calendar event can keep its copied title and planned duration. The approved owner has explicitly accepted transfer of that direct and derived data to the validated ChatGPT/Codex account, with account-wide model improvement off.

  • The owner boundary is enforced. OAuth completion, bearer use, and Settings reject every owner outside the protected cohort.
  • All nine permissions are disclosed. WorkOS role permissions authorize tools because dynamic clients cannot select a smaller custom subset.
  • Other transfer paths stay closed. Copy for assistant, Open in Codex, other hosts, and public setup remain unavailable. Optional in-app task suggestions have their own reviewed provider and rollout boundary.

Before broader access

Each wider release still needs its own proof.

Google's data-access approval does not approve another owner, host provider, or public marketplace release.

  1. 1

    Provider controls

    Each additional provider plan needs verified data-use and training controls.

  2. 2

    Consent and lineage

    Broader controls must cover Calendar projections and content copied into tasks.

  3. 3

    Complete host evidence

    OAuth, discovery, tools, refresh, revocation, recovery, and rollback must pass for each exact host build.

Need help with an earlier connection?

Read the current privacy notice or contact Uredan support. There are no public setup steps while protected validation is in progress.

Contact support