Helpdesk
TOPdesk MCP connector
The TOPdesk connector brings incidents and their attachments into Claude, ChatGPT, Cursor, and any other MCP client, so your service desk can log, update, escalate, and archive TOPdesk incidents in plain language, inside each person's own TOPdesk 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.
How to connect
How to connect TOPdesk to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect TOPdesk once
-
Open Connections, choose Add connection, and pick TOPdesk.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a TOPdesk API key. One person generates a token in TOPdesk 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 TOPdesk 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 TOPdesk 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 TOPdesk 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 TOPdesk 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 TOPdesk through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
IT service desk
Log an incident from a chat message
A colleague describes a broken laptop in a message and the agent creates the TOPdesk incident with the right caller, category, and description, so nothing waits for someone to open a form.
-
IT service desk
Catch an incident up after a call
After a phone call with the caller, update the TOPdesk incident with what was tried, change its status, and attach the screenshot they sent, in one ask.
-
Facilities
Escalate stalled requests to the right level
Ask which facilities incidents have been open longest and escalate the ones that are overdue, or de-escalate a ticket that turned out to be minor.
-
Support
Find every incident about the same problem
When a printer, building, or application keeps coming up, list the open TOPdesk incidents that mention it and get a summary of what callers are reporting.
-
HR
Handle onboarding requests without leaving the conversation
Create the TOPdesk incident for a new starter's access request, check on it later by number, and pull down the signed form attached to it when payroll asks.
-
Operations
Clean up the incident backlog
Archive TOPdesk incidents that have been resolved for months, unarchive one when a caller reopens the case, and remove attachments that should no longer be kept on a ticket.
Try asking
- “Show open TOPdesk incidents escalated this week.”
- “Create a TOPdesk incident for the printer outage.”
- “Which TOPdesk incidents were archived yesterday, and by whom?”
AI tools
TOPdesk tools for your AI agents
441 tools are ready to call through Elaichi's MCP endpoint the moment you connect TOPdesk, 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 TOPdesk gets you
6 screens from the product, each doing one job for your TOPdesk account.
The agent
Ask about incidents, read answers from TOPdesk.
Plain questions return live incidents, operators and changes straight from TOPdesk records.
- incidents
- incident numbers
- escalations
- archives
Ask Elaichi to work across your apps.
Show open TOPdesk incidents escalated this week.
Create a TOPdesk incident for the printer outage.
Which TOPdesk incidents were archived yesterday, and by whom?
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach TOPdesk here.
One org MCP endpoint over OAuth, no SDK work and no shared API key.
Copy the endpoint
Tool catalog
441 TOPdesk tools are ready to call.
Incidents, incident numbers, escalations and archives are covered without writing custom code.
- List all TOPdesk incidents
- Create a TOPdesk incident
- TOPdesk incidents deescalate
- TOPdesk incidents archive
Toolboxes
Every team gets its own TOPdesk toolbox.
Service desk, change and reporting teams each see a toolbox scoped to them.
- Service desk
- Change management
- Field support
- Operations reporting
Shared connections
Share a TOPdesk account, never the password.
Connections table shows who connected each account and which teams and members use it.
- Service desk EMEA
- Field support
- Change board
- Security operations
Audit log
Every TOPdesk call is written down.
When, who, what happened, type and resource for each incident touched.
- 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, TOPdesk incidents get handled.
Six steps fetch and group incidents, draft a digest, wait for approval, post back.
TOPdesk digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch incidents
TOPdesk
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
TOPdesk
Queued
Collections and dashboards
TOPdesk incident numbers, computed on a schedule.
Four metrics, fourteen days of incidents created and a breakdown by team, no model involved.
TOPdesk health
Refreshed 4 minutes ago · every 15 minutes · from the incidents collection
Incidents
1,284 ↓ 12%
Incident numbers
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Incidents created
Last 14 days
By team
Share of activity
Service desk EMEA 34%
Field support 27%
Change board 21%
Security operations 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect TOPdesk to Claude?
First connect TOPdesk in Elaichi, which asks for a TOPdesk API key, the application password you create for your own TOPdesk operator account. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and TOPdesk incidents are available in your next conversation.
Does TOPdesk work with ChatGPT and Cursor as well as Claude?
Yes. TOPdesk is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is added to Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. Each person signs in as themselves in whichever client they use, and the same restrictions and audit log apply everywhere.
What can an AI agent actually do with my TOPdesk data?
An agent can list your TOPdesk incidents, open one by its ID or incident number, create a new incident, and update an existing one with notes, status, or a new category. It can escalate or de-escalate an incident, archive and unarchive it, and add, download, or remove attachments such as screenshots and forms. Because TOPdesk exposes hundreds of actions, short concrete asks like "escalate incident I-2403-118" work better than long paragraphs.
Does connecting TOPdesk give the AI access to every incident?
No. Every request runs inside the TOPdesk access of the person who signed in, so an agent sees only the incidents, operator groups, and attachments that person can already open in TOPdesk. Elaichi can narrow that further, for example to reading incidents only, but it can never grant more than TOPdesk itself allows that person.
Can I stop an agent from deleting or changing things in TOPdesk?
Yes. Restrictions in Elaichi work per action, so you can allow reading and creating TOPdesk incidents while blocking updates, archiving, or deleting attachments. A blocked action is never advertised to Claude, ChatGPT, Cursor, or any other client, so no prompt, however worded, can reach it.
What happens to a TOPdesk connection when someone leaves?
Offboarding a person in Elaichi ends their access to TOPdesk through every client at once, with no clean-up needed in Claude, ChatGPT, or Cursor. If they had shared a TOPdesk connection with a team, that connection keeps working for everyone else. Disconnecting TOPdesk once in Elaichi removes it from every client for the whole organization.
Put TOPdesk in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.