Use Supersei CRM with Claude
Connect Claude to your Supersei workspace and ask for what you need in plain language. Claude acts as you, with exactly your permissions.
Connect in two minutes
Claude.ai, Claude Desktop and mobile
- Open claude.ai, then Settings → Connectors.
- Choose Supersei CRM from the directory, or add a custom connector with the URL
https://api.supersei.com/mcp. - Click Connect. Enter the email you use for Supersei and the 6-digit code we send you.
- If your email belongs to more than one workspace, pick the one to connect.
- Start a chat, make sure the Supersei connector is enabled, and ask: "Who am I connected as?"
Claude Code and other developer tools
An admin creates an API key in Settings → API keys, then registers the server:
claude mcp add --transport http supersei-crm https://api.supersei.com/mcp --header "Authorization: Bearer ilcrm_YOUR_KEY"
Any MCP client that supports Streamable HTTP with OAuth 2.1 or a bearer token can connect the same way.
What you can ask
Claude reads and runs your workspace through the same API the Supersei web app uses. A few examples by area:
| Area | Try asking |
|---|---|
| Leads and pipeline | "Which Demo booked leads have had no activity for 5 days?""Move Rahul Mehta to Negotiation and assign him to Asha" |
| Tasks and meetings | "Remind me to call Sunil tomorrow at 11""Book a 30-minute demo with Neha on Thursday 4pm" |
| Calls | "Call Amit now""What did Amit say about pricing on the last call?" |
| WhatsApp, email, inbox | "WhatsApp Priya the pricing link and say I will call at 5""Reply to the unread web chat from Kavya" |
| Campaigns and sequences | "How many Proposal sent leads have not replied in 7 days? Draft a WhatsApp campaign to them"(launches only after you confirm the count) |
| Reports | "Run my morning standup""Weekly review for my team""Revenue by owner for August" |
| Deals and customers | "Create a payment link for Priya for INR 24,000""Which renewals are due this month?" |
| Workspace setup (admins) | "Add a Proposal sent stage after Demo attended""Create a Field rep role that only sees its own leads" |
How permissions work
- Claude signs in as you. An agent sees their own leads, a manager their team, an admin the organisation.
- Plan-aware. Modules not in your plan answer "feature not included".
- Single actions confirm first. Messages, calls and bookings go out immediately, so Claude shows the exact text or slot and waits for your yes.
- Bulk actions are drafts. Campaigns, drips and imports are prepared as drafts and need a confirmed count before anything is sent.
- Deletes are two-step. Deleted leads go to a recycle bin and can be restored.
- Everything is on the timeline. Every change appears on the lead timeline with your name, exactly like an action in the web app.
Change a person's role in Settings → Roles and their Claude access follows within a minute. Deactivating a user ends their connection at once.
Disconnecting
- From Claude: Settings → Connectors → Supersei CRM → Remove.
- From Supersei: Settings → API keys → revoke the key named Claude connector - …. Access stops immediately.
- Connections expire after 90 days; simply connect again.
Troubleshooting
| Problem | What to do |
|---|---|
| No code arrives | Check spam. Codes are only sent to addresses with a seat in a Supersei workspace; ask your admin to invite you first. |
| "That code is incorrect or has expired" | Request a new code. Each one works for a few minutes and a few attempts. |
| Claude says it is not authenticated | The connection was revoked or expired. Reconnect from Settings → Connectors. |
| Claude says "forbidden" | Your role does not include that capability. An admin can grant it in Settings → Roles; it applies within a minute. |
| Anything else | Email support@supersei.com with the date, time and what you asked Claude. |
Privacy and security
The connector uses OAuth 2.1 with PKCE; no passwords are typed into Claude. Data flows only between Claude and Supersei for the request being made, and the connector keeps no copies of your CRM data. Every request is logged with the organisation, user and outcome, never the credential. See our Privacy Policy and Security Overview.