# Use ChatGPT and Claude

Connect an assistant and verify exactly what it can read and change.

Source: https://docs.getridian.com/guides/assistants/
Language: en
Reviewed: 2026-09-20

## Before connecting

Connect a calendar in Ridian first. Select the workspace and decide which calendars, content level and actions this client needs. Public directory availability and custom connector support can differ by client and plan. Use the setup instructions offered in Ridian; a beta invitation is not proof that a public directory listing is live.

## Connect the Ridian endpoint

Where your client supports a custom remote MCP connector, use `https://api.getridian.com/mcp`. Complete the Ridian OAuth flow in your browser. Review the workspace, selected calendars and allowed operations before confirming. Never paste provider credentials into a chat.

## Start with a read

Ask: “List the calendars I have allowed you to use.” Then request a short, explicit window in your test calendar. For example: “Show events tomorrow in my test calendar, in Europe/Berlin.” Verify the calendar and time zone against your provider's app.

For a write test, explicitly ask for one standalone event without guests. Check it in the provider app, then ask to rename and delete that specific test event. Do not use a real meeting as a test. CalDAV's provider path is deployed, but the complete CalDAV client acceptance is still pending; see [CalDAV](https://docs.getridian.com/integrations/caldav/).

## Tools and permission changes

An assistant saying “I cannot create events” is not enough to identify the cause. The client may have an old tool list, the write scope may be absent, or effective calendar rights may deny writing. Check [missing tools](https://docs.getridian.com/troubleshooting/assistant-access/) before repeating the request.

Use the Ridian client controls to narrow or revoke access. Disconnecting one assistant is a different action from disconnecting the underlying calendar account.