Skip to content

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.

1

In Elaichi

Connect TOPdesk once

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

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

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

topdesk
TOPdesk
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.

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

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

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

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?”

See all 441 TOPdesk tools below

Compare

Elaichi vs Zapier MCP vs Composio for TOPdesk

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

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.

Showing 275 of 441 TOPdesk tools here. Connect TOPdesk and call search_tools or tools/list over the MCP endpoint for the complete set.

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.

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

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
ElaichiTools
Tool Action Description
List all TOPdesk incidents List List TOPdesk incidents with optional FIQL filtering, field selection, and sorting. Returns: id, number, request, action, briefDescription, caller, operator, operatorGroup, callType, category, subcategory, object, location, callDate, creationDate, modificationDate, targetDate, closedDate, escalationStatus, externalLinks, attachments, partialIncidents, responded, responseDate, sla, departmentId,…
Create a TOPdesk incident Create Create a new incident in TOPdesk. Returns the created incident including id, number, briefDescription, caller, operator, and operatorGroup. Persons can only set request, briefDescription, callType, category, subcategory, object, location, and operatorGroup.
TOPdesk incidents deescalate Action Deescalate a TOPdesk incident by id. Returns the updated incident including id, number, briefDescription, caller, operator, and escalationStatus. Required: incident_id.
TOPdesk incidents archive Archive Archive a TOPdesk incident by id. If the incident has partial incidents they will also be archived. Returns the updated incident including id, number, briefDescription, caller, operator, and escalationStatus. Required: incident_id.
TOPdesk incidents escalate Action Escalate a TOPdesk incident by id. Returns the updated incident including id, number, briefDescription, caller, operator, and escalationStatus. Required: incident_id.

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
ElaichiToolboxes
Name Source template Tools Created

Service desk toolbox

TOPdesk · incidents and callers

TOPdesk starter 18 Mar 4, 2026

Change management toolbox

TOPdesk · escalations and approvals

— 9 Mar 2, 2026

Field support toolbox

TOPdesk · on site incidents and assets

— 24 Feb 27, 2026

Operations reporting toolbox

TOPdesk · incident volumes and archives

TOPdesk starter 6 Feb 19, 2026

IT security toolbox

TOPdesk · escalated incidents and access requests

— 31 Jan 30, 2026

HR services toolbox

TOPdesk · onboarding and offboarding tickets

— 12 Jan 22, 2026

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
ElaichiConnections
Connection Scope Status Access
TO

TOPdesk (Service desk EMEA)

Connected by Emily Carter

Personal • Active 1 team · 6 members
TO

TOPdesk (Field support)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
TO

TOPdesk (Change board)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
TO

TOPdesk (Security operations)

Connected by Tyler Reed

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

TOPdesk (HR services)

Connected by Ryan Hayes

Personal • Active Not shared
TO

TOPdesk (Reporting)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every TOPdesk call is written down.

When, who, what happened, type and resource for each incident touched.

  • 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

TOPdesk Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

TOPdesk Incidents Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

TOPdesk Incidents 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, 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 Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch incidents

    TOPdesk

    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

    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

Live

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%

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 my team share one TOPdesk connection?

Yes. One person connects TOPdesk in Elaichi and shares the connection with a team, and nobody else ever handles the TOPdesk API key. Each teammate still signs in to Elaichi as themselves, so every incident created or updated is logged under the name of the person who asked for it, not the person who connected TOPdesk.

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.

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

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

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

How is Elaichi different from Composio for TOPdesk?

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

Put TOPdesk in front of your team

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

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.