Skip the install. Get this working in under 2 minutes.
Start a free trial on cloud.anythingmcp.com, add the TOPdesk in one click, then point your AI client (Claude, ChatGPT, Copilot or Cursor) at the generated MCP endpoint. No Docker, no git clone, zero engineering experience required.
Summary
TOPdesk ITSM: incidents, changes, assets, operators, persons and branches, with TOPdesk's FIQL query language for precise filtering. REST API, Basic auth with an application password.
Try asking
Example prompts for TOPdesk
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → TOPdesk, paste your credentials, mint an MCP API key — done. No Docker, no
git clone, no local server.
TOPdesk + Microsoft Copilot
TOPdesk ITSM: incidents, changes, assets, operators, persons and branches, with TOPdesk's FIQL query language for precise filtering. REST API, Basic auth with an application password.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
TOPDESK_URL, TOPDESK_USERNAME, TOPDESK_APP_PASSWORD
Step 1 — Get credentials
Use an application password, never the operator's own.
- In TOPdesk open Modules → Supporting Files → Operator Management, pick the operator the integration should act as, and on its card create an Application Password. TOPdesk shows it once.
- Give that operator exactly the permission groups the agent needs — TOPdesk enforces them per module, and a missing one produces a 403 rather than an empty list, which is at least honest.
- Set
TOPDESK_URLto your instance root (e.g.https://mycompany.topdesk.net, no trailing slash),TOPDESK_USERNAMEto the operator login name andTOPDESK_APP_PASSWORDto the generated value.
…(continued in the in-app connector instructions)
Step 2 — Install the adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Add the connector in Microsoft Copilot
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.
- In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
- Enter a Server name (for example
AnythingMCP), a Server description that says what the connector does, and the Server URLhttps://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server. - Under authentication, choose API key, set Type to Header and the header name to
X-API-Key, then select Create. - In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
- Try it in the agent's Test pane: ask for something that needs the
TOPdesktools. - Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.
Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.
Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.
Available tools
| Tool | What it does |
|---|---|
topdesk_get_version | Read the TOPdesk version this instance runs |
topdesk_list_incidents | List incidents with FIQL filtering |
topdesk_get_incident | Read one incident by its TOPdesk number or UUID, with its caller, category, status, operator group, SLA target dates and request text |
topdesk_get_incident_progress | Read the progress trail of one incident: every action and memo in order, with author, timestamp and whether it is invisible to the caller |
topdesk_list_changes | List change activities with their number, requester, status, planned dates and change type |
topdesk_list_persons | List persons (the callers incidents are raised for) with their name, e-mail, branch and department |
topdesk_list_operators | List operators (the staff who work the queue) with their name, e-mail and the operator groups they belong to |
topdesk_list_branches | List branches — the sites or client organisations TOPdesk groups people and assets under — with their name, address and client reference num |
topdesk_search_assets | Search the asset management module for configuration items by name or type, returning their id, name, template and status |
topdesk_create_incident | Open a real incident in the live instance |
FAQ
Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.
What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.
The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.
Next steps
- Connector landing page
- Connect to Claude
- Connect to ChatGPT
- Connect to Cursor
- Connect to Gemini
- Connect to Meta Muse
Was this guide helpful?