Connect Claude, ChatGPT and other AI apps

AI connectors let the AI app you already use, such as Claude, ChatGPT, Claude Code or Cursor, work with your Sela workspace. Ask it "What's late in Work and who owns it?" or "Which customers asked about delivery this week?" and it answers from your real conversations, customers, work and reports. Ask it to do something, such as create a task or draft a campaign, and it prepares the change as a card that you approve inside Sela. Nothing changes until you do.

Sela connects through the Model Context Protocol (MCP), the open standard these apps use for connectors. Your own AI app does the thinking, so questions you ask it do not use Sela AI credits.

Who can use it#

AI connectors are included in every paid plan, from Inbox up, and in Enterprise. Sandbox workspaces cannot connect apps.

Each person connects their own app. The app acts as that person: it sees only what their role lets them see in Sela, and it can only prepare changes their role could make on the matching screen. When someone's role changes, or they are suspended or removed, their connection follows on the next request.

Owners and admins control connectors for the whole workspace in Settings → AI connectors:

• Allow AI connectors turns connections on or off for everyone. Turning it off stops every connection in the workspace at once; turning it back on lets them work again.
• Allow connected apps to propose changes lets apps prepare change cards. When it is off, apps can still read, and changes already waiting cannot be approved until it is on again.

Connect an app#

Open Settings → AI connectors and copy the Server URL. The page has the same steps for each app, with a copy button for commands. Menu names below follow each app's English interface and can differ slightly between versions.

Claude#

1. In Claude, open Settings → Connectors.
2. Choose Add custom connector, name it Sela, paste the server URL and choose Add.
3. Choose Connect. Sela opens in your browser: sign in, pick the workspace and choose Allow.

On Claude Team and Enterprise plans, an organization owner adds the URL once in the organization's connector settings, then each person chooses Connect and signs in with their own Sela account.

ChatGPT#

1. In ChatGPT, open Settings → Apps & Connectors and turn on Developer mode under Advanced settings.
2. Choose Create, name it Sela, paste the server URL and choose OAuth for authentication.
3. Choose Connect, sign in to Sela and choose Allow.

On ChatGPT Business and Enterprise plans, an admin may need to allow custom connectors first.

Claude Code#

Run this in your terminal, with the server URL from Settings:

claude mcp add --transport http sela <server URL>

Then type /mcp in Claude Code, choose sela and Authenticate. Your browser opens Sela to finish.

Cursor#

In Cursor, open Settings → MCP and add a new MCP server, or add Sela to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "sela": { "url": "<server URL>" }
  }
}

When sela shows that it needs a login, select it, sign in to Sela and choose Allow.

Add the Sela skill#

The connector gives an app Sela's tools. The Sela skill teaches the app how to use them well: how to run a weekly review that compares branches, how to check what is late and who owns it, how to prepare an audience and a campaign for your approval, how to turn a conversation into a work item, review the sales pipeline and lost deals and draft follow-ups for your approval, and how to work with Iraqi Arabic, dinar amounts and a Saturday-first week. It follows the open Agent Skills format, which Claude, ChatGPT, Cursor, GitHub Copilot and VS Code support.

1. Open Settings → AI connectors and choose Download the skill (.zip), or download it from usesela.com/skills/sela-business-operations.zip.
2. Add it in your app. In Claude, open Settings → Capabilities → Skills and upload the zip. In other apps, add it where the app lists skills.
3. Keep the connector connected. The skill only works through the connector's tools and never sees anything your role can't.

The Allow screen#

When an app connects, Sela shows a page that names the app and asks whether it may access your workspace. Check it before choosing Allow:

• The app's name and where you return. Sela shows the address the app will receive the approval at. When that address is on your own computer (Claude Code, Cursor), Sela warns you: continue only if you started the connection yourself from an app on this computer.
• What it can do. Read access covers conversations, customers, work, tasks, approvals, orders and reports. When the app also asks to propose changes, the page says so.
• Workspace. The connection belongs to one workspace. The page uses the workspace you are signed in to; choose another from the list to switch. Connect again to use another workspace.

If the workspace's plan does not include connectors, an admin turned them off, or your role cannot connect apps, the page says so and Allow stays unavailable. Cancel tells the app you declined. A connection request expires after 10 minutes; start again from the app.

What a connected app can read#

A connected app reads the same records you can open in Sela, with the same rules for each of them:

• an overview of the workspace (channels, business hours, branches, plan);
• conversations and their recent messages, and search across records;
• a customer's full picture: profile, conversations, orders, work items, tasks and invoices;
• work and operations: overdue work with its owner and stage, overdue tasks, unassigned or waiting conversations, and customers without a follow-up;
• the sales pipeline over your Work boards (needs permission to read work): open value by board and stage, how long items sit in each stage, stale items, deals won and lost with their value and win rate, lost reasons with your notes, new work by source, and open deals whose customer is waiting for a reply or has gone quiet;
• reports and analytics, team performance, ads results from inquiry to order, and branch comparisons for parent accounts;
• campaigns and audiences, approvals waiting for a decision, and orders;
• with Zoho Books connected and permission to read billing: receivables per currency with how overdue they are, and completed or won work that has no invoice yet (unbilled work works without Zoho too).

Phone numbers are shown or masked exactly as your role shows them in Sela. Apps never receive passwords, API keys or channel credentials. Lists come back in pages of up to 50 rows.

Changes you approve in Sela#

A connected app cannot send, delete or change anything by itself. When you ask it for a change, it prepares the same review card the Sela Companion prepares:

You find each card in three places:

• Home shows how many changes from connected apps are waiting, with Review.
• A notification, by push and in the notification center, says the app prepared a change for your approval. Its link opens the card.
• The app's own chat in the Companion, named after the app (for example Claude · connected app), keeps every card it prepared. Without Companion access, Review on Home opens the cards in a window instead.

Each card shows the fields that will change and what approval does, with the app's name. Choose Approve (or Approve and send for a campaign start or a follow-up message) to commit it, or Cancel to decline. Approval re-checks your role, your plan and the current data, exactly like the Companion; if something changed since the app prepared it, nothing is applied and the card says so. Ask the app to prepare it again.

A card waits 24 hours. The app can check whether you approved it and see the result, including a campaign draft that finishes in the background. Asking for the same change again while a card waits returns the existing card, and one connection can have at most 20 cards waiting. Approving a card from a connected app does not need AI Assist or Companion access; each action keeps its own plan requirement, such as Smart Groups or WhatsApp Marketing.

Only the person who connected the app can see and approve its cards. A teammate cannot approve a card another person's app prepared.

Disconnect an app#

Open Settings → AI connectors. My connections lists every app you connected, with when it was connected, when it was last used and how many requests it made in the last 7 days. Recent calls shows which tools it used and whether they worked. Disconnect removes its access immediately.

Owners and admins also see Everyone in this workspace and can disconnect anyone's app. Disconnecting cancels that app's waiting cards: they can no longer be approved. You can also remove Sela from inside the app; Sela stops the connection the same way. Leaving a workspace ends your connections to it.

Security and privacy#

• Sign-in with OAuth. The app never sees your Sela password. You sign in to Sela yourself and approve the connection; the app receives a token that only works for that one workspace and your account. Tokens are stored by Sela only in scrambled (hashed) form, expire after an hour and are renewed automatically for up to 30 days of inactivity.
• Your permissions, checked on every request. Each request is checked against your current role. Records from other workspaces are never visible.
• Nothing is sent or changed without you. Changes are cards you approve in Sela with your own session. An app that runs tools automatically still cannot approve its own card.
• What Sela keeps. For each request Sela records which tool was used, whether it worked, how long it took and how many rows it returned, for 90 days. It does not store your questions or the answers. What you share in the AI app is handled by that app's provider under their terms.

Limits#

• Each connection can make up to 60 requests a minute.
• Each workspace has a daily request limit by plan: 1,000 on Inbox, 5,000 on Operations and 20,000 on Scale.
• A single result is limited in size; ask for a narrower period or a smaller list if the app says a result was cut.
• Apps can propose the changes in the table above. Settings such as business hours or the customer assistant's identity are changed in Sela or with the Sela Companion.

If the app says Sela refused a request, the message explains why, for example that your role cannot make that change or that the workspace turned proposals off.