eDesk logo edesk.com

Live

eDesk API and MCP server

eDesk opens its API only on the Enterprise plan, and gives agents no ready tools for tickets, replies or orders. Sign in to eDesk once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.

Sign up free View as Markdown

Not affiliated with eDesk.

eDesk has no API for this. So we run one for you.

eDesk's own API, a GitHub MCP server and Cotlet compared
What you need eDesk's APIGitHub MCP serverCotlet
Tickets, replies, tags, orders No Partly Yes, 11 tools
Acts as you, signed in 24/7 No No Yes, Cloud Browser
Fixed for you when eDesk changes N/A No Yes, tested every 6h
Runs with your laptop off N/A No Yes, hosted

Checked Oct 20, 2026. Sources: eDesk Help: Getting started with the eDesk API · eDesk Help: How to generate a token for the eDesk API · eDesk developers: API reference · eDesk developers: Create Message

Your own Cloud Browser, on 24/7. Sign in once. We keep it connected.

  1. 01Sign in to eDesk in your own Cloud Browser

  2. 02Connect it for your agents

  3. 03Cotlet keeps it signed in and working

How do I connect eDesk to Claude, ChatGPT or my code?

AI agents connect over MCP, scripts call the REST API. Both reach the same 11 tools with one API key.

For AI agents: MCP

Add Cotlet to your agent once. eDesk and every other app you connect show up as its tools.

  • Claude
  • ChatGPT
  • OpenClaw
  • Hermes
  • GrokBot
  • Cursor
  • n8n
  • Any MCP client
  1. 1

    Add Cotlet to your agent

    Claude Code
    claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
    Cursor
    {
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
    Codex
    # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

For scripts: REST API

Every tool is an endpoint under /api/v1/edesk with its own method and path, such as POST /api/v1/edesk/tickets/{ticket_id}/replies, with the same API key. Our open-source repo has ready scripts to start from.

REST API docs

What can the eDesk API and MCP server do?

11 tools on your own eDesk account. Agents call them as operations of the MCP tools edesk_read and edesk_write; scripts call each one at its own REST endpoint, with the same inputs and answers.

API reference
eDesk tools in Cotlet's MCP server and REST API
Tool What it does Access
list_tickets Tickets in the Mailbox by section, channel, type, owner or tag, with status, order number and reply count. read
get_ticket One ticket with its messages and internal notes, customer, tags and the order panel with tracking. read
list_orders Orders from the All Orders page, filtered by search text, status, channel or date, with items and ticket link. read
get_order One order with items, status, dates, delivery address, tracking code and carrier. read
list_templates Reply templates from Settings, Smart Tools, Templates, with text and usage. read
list_users Teammates of your eDesk account with their role. read
list_tags Tags and tag groups in your eDesk account. read
list_channels Channels connected to eDesk: marketplaces, webstores and email. read
reply_to_ticket Send a reply to the customer from the ticket, with the send status you choose. writeasks first
add_internal_note Add a note to the ticket that only your teammates see. writeasks first
update_ticket Set owner, tags and status, snooze the ticket or mention a teammate. writeasks first

Scroll the table for all 11 tools.

Ask in plain words. Your agent does the rest.

All eDesk use cases

Is it safe to connect eDesk?

You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.

Security overview

How much do the eDesk API and MCP server cost?

One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Most calls use 25 credits, and your Cloud Browser uses 50 credits a day while eDesk is enabled for agents, so 20 calls a day come to 550 credits.

See full pricing
Cotlet credit packs: price, credits and calls at 25 credits each
Credits Price, one time Calls at 25 credits Per 1,000 credits
5,000 $29 200 $5.80
15,000 $79 600 $5.27
32,000 $149 1,280 $4.66
60,000 $249 2,400 $4.15

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.

Questions

Does eDesk have an API?

eDesk has a full REST API but no MCP server (checked 20 Oct 2026). Its docs and help center list none. The API needs the Enterprise plan, and an Admin has to create the API token under Settings > API Tokens. So on any other plan there is no API at all.

How do I get access?

Sign up free, open eDesk under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.

Is the MCP server different from the API?

No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 11 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.

What is the Cloud Browser?

Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to eDesk yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so eDesk sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.

Can my agent act without asking me?

Not on anything that reaches other people: reply_to_ticket, add_internal_note, update_ticket wait for your OK by default. You can switch that off per tool for scheduled runs.

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.

Should I use a eDesk MCP server from GitHub instead?

Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when eDesk changes. Pick Cotlet if you want it hosted and kept working for you.

Can I use it in n8n, Make or Zapier?

Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.

Who runs Cotlet?

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

Is Cotlet affiliated with eDesk?

No. Cotlet is independent and not affiliated with eDesk.

Give your agent access to eDesk.

Free 7-day trial with 2,000 credits, no card needed.

Sign up free