Skip to content

CRM

Sellsy MCP connector

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

  • App credentials
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

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

Working in Sellsy with Elaichi

  • List all Sellsy comments
  • Get single Sellsy comment by ID
  • List all Sellsy search comments
Ask anything…
Governance / Audit log Last 24 hours
Sellsy List all Sellsy search comments Emily Carter · ChatGPT · 9:41 AM Done
Sellsy Get single Sellsy comment by ID Emily Carter · ChatGPT · 9:41 AM Done
Sellsy List all Sellsy comments Emily Carter · ChatGPT · 9:41 AM Done
Sellsy Create a Sellsy comment Megan Brooks · Claude · 9:38 AM Done
Sellsy Update a Sellsy comment by ID Ryan Hayes · Cursor · 9:35 AM Done

How to connect Sellsy to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Sellsy MCP connector for 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.

Sellsy MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

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

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Sellsy MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.

Sellsy MCP connector for 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.

Sellsy MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

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

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

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.

What teams do with Sellsy through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Sellsy is logged.

  • 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 →

What connecting Sellsy gets you

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

Elaichi Agent

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, Cursor or Microsoft Copilot

The agent

Ask Sellsy questions, get answers from live records.

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

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

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

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One endpoint puts Sellsy in every MCP client.

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

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.

Tool catalog

327 Sellsy tools, ready with no code.

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

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

Toolboxes

Each team gets its own Sellsy toolbox.

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

ElaichiConnections
Connection Scope Status Access
SE

Sellsy (Sales France)

Connected by Emily Carter

Personal • Active 1 team · 6 members
SE

Sellsy (Sales EMEA)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
SE

Sellsy (Finance)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
SE

Sellsy (Support)

Connected by Tyler Reed

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

Sellsy (Account management)

Connected by Ryan Hayes

Personal • Active Not shared
SE

Sellsy (Operations)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Teammates work in Sellsy without seeing a credential.

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

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Sellsy Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Sellsy Companies Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Sellsy Companies List Toolbox

Audit log

Every Sellsy change names who made it.

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

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.

Sellsy digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    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 Jake Morgan

    Approve
  6. Post the digest

    Sellsy

    Queued

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 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%

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.

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Sellsy

All three can connect Sellsy to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Sellsy, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Sellsy tools Allow or restrict single Sellsy tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Sellsy call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

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.

Questions, answered

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, Microsoft Copilot, 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 restricting deletes or edits to addresses. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.

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, Microsoft Copilot and the Elaichi Agent in one step.

Does the Sellsy MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Sellsy is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Sellsy?

Yes. Both let Claude, ChatGPT or Cursor use Sellsy. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Sellsy call.

How is Elaichi different from Composio for Sellsy?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Sellsy: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Sellsy in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot