eDesk MCP connector
Connect eDesk to Claude, ChatGPT, Cursor, and any MCP client through Elaichi, so support tickets, customer contacts, sales orders, and order notes can be found, updated, and tagged by an AI agent working inside each person's own eDesk access.
-
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.
39 tools
How to connect
How to connect eDesk to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect eDesk once
-
Open Connections, choose Add connection, and pick eDesk.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste an eDesk API key. One person generates a token in eDesk 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.
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.
eDesk MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
eDesk MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
eDesk MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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 eDesk to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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 eDesk through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Support
Catch a ticket up after a customer reply
Ask for the ticket by number, hear what the customer last said, and have the agent update its status and tags so the queue reflects where things actually stand.
-
Support
Tag and sort the morning queue
Pull every open eDesk ticket that came in overnight, group them by channel or complaint, and apply the right tags so the team picks up the urgent ones first.
-
Operations
Check the order behind a complaint
Look up the sales order tied to a ticket, confirm what was bought and when, and answer the customer without switching between eDesk and the storefront.
-
Fulfillment
Leave an order note everyone sees
After a reship or a refund decision, add a note to the eDesk sales order so the next person who opens the ticket knows what has already been done.
-
Team leads
See what each agent is carrying
List eDesk users and the tickets sitting with each of them, spot who is overloaded, and rebalance before response times slip.
-
Marketplace
Log a ticket from an outside message
When a buyer reaches out through a channel eDesk does not catch on its own, create the ticket and contact in eDesk so nothing is answered off the record.
Try asking
- “Show open eDesk tickets tagged urgent this week.”
- “Which channels sent the most tickets yesterday?”
- “Tag ticket 4821 as refund and summarize the thread.”
Compare
Elaichi vs Zapier MCP vs Composio for eDesk
All three can connect eDesk to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| 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 eDesk tools | Allow or restrict single eDesk 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 eDesk 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 | $15 per user per month. | 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.
AI tools
eDesk tools for your AI agents
39 tools are ready to call through Elaichi's MCP endpoint the moment you connect eDesk, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting eDesk gets you
6 screens from the product, each doing one job for your eDesk account.
The agent
Ask about tickets, read the answer.
Plain questions return live eDesk tickets, tags and contacts, no query syntax.
- tickets
- tags
- contacts
- channels
Ask Elaichi to work across your apps.
Show open eDesk tickets tagged urgent this week.
Which channels sent the most tickets yesterday?
Tag ticket 4821 as refund and summarize the thread.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach eDesk.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
39 eDesk tools ready to call.
Tickets, tags, contacts, channels and users, listed with methods and no custom code.
- List all eDesk users
- List all eDesk tags
- Get single eDesk tag by ID
- Create a eDesk tag
ElaichiToolsToolboxes
Every team gets its own toolbox.
Curate eDesk tickets, tags and channel tools per team from one place.
- Support
- Escalations
- Quality
- Marketplace ops
ElaichiToolboxesShared connections
Share eDesk access, never the credential.
Teammates handle tickets through a connection someone else connected and owns.
- Support EMEA
- Support US
- Escalations
- Marketplaces
ElaichiConnectionsAudit log
Every eDesk call is on record.
When, who, what happened, type and resource, appended for each ticket change.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching 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 drafts your ticket digest.
Fetch eDesk tickets, group them, draft a digest, approve, post it back.
eDesk digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch tickets
eDesk
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
eDesk
Queued
Collections and dashboards
eDesk ticket health, counted not guessed.
Four metrics, 14 days of tickets created and a team breakdown, refreshed on schedule.
eDesk health
Refreshed 4 minutes ago · every 15 minutes · from the tickets collection
Tickets
1,284 ↓ 12%
Tags
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Tickets created
Last 14 days
By team
Share of activity
Support EMEA 34%
Support US 27%
Escalations 21%
Marketplaces 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect eDesk to Claude?
In Elaichi, choose eDesk from the connector list and paste in an API key from your eDesk account; there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi, and from then on your eDesk tickets, contacts, and sales orders are available in the conversation.
Does eDesk work with ChatGPT and Cursor as well as Claude?
Yes. Once eDesk is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect eDesk once and every client you use picks it up.
What can an AI agent actually do with my eDesk data?
An agent connected to eDesk can find and read tickets, contacts, channels, sales orders, and order notes, then create or update tickets, add tags, and leave notes on orders. In practice that means asking for the open tickets from one marketplace, checking the order behind a complaint, or tagging a batch of tickets after a product recall. eDesk has a lot of things an agent can do, so short concrete asks such as "tag ticket 4821 as refund" work better than long paragraphs.
Does connecting eDesk give the AI access to every mailbox and channel?
No. Every request runs as the person who signed in, so an agent only sees the eDesk tickets, channels, and sales orders that person's own eDesk account can already see. Elaichi can narrow that further, for example to read only, but it can never widen it beyond what eDesk itself allows that person.
Can I stop an agent from deleting or changing things in eDesk?
Yes. Restrictions in Elaichi apply per action, so you can allow reading eDesk tickets and sales orders while blocking deletion, or block any change at all for a given team. A blocked action is never shown to Claude, ChatGPT, or Cursor in the first place, so no prompt, however worded, can reach it.
What happens to an eDesk connection when someone leaves?
When you offboard someone in Elaichi, their access to eDesk through every AI client ends at once. If they had shared an eDesk connection with the team, it keeps working for everyone else. If you want eDesk gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Does the eDesk MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. eDesk 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, 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 eDesk?
Yes. Both let Claude, ChatGPT or Cursor use eDesk. 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 eDesk call.
How is Elaichi different from Composio for eDesk?
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 eDesk: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put eDesk in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.