eDesk MCP Server
Tickets, replies, orders and tags in your eDesk, worked by your agent.
Hosted MCP Server
npx add-mcp 'https://cotlet.dev/mcp/v1/edesk'Installs into Claude Code, Codex, Cursor and more
Documentation
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
eDesk API and MCP server: Let your AI agent clear the eDesk Mailbox.
eDesk has no MCP server (checked 27 Oct 2026). Its Open API 2.0 lists 42 operations for tickets, messages, orders, tags and templates, but eDesk Help says you "need to be on the eDesk Enterprise plan" and an Admin has to create the token. Cotlet runs 11 eDesk tools hosted, over MCP for agents and REST for scripts, on any eDesk plan.
Tickets, replies, orders and tags in your eDesk, worked by your agent. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.
- Free 7-day trial, no card
- Unofficial, not affiliated with eDesk
- Page: https://cotlet.dev/integrations/edesk-api-mcp-server
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by eDesk. eDesk is a trademark of its owner. If eDesk's own integrations cover what you need, use them first.
What can you automate in eDesk?
- Triage new tickets by what the buyer wrote
- Answer where-is-my-order with real tracking
- Chase customers who went quiet in Waiting
- Flag negative feedback for a manager
- List returns and cancellations by channel
- Assign owners and add tags in bulk
Does eDesk have an MCP server or an API?
- API tokens expire after 90 days by default, and every tool built on one stops until an Admin makes a new token.
- The API has no free-text ticket search, no snooze and no mention. Its ticket statuses (Open, Pending, Closed) are not the Mailbox sections you see.
- eDesk's own AI Agent answers inside eDesk at $0.99 per outcome on every plan, but your own agent cannot call it or hand it work.
| What you need | eDesk API (Enterprise) | eDesk AI Agent | Cotlet |
|---|---|---|---|
| Read tickets and orders | Yes | Inside eDesk only | Yes |
| Reply with tracking | Yes, you build it | Yes, $0.99 a ticket | Yes, after your OK |
| Search by customer or SKU | Filters only | No | Yes |
| Snooze or mention a teammate | No | No | Yes |
| Driven by your own agent | With your own code | No | Any MCP client |
| What you need first | Enterprise, custom price | Any plan | Any plan |
Checked 27 Oct 2026. Sources: Getting started with the eDesk API (eDesk Help), How to generate a token for the eDesk API (eDesk Help), eDesk Open API reference, eDesk pricing
How does Cotlet connect to eDesk?
- Sign in to eDesk. Use your own account in its Cotlet Cloud Browser.
- Choose MCP or REST. Connect your agent or create a Cotlet API key.
- Run your workflow. Ask your agent or send an HTTP request.
We never keep your eDesk password, and no reply, note or ticket change is saved before you approve it.
Connect eDesk to your agent or workflow
Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.
- Sign in to eDesk in a Cloud Browser. Create a Cotlet account, open eDesk in its Cloud Browser, sign in with your own eDesk user on any plan and press Enable for agents.
- Add the Cotlet address. Paste https://cotlet.dev/mcp/v1 into the MCP server or connector field of your agent.
- Approve the connection. Chat apps send you to a Cotlet sign-in page. Code editors, n8n and scripts send an API key from the console.
https://cotlet.dev/mcp/v1 serves every app you enable on Cotlet, eDesk included. Enable eDesk after connecting and the connector needs a refresh before its tools show up.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY"
ChatGPT:
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Cursor:
// ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n:
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: edesk_read
Make, Zapier:
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: edesk_write
How to use the eDesk REST API
Create your Cotlet API key
Create a Cotlet API key with access to eDesk and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Connect eDesk in Cotlet and enable it for agents. Account access: Your own eDesk login (Basic role or higher to reply, as shown in eDesk Help). You sign in in your own browser and keep your own password and 2-step verification.
Make your first eDesk API request
REST:
curl "https://cotlet.dev/api/v1/edesk/tickets?limit=5" \
-H "Authorization: Bearer $COTLET_API_KEY"
Read tickets and apply the operation limits
A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.
Illustrative response excerpt:
{
"status": "success",
"app": "edesk",
"tool": "list_tickets",
"result": {
"tickets": [
{
"ticket_id": 48199,
"subject": "Parcel has not arrived",
"status": "waiting",
"type": "Shipping query",
"channel": "Amazon UK - Brightside Home",
"customer": "Emma Wright",
"owner": null,
"tags": [],
"replies": 1,
"order_number": "026-3350917-1184029",
"last_updated_at": "2026-10-12 08:15:00"
},
{
"ticket_id": 48177,
"subject": "Item arrived with a cracked lid",
"status": "waiting",
"type": "Return request",
"channel": "eBay UK - Brightside Home",
"customer": "Tom Hale",
"owner": "Marco Silva",
"tags": [
"Returns"
],
"replies": 2,
"order_number": "15-11874-62103",
"last_updated_at": "2026-10-11 16:40:00"
}
],
"next_cursor": null
}
}
Lists tickets the way the Mailbox shows them. status picks the section: new (never answered), to_do, waiting, snoozed, resolved or spam. query searches customer details (name, email, phone) and order details (product name, SKU, order ID) like the Search bar. type is the ticket type as eDesk names it, for example Shipping query, Return request, Cancellation or Negative feedback. last_updated_at is the time of the latest message on the ticket. Pass next_cursor back as cursor for the next page.
Use ticket_id with get_ticket, reply_to_ticket and update_ticket.
limit: How many items to return per page.
cursor: Next page cursor from the previous call.
Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.
eDesk workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | One ticket with its messages and internal notes, customer, tags and the order panel with tracking. Use get_ticket in your configured support report. |
| Make | HTTP > Make a request | One order with items, status, dates, delivery address, tracking code and carrier. Use get_order in your configured support report. |
| Python or Node.js | REST API | Reply templates from Settings, Smart Tools, Templates, with text and usage. Use list_templates in your configured support report. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads eDesk; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.
Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.
The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.
eDesk API endpoints and MCP tools
Tickets, replies and notes
A reply goes out on the channel the ticket came from, such as Amazon or eBay messaging, and cannot be unsent. A ticket has one owner; a new one replaces the old.
- List tickets (
list_tickets, read): Tickets in the Mailbox by section, channel, type, owner or tag, with status, order number and reply count. - Get ticket (
get_ticket, read): One ticket with its messages and internal notes, customer, tags and the order panel with tracking. - Reply to ticket (
reply_to_ticket, write, asks first): Send a reply to the customer from the ticket, with the send status you choose. - Add internal note (
add_internal_note, write, asks first): Add a note to the ticket that only your teammates see. - Update ticket (
update_ticket, write, asks first): Set owner, tags and status, snooze the ticket or mention a teammate.
Orders and tracking
Amazon hides buyer names and addresses from sellers, so ship_to stays thin on Amazon channels.
- List orders (
list_orders, read): Orders from the All Orders page, filtered by search text, status, channel or date, with items and ticket link. - Get order (
get_order, read): One order with items, status, dates, delivery address, tracking code and carrier.
Templates, team, tags and channels
Read only. Message Rules, templates and channels stay as your Admin set them.
- List templates (
list_templates, read): Reply templates from Settings, Smart Tools, Templates, with text and usage. - List users (
list_users, read): Teammates of your eDesk account with their role. - List tags (
list_tags, read): Tags and tag groups in your eDesk account. - List channels (
list_channels, read): Channels connected to eDesk: marketplaces, webstores and email.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/edesk-api-mcp-server#tools
Who can see my eDesk session, and how do I revoke it?
- What we store. Your signed-in eDesk profile, encrypted with AES-256-GCM, in Finland. Never the password.
- What your agent gets. 11 eDesk tools. No cookie, no login, no API token.
- What the session sees. What your eDesk role sees. A Read-only user cannot reply, so sign in as Basic or higher.
- What no tool touches. Message Rules, AI Agent settings, channels, billing, ticket merges and deletes.
- If eDesk signs you out. We email you a sign-in link. You sign in and pass 2-step verification yourself.
- How to cut access. Disable for agents, reset the browser or delete the key. The next call fails.
Tickets carry buyer names, emails and order details, so the agent reads personal data your marketplaces share with you. eDesk is an Irish company and Cotlet a Polish one, both under GDPR, and our DPA applies to business accounts without a signature. The Cotlet site has A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Approvals, undo and mistakes
- Reads the question. Shipping query tickets in To Do, with the order eDesk linked to each.
- Checks the parcel. Tracking, carrier and the latest expected date against today.
- Waits for your OK. Each on-time reply waits in your Cotlet console, in your Delivery update wording.
- Reports back. Who got tracking, and the late or untracked parcels left for you.
| Action | Undo |
|---|---|
| Reply to a ticket | None; the buyer has it. Send a correction |
| Add an internal note | No tool removes it; teammates may have read it |
| Assign an owner | Assign the old owner back; both saw the change |
| Add tags | Remove them in eDesk; the tool only adds |
| Resolve or mark as spam | Set the status back to to_do |
All 3 write tools ask first, because a reply reaches the buyer and a new owner or a mention notifies a teammate. Reads run at once. For a scheduled run you can switch the wait off per tool, for example for update_ticket during triage.
eDesk sends replies with your default send status, often Resolved. The agent passes waiting, so a ticket comes back to To Do when the buyer answers.
MCP call:
{
"name": "reply_to_ticket",
"arguments": {
"ticket_id": 48210,
"body": "Hi Emma, your order 203-7718305-2294466 was dispatched on 9 October with Royal Mail. Tracking code: HB204418830GB. It should reach you by 14 October. Reply here if it has not arrived by then.",
"send_status": "waiting"
}
}
REST:
curl -X POST https://cotlet.dev/api/v1/edesk/tickets/48210/replies \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"body":"Hi Emma, your order 203-7718305-2294466 was dispatched on 9 October with Royal Mail. Tracking code: HB204418830GB. It should reach you by 14 October. Reply here if it has not arrived by then.","send_status":"waiting"}'
Response:
{
"message_id": 771209,
"ticket_id": 48210,
"kind": "reply",
"status": "waiting",
"sent_at": "2026-10-20 09:05:00"
}
An order system or a nightly script can call the same tools over REST at /api/v1/edesk, with one key and one price, and no Enterprise token. A call your eDesk role may not make returns an error and costs nothing. Every tool row above lists its REST path.
How much does the eDesk MCP server cost?
About $72 a month for a seller with 2 support agents and about 400 tickets, 12,440 credits. Works on eDesk Essential, from $39 an agent a month billed yearly.
| Job | Calls | Credits |
|---|---|---|
| Triage what Message Rules left in New, daily | 16 × 30 | 4,800 |
| Answer on-time where-is-my-order tickets, daily | 13 × 30 | 3,900 |
| Chase Waiting tickets, 3 times a week | 12 × 12 | 1,440 |
| Returns and cancellations digest, weekly | 13 × 4 | 520 |
| Flag negative feedback for a manager, weekly | 7 × 4 | 280 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 12,440 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- No Enterprise plan or API token needed
The month is our example: about 5 tickets a day that rules left in New, 4 on-time shipping questions a day, Waiting checked three times a week, and two weekly reports. A third-party test of a small Amazon, eBay and Shopify seller counted about 380 conversations a month. Dollars at the $29 pack rate. eDesk's AI Agent would charge $0.99 for each ticket it answers.
eDesk MCP server on GitHub, Make or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| Hamelyn-SL/edesk-cli | A Rust command line for all 40 Open API endpoints, MIT. 0 stars, last commit 2 Jul 2026. | Needs an Enterprise token; a CLI, not an MCP server. |
| eDesk by Maxmel Tech | A community Make app: tickets, messages, orders, tags, templates, polling Watch triggers. | Same Enterprise token; no snooze or mention. |
| eDesk AI Agent | eDesk's built-in agent answers and acts on tickets by your procedures. | $0.99 per outcome; lives inside eDesk, your own agent cannot direct it. |
On Enterprise with a developer, the Open API is the direct route. If you want eDesk to answer simple tickets by itself, its AI Agent does that per outcome. If your own agent should triage, reply with tracking and chase Waiting tickets on any plan, Cotlet does that hosted. Zapier, n8n and Pipedream have no eDesk app.
Who runs Cotlet
Take Group sp. z o.o. runs Cotlet: a software company registered in Poland, EU (VAT PL6342984273), in business since 2019. The founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the eDesk tools go to contact@cotlet.dev.
eDesk API and MCP: questions
How do I get access?
Sign up free at https://cotlet.dev, open eDesk under Integrations in the console and sign in to eDesk in its Cloud Browser. The trial starts when you sign up and needs no card.
How do I connect eDesk to ChatGPT or Claude?
Sign up at cotlet.dev, log in to eDesk once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your eDesk account through Cotlet, in their phone apps too.
What can ChatGPT do in eDesk?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in eDesk: triage new support tickets; answer where-is-my-order tickets; follow up on waiting tickets. You ask in plain words, and anything that reaches other people waits for your OK first.
Do I need eDesk Enterprise to use this?
No. eDesk's own API and API tokens need the Enterprise plan and an Admin login (eDesk Help: Getting started with the eDesk API). Cotlet works in your own eDesk login on your plan instead. Your role still counts: eDesk Help says replying and creating tickets need Basic mailbox access or higher, and Read-only users cannot.
What can it not do?
Nothing creates a ticket, merges tickets, sends a bulk reply, schedules a send or attaches files. Message Rules, templates and channels are read only or out of reach, and Cotlet changes no settings. A sent reply cannot be unsent, which is why each reply asks for your OK by default.
Does eDesk have webhooks?
No. The Open API lists no webhook or event subscription, and the community Make apps poll. To act on new tickets, run your agent on a schedule and read the Mailbox.
Does it work during the eDesk trial?
Yes, but eDesk runs its 14-day trial in Safe Mode, where messages are not stored or sent. Replies go out only after you turn Safe Mode off.
Is the MCP server different from the REST API?
Only in how you call it. Both expose the same 11 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and order systems use REST.
Is Cotlet affiliated with eDesk?
No. Cotlet is independent and not affiliated with eDesk.
Can I use the eDesk API without an AI agent?
Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.