Skip to content

Helpdesk

Desk365 MCP connector

The Desk365 connector brings your helpdesk tickets, replies, notes, contacts, companies and time entries to Claude, ChatGPT, Cursor and the Elaichi Agent, so each agent signs in as themselves and works the queue in plain language with every action logged.

Connect on Elaichi How to connect

  • 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 Desk365 to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Desk365 once

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

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

  3. Paste a Desk365 API key. One person generates a token in Desk365 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.

desk365
Desk365
Acquire
Ada
Atomicwork
CM Mobile Service Cloud
Crisp
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.

Desk365 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.

Desk365 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 today. The plugin directory lives at chatgpt.com/plugins.

Desk365 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.

Connect Desk365 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.

Connect Desk365 on Elaichi See pricing

Use cases

What teams do with Desk365 through Elaichi

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

  • Support

    Catch up on a ticket before replying

    Ask for the full conversation on a Desk365 ticket, get the back and forth summarized, and send the reply from the same place, with the file the customer needs attached.

  • Support

    Log a ticket while you are still on the call

    Describe the problem as the customer explains it and a Desk365 ticket is created under the right contact, with a private note for whoever picks it up next.

  • IT helpdesk

    Find every open request from one office

    Pull the open Desk365 tickets for a company, see what is stuck and what is waiting on the requester, and update priority or status in one pass.

  • Customer success

    Keep contact and company records current

    When someone changes role or a client renames itself, update the Desk365 contact or company record without opening the admin screens.

  • Finance

    Pull time entries for month-end billing

    List the Desk365 time entries logged against a client's tickets for the period, check them against the contract, and hand the totals to invoicing.

  • Operations

    Spot patterns across the week's tickets

    Ask which Desk365 tickets came in this week, group them by company or subject, and see which issues keep coming back before the next team meeting.

Try asking

  • “Summarize open Desk365 tickets raised this week”
  • “Draft a reply to ticket 4821 about billing”
  • “List contacts with more than three open tickets”

See all 44 Desk365 tools below

Compare

Elaichi vs Zapier MCP vs Composio for Desk365

All three can connect Desk365 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 Desk365, 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 Desk365 tools Allow or restrict single Desk365 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 Desk365 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

Desk365 tools for your AI agents

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

See it in Elaichi

What connecting Desk365 gets you

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

The agent

Ask about tickets, get answers back.

Plain language questions answered from live Desk365 tickets, contacts and conversations.

  • tickets
  • conversations
  • notes
  • contacts

Ask Elaichi to work across your apps.

Summarize open Desk365 tickets raised this week

Draft a reply to ticket 4821 about billing

List contacts with more than three open tickets

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Desk365.

One governed MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

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

Tool catalog

44 Desk365 tools ready without custom code.

Tickets, replies, notes, attachments and contacts, each with named resources and methods.

  • List all Desk365 ping
  • List all Desk365 tickets
  • Get single Desk365 ticket by ID
  • Create a Desk365 ticket
ElaichiTools
Tool Action Description
List all Desk365 ping List Check Desk365 API server status.
List all Desk365 tickets List List tickets in Desk365. Returns ticket_number, subject, status, priority, contact and assignment fields, and created/updated dates. Use ticket_number with the get ticket tool for details and attachments.
Get single Desk365 ticket by ID Get Get one Desk365 ticket by its ticket_number (from the list tickets tool), passed as id. Returns the ticket fields and attachments[] with file_name and attachment_url, a temporary link to the attachment file.
Create a Desk365 ticket Create Create a ticket.
Desk365 tickets create with attachment Create Create a ticket with attachment. Send the file in multipart body and the stringified `ticket_object` in query params.

Toolboxes

Every team gets its own Desk365 toolbox.

Support, escalations and reporting each work from a toolbox scoped to them.

  • Support
  • Escalations
  • Customer Success
  • IT Helpdesk
ElaichiToolboxes
Name Source template Tools Created

Support toolbox

Desk365 · tickets and replies

 Desk365 starter 18 Mar 4, 2026

Escalations toolbox

Desk365 · overdue and reopened tickets

 — 9 Mar 2, 2026

Customer Success toolbox

Desk365 · contacts and ticket history

 — 24 Feb 27, 2026

IT Helpdesk toolbox

Desk365 · internal tickets and notes

 Desk365 starter 6 Feb 19, 2026

Quality toolbox

Desk365 · ticket conversations and notes

 — 31 Jan 30, 2026

Operations toolbox

Desk365 · ticket volume reporting

 — 12 Jan 22, 2026

Shared connections

Teammates use Desk365 without seeing credentials.

Each connection shows who connected it and how many teams and members share it.

  • Support EMEA
  • Support APAC
  • Escalations
  • IT Helpdesk
ElaichiConnections
Connection Scope Status Access
DE

Desk365 (Support EMEA)

Connected by Emily Carter

 Personal • Active 1 team · 6 members
DE

Desk365 (Support APAC)

Connected by Jake Morgan

 Organization • Active 3 teams · 24 members
DE

Desk365 (Escalations)

Connected by Megan Brooks

 Organization • Active 2 teams · 11 members
DE

Desk365 (IT Helpdesk)

Connected by Tyler Reed

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

Desk365 (Customer Success)

Connected by Ryan Hayes

 Personal • Active Not shared
DE

Desk365 (Billing Queue)

Connected by Ashley Parker

 Personal • Active 2 teams · 9 members

Audit log

Answer who touched which Desk365 ticket.

Every call is logged with time, actor, action, type and resource.

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

2 minutes ago

Mar 6, 2026, 3:10 PM
E

Emily Carter

emily.carter@northwind.io

 Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM
J

Jake Morgan

jake.morgan@northwind.io

 Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM
M

Megan Brooks

megan.brooks@northwind.io

 Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM
T

Tyler Reed

tyler.reed@northwind.io

 Desk365 Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM
R

Ryan Hayes

ryan.hayes@northwind.io

 Desk365 Tickets Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM
A

Ashley Parker

ashley.parker@northwind.io

 Desk365 Tickets 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 fires, a digest ships.

Desk365 tickets are fetched, grouped, drafted by an agent, approved, then posted back.

Desk365 digest

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

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch tickets

    Desk365

    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

    Desk365

    Queued

Collections and dashboards

Desk365 ticket numbers arrive on schedule.

Four metrics, 14 days of tickets created and a team breakdown, computed without a model.

Desk365 health

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

Live

Tickets

1,284 ↓ 12%

Conversations

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

Escalations 21%

IT Helpdesk 18%

Related connectors

More from the catalog

Browse all 600+ connectors →

FAQ

Frequently asked questions

How do I connect Desk365 to Claude?

First connect Desk365 in Elaichi by pasting in a Desk365 API key from your helpdesk settings, which takes a couple of minutes. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. There is no OAuth application to register and no client ID or secret to generate, and Claude then asks you to sign in to Elaichi as yourself.

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

Yes. Once Desk365 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 Desk365 once and every client picks it up, with each person signing in as themselves.

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

An agent can list and open Desk365 tickets, read the whole conversation on one, create new tickets, send replies and add private notes, including ones with attachments. It can also look up, create and update contacts and companies, and list or log time entries against work. Because Desk365 offers many actions, short concrete asks such as "open tickets for Acme this week" get better results than long paragraphs.

Does connecting Desk365 give the AI access to every ticket in the helpdesk?

No. Every request runs inside the Desk365 access of the person who signed in, so an agent sees the tickets, contacts and companies that person could already see in Desk365. Elaichi can narrow that further, for example to reading only, but it can never widen it beyond what Desk365 itself allows.

Can my team share one Desk365 connection?

Yes. One person connects Desk365 in Elaichi and shares the connection with a team, and nobody else ever handles the Desk365 API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person who replied to a ticket or changed a company record.

Can I stop an agent from changing things in Desk365?

Yes. Restrictions in Elaichi apply per action, so you can allow reading Desk365 tickets and conversations while blocking updates, replies or new contacts. A blocked action is never shown to Claude, ChatGPT or any other client, so no prompt can reach it.

What happens to a Desk365 connection when someone leaves?

Offboarding that person in Elaichi ends their access to Desk365 through every client at once. If they set up a shared Desk365 connection, it keeps working for everyone else on the team. Disconnecting Desk365 once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.

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

Yes. Desk365 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 Desk365?

Yes. Both let Claude, ChatGPT or Cursor use Desk365. 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 Desk365 call.

How is Elaichi different from Composio for Desk365?

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 Desk365: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Desk365 in front of your team

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

Connect Desk365 Talk to us
Works with
Claude ChatGPT Cursor 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.