> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cortado.pro/llms.txt
> Use this file to discover all available pages before exploring further.

# Claude

> Connect Claude, or another AI app, to look up Cortado records and take a few permission-scoped actions

## Claude Overview

You can connect Claude — or another AI app that supports the same connection standard — to your Cortado data. The connected app can look up leads, contacts, notes, tasks, and quotes, check whether a date is free, and take a short list of actions you already have permission to do: move a lead's stage, add a team note, or mint a customer-portal link.

This connection is available to every organization. You can configure it from **Settings > Integrations > Connected Apps**, and it also appears as an optional step in Getting Started.

## Connecting Claude

<Steps>
  <Step title="Open Integrations">
    Go to **Settings > Integrations > Connected Apps** and find the **AI assistants (MCP)** card. If you already approved this connection, Cortado finishes authorization and returns you to the AI app instead of showing an error.
  </Step>

  <Step title="Copy the server URL">
    Click **Copy URL** to copy your organization's server address. It's specific to your organization, so treat it like a credential.
  </Step>

  <Step title="Add it in Claude">
    In Claude, open Connectors settings, choose to add a custom connector, and paste the URL you copied.
  </Step>

  <Step title="Sign in and authorize">
    Claude opens a Cortado sign-in and authorization screen in your browser. Sign in with the Cortado account whose organization you want the app to use, review exactly what access it's requesting, and approve.
  </Step>

  <Step title="Start asking">
    You're returned to Claude with the connection active. Ask about your leads, contacts, quotes, or upcoming events — or ask it to move a lead, add a note, or share a portal link.
  </Step>
</Steps>

## What Claude Can See

The authorization screen spells out exactly what the connected app can access before you approve:

* **Leads** — inquiries, filtered the same way you'd filter them in Cortado, plus counts and totals grouped by channel, stage, or month
* **Contacts** — names, emails, phone numbers, and custom fields
* **Notes** — attached to leads and other records, including who wrote them
* **Tasks** — title, status, due date, and assignee
* **Quotes** — line items, totals, payment schedules, and status
* **Availability** — whether a day has conflicting active leads or upcoming events (including nearby bookings that would overlap setup or teardown)

Every request runs through the same permissions your Cortado role already has — if you can't view quotes in the app, the connected AI app can't read them either. Records belonging to another organization are never returned.

## What Claude Can Do

A few actions go beyond looking things up. They still follow your role, and they need an active Cortado subscription:

* **Move a lead** — change one lead's pipeline stage (New, In Progress, Quote Sent, Accepted, Rejected, or Stale). Requires lead management permission.
* **Add a note** — attach a team note to a lead, contact, event, booking, quote, or invoice. Requires management permission on that kind of record.
* **Get a portal link** — mint a fresh customer-portal URL for one quote or invoice. Each request creates a new link, so only ask when you are about to send it. Requires lead or invoice management permission, matching the record.

<Info>
  Claude cannot send email, create quotes, take payments, or delete records. If a teammate's role can't do an action in Cortado, an AI app signed in as them can't do it either.
</Info>

## Reviewing and Revoking Access

Approving a connection doesn't lock you in. Review or remove it at any time from the connected app's own settings — for example, Claude's Connectors settings — and disconnecting immediately revokes access and stops all further reads and actions. If you want to connect a different organization, add its server URL separately and approve it separately; one authorization never carries over to another organization.

<Tip>
  If you're not sure an integration is still needed, disconnecting is reversible in the sense that you can always reconnect later — but while it's connected, treat the server URL like any other credential and don't share it outside your organization.
</Tip>

## Best Practices

1. **Copy the URL from Settings, not from memory** — it's organization-specific, and a mistyped or reused URL from another org won't work
2. **Review what's requested before approving** — the authorization screen lists exactly what the app can read and do; confirm it matches what you expect
3. **Keep the server URL private** — anyone with it can start a connection request against your organization
4. **Match roles to what you want visible** — since access follows your Cortado permissions, tighten a role first if you want an AI app to see or change less
5. **Ask for a portal link only when you're sending it** — every request creates a new URL
6. **Disconnect unused connections** — remove a connector you're no longer using from the AI app's settings rather than leaving it active

<CardGroup cols={2}>
  <Card title="Staff" icon="users" href="/guides/staff">
    Control what a teammate's role — and any AI app connected as them — can see and do.
  </Card>

  <Card title="Gibby" icon="sparkles" href="/guides/gibby">
    Cortado's own built-in AI assistant, with the same permission-scoped approach.
  </Card>

  <Card title="Leads Pipeline" icon="filter" href="/guides/leads-pipeline">
    The stages Claude can move a lead through.
  </Card>

  <Card title="Customer Portal" icon="browser" href="/guides/customer-portal">
    Where portal links land when you share them.
  </Card>
</CardGroup>