Skip to content

CRM

Sellsy MCP connector

The Sellsy connector brings companies, contacts, comments, addresses and payments into Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can read and update Sellsy records inside their own access, with every call logged.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Sellsy to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Sellsy once

  1. Open Connections, choose Add connection, and pick Sellsy.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Sellsy API key. One person generates a token in Sellsy and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

sellsy
Sellsy
Affinity
Attio
EveryAction
Google Contacts
Highlevel
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Connect Sellsy to Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Connect Sellsy to ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Connect Sellsy to Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Sellsy to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Sellsy through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Sales

    Catch the company record up after a call

    Tell the agent what happened on the call and it adds a comment to the Sellsy company, so the history is current before the next touch.

  • Sales

    Turn a prospect into a client

    When the deal closes, ask the agent to convert the prospect in Sellsy and confirm the billing address and main contact are in place.

  • Finance

    Log a payment against the right company

    Paste the remittance details and the agent records the payment on the Sellsy company, then leaves a comment noting who confirmed it.

  • Support

    Find who to call at a company

    Ask for the contacts at a Sellsy company and get names, roles and details in the chat, without opening another tab.

  • Operations

    Fix addresses before a mailing

    Ask for Sellsy companies with a missing or outdated delivery address and correct them from a list, one at a time or in a batch.

  • Leadership

    Pull an export of companies for review

    Ask for a Sellsy companies export using one of your saved filters and have the agent summarize what changed since last month.

Try asking

  • “Add a comment to Acme Industries about today's renewal call”
  • “Which contacts do we have at Dupont Logistique?”
  • “Convert Maison Verte from prospect to client and check its billing address”

See all 327 Sellsy tools below

AI tools

Sellsy tools for your AI agents

327 tools are ready to call through Elaichi's MCP endpoint the moment you connect Sellsy, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Sellsy gets you

6 screens from the product, each doing one job for your Sellsy account.

The agent

Ask Sellsy questions, get answers from live records.

Type a plain question and the agent reads companies, contacts and comments in Sellsy.

  • companies
  • contacts
  • comments
  • addresses

Ask Elaichi to work across your apps.

Add a comment to Acme Industries about today's renewal call

Which contacts do we have at Dupont Logistique?

Convert Maison Verte from prospect to client and check its billing address

Also runs in Claude, ChatGPT or Cursor

MCP clients

One endpoint puts Sellsy in every MCP client.

Claude, ChatGPT and Cursor reach Sellsy through one governed endpoint, no SDK, no shared key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

327 Sellsy tools, ready with no code.

Companies, contacts, comments, addresses and payments, every method cataloged and searchable.

  • List all Sellsy comments
  • Create a Sellsy comment
  • Get single Sellsy comment by ID
  • Update a Sellsy comment by ID
ElaichiTools
Tool Action Description
List all Sellsy comments List List comments in Sellsy. Returns comment records with id, owner, description, created, and updated.
Create a Sellsy comment Create Create a comment in Sellsy. Returns the created comment record with id, owner, description, created, and updated. Required: description.
Get single Sellsy comment by ID Get Get a single Sellsy comment by id. Returns the comment record with id, owner, description, created, and updated. Required: id.
Update a Sellsy comment by ID Update Update a Sellsy comment by id. Returns the updated comment record with id, owner, description, created, and updated. Required: id.
Delete a Sellsy comment by ID Delete Delete a comment in Sellsy by id. Returns an empty 204 response on success. Required: id.

Toolboxes

Each team gets its own Sellsy toolbox.

Sales, finance and support each see the Sellsy tools their work calls for.

  • Sales
  • Account management
  • Finance
  • Support
ElaichiToolboxes
Name Source template Tools Created

Sales toolbox

Sellsy · companies and prospects

Sellsy starter 18 Mar 4, 2026

Account management toolbox

Sellsy · contacts and comments

9 Mar 2, 2026

Finance toolbox

Sellsy · payments and billing addresses

24 Feb 27, 2026

Support toolbox

Sellsy · contacts and comment history

Sellsy starter 6 Feb 19, 2026

Operations toolbox

Sellsy · addresses and exports

31 Jan 30, 2026

Marketing toolbox

Sellsy · company lists and saved filters

12 Jan 22, 2026

Shared connections

Teammates work in Sellsy without seeing a credential.

One person connects the Sellsy account and shares it with teams and members.

  • Sales France
  • Sales EMEA
  • Finance
  • Support
ElaichiConnections
Connection Scope Status Access
SE

Sellsy (Sales France)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
SE

Sellsy (Sales EMEA)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
SE

Sellsy (Finance)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
SE

Sellsy (Support)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
SE

Sellsy (Account management)

Connected by Clara Nowak

Personal • Active Not shared
SE

Sellsy (Operations)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every Sellsy change names who made it.

When, who, what happened, type and resource, for every call in an append-only log.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Sellsy Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Sellsy Companies Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Sellsy Companies List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule runs Sellsy work end to end.

New companies are fetched, grouped, drafted into a digest, approved, then posted back to Sellsy.

Sellsy digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch companies

    Sellsy

    1.4s
  3. Group by owner

    Transform

    0.1s
  4. Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Sellsy

    Queued

Collections and dashboards

Sellsy health numbers arrive without anyone asking.

Four metrics, 14 days of companies created and a team breakdown, refreshed on schedule, no model.

Sellsy health

Refreshed 4 minutes ago · every 15 minutes · from the companies collection

Live

Companies

1,284 ↓ 12%

Contacts

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Companies created

Last 14 days

By team

Share of activity

Sales France 34%

Sales EMEA 27%

Finance 21%

Support 18%

FAQ

Frequently asked questions

How do I connect Sellsy to Claude?

Connect Sellsy in Elaichi first, which means pasting the API key from your Sellsy account, since there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Sellsy companies, contacts and comments are available in Claude.

Does Sellsy work with ChatGPT and Cursor as well as Claude?

Yes. Sellsy is connected once in Elaichi and the same endpoint, https://api.elaichi.ai/mcp, is pasted into Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. There is nothing to set up again per client.

What can an AI agent actually do with my Sellsy data?

An agent can look up Sellsy companies and their contacts, add or edit comments after a call, correct an address, record a payment, convert a prospect into a client and pull an export of companies. Because Sellsy has hundreds of actions, the agent searches for the right one as you ask, so short concrete asks like "add a comment to Acme about today's call" work better than long paragraphs.

Does connecting Sellsy give the AI access to everything in my Sellsy account?

No. Every call to Sellsy runs as the person who signed in, so the agent sees the companies, contacts and payments that person can already see in Sellsy, and nothing more. Elaichi can narrow that further with roles and restrictions, but it can never widen access beyond what Sellsy itself grants.

Can my team share one Sellsy connection?

Yes. One person connects Sellsy in Elaichi and shares the connection with a team, and nobody else ever handles the Sellsy API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every change to a Sellsy company or contact.

Can I stop an agent from deleting or changing things in Sellsy?

Yes. Restrictions in Elaichi apply per action, so you can allow reading Sellsy companies and adding comments while blocking deletes or edits to addresses. A blocked action is never advertised to Claude, ChatGPT or any other client, so no prompt can reach it.

What happens to a Sellsy connection when someone leaves the company?

Offboarding that person in Elaichi ends their access to Sellsy at once, across every client they used. A shared Sellsy connection keeps working for everyone else on the team. If you disconnect Sellsy in Elaichi, it disappears from Claude, ChatGPT, Cursor and the Elaichi Agent in one step.

Put Sellsy in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.