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.
-
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.
In Elaichi
Connect Desk365 once
-
Open Connections, choose Add connection, and pick Desk365.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
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.
Connect Desk365 to 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.
Connect Desk365 to 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.
Connect Desk365 to 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 Desk365 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 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”
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.
No tools match your search.
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.
Copy the endpoint
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
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
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
Audit log
Answer who touched which Desk365 ticket.
Every call is logged with time, actor, action, type and resource.
- When
- Who
- What happened
- Type
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 Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch tickets
Desk365
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
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
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
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 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.
Put Desk365 in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.