TOPdesk MCP: connect TOPdesk to Claude and ChatGPT
Ask Claude or ChatGPT which incidents for a location are still open, what has changed on the network this month or which knowledge item answers a question you get every week. The answer comes straight from TOPdesk, without building a selection first.
We build the connector for your company on TOPdesk’s own API. It signs in as a TOPdesk operator with an application password, so TOPdesk applies that operator’s permissions, and it only reads.
Built for your company · Works in Claude, ChatGPT and Copilot
What your team can do with TOPdesk in Claude and ChatGPT
The queue in one answer
Patterns before the weekly meeting
What is changing and when
Rooms, assets and reports
Ask it like this
“Which incidents for the Utrecht office are still open, and who is working on them?”
“Summarise all incidents about the VPN from the last two weeks.”
“Which changes are planned for next week, and which are still waiting for approval?”
“Is there a knowledge item on resetting the badge reader at Kantoor Gent?”
“Which laptops are registered to Sanne de Vries?”
“Which categories produced the most incidents in October compared with September?”
What we build for TOPdesk
Deployed OS has no ready TOPdesk connector yet. We build it for your company when you start, on TOPdesk’s own API, with the same rules as every other connector: each person’s own login, access decided by group, every call logged.
- Incidents
- Incidents with their caller, operator group, category, status and actions, filtered the way you ask.
- Changes
- Changes with their status and planning, so the AI can say what is going live and what is waiting.
- Assets
- Assets from asset management, and who or which location they are linked to.
- Knowledge base
- Knowledge items and their status, so the answer to a known question can be found in one go.
- Operators and persons
- Operators, operator groups and callers, so the AI can tell you who is working on what.
Who sees what
- Read-only
- The connector reads. It does not register incidents, change a card or close anything. Writing, such as adding an action to an incident, we only build if you ask for it.
- Signed in as a TOPdesk operator
- TOPdesk’s API takes an application password, which only operators can create, and the operator’s permission group must allow API access. TOPdesk then applies that operator’s permissions, so each operator can connect with their own, or you use one operator account set up for the connector.
- Your company decides who gets it
- Admins choose which groups get TOPdesk in Deployed OS, for example the service desk only. A group without access never sees the connector.
- Every call logged
- Who asked, what was read and when. Deployed OS keeps the log, and it can be exported.
Set up the TOPdesk connector in three steps
TOPdesk MCP: common questions
Not as far as we know. There are community MCP servers for TOPdesk and some hosted third-party ones. We build the MCP connector on TOPdesk’s own documented API, so the answers can be used in Claude and ChatGPT next to your other systems.
No. The connector reads incidents, changes, assets and knowledge items. It does not register or update cards, and we only build writing if you ask for it.
No. Every call runs with an operator’s application password, and TOPdesk applies that operator’s permissions. If you use one operator account for the connector, give it only the permissions you want the AI to have.
TOPdesk only gives application passwords to operators. Staff who are not operators can still ask through Deployed OS if you give their group access, and the answers then come through the operator account set up for the connector.
Deployed is an EU company and fully GDPR compliant, and you choose where your data is stored, down to the city. TOPdesk data is fetched when someone asks for it.
It depends on the size of your team. Get in touch and we will walk you through it.
See it on your own tools.
Tell us which systems your company runs on. We’ll show you what your team can ask, and what IT gets to control.