# AnyDesk MCP connector The AnyDesk connector brings your AnyDesk clients, remote sessions, rosters, device system information and sign-in records into Claude, ChatGPT, Cursor and other MCP clients, so support and IT staff can look up, check and tidy remote access from a plain conversation. Source: https://elaichi.ai/connectors/anydesk/ ## Facts | | | | --- | --- | | Application | AnyDesk | | Category | Remote Support | | AI tools | 10 | | Authentication | Connects with an API key | | Needs your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | Yes | ## What you can ask once AnyDesk is connected - Summarize AnyDesk sessions from the last seven days. - Which AnyDesk clients in the support roster are offline? - List sysinfo for AnyDesk clients on outdated versions. ## Connect AnyDesk in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick AnyDesk. 2. Optionally set Share with, then press Connect. 3. Paste an AnyDesk API key. One person generates a token in AnyDesk and pastes it once. Everyone else works through Share with, and never sees it. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which AnyDesk tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect AnyDesk to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 4. Sign in and approve. On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves. ## Connect AnyDesk to ChatGPT Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 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 AnyDesk to Cursor Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect AnyDesk to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a AnyDesk tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with AnyDesk through Elaichi ### Find out who is connected right now Support. Ask which AnyDesk sessions are active, who started each one and which device they are on, without opening the management console. ### Look up a device before you help IT. Pull up a colleague's AnyDesk client and its system information, such as operating system and version, so the first minute of a call is spent fixing rather than asking. ### Rename and tidy the device list IT. Fix an alias or comment on an AnyDesk client after a laptop changes hands, and remove clients for devices that have been retired. ### Review recent sign-ins for anything odd Security. List AnyDesk sign-in records and remote sessions from the last week and ask which ones happened outside working hours or from an unfamiliar device. ### Check which sites have devices online Operations. Read your AnyDesk rosters to see how the fleet is grouped by office or customer, and which clients are online or unreachable. ### Answer who accessed what and when Compliance. Get a plain list of AnyDesk sessions for a given device or period, with the notes on each session updated so the record matches what actually happened. ## Frequently asked questions ### How do I connect AnyDesk to Claude? First connect AnyDesk in Elaichi: AnyDesk connects with an API key, so you paste a key from your AnyDesk management console into Elaichi, and there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in with your Elaichi account and AnyDesk is available in Claude. ### Does AnyDesk work with ChatGPT and Cursor as well as Claude? Yes. Once AnyDesk 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 AnyDesk once and every client you use picks it up. ### What can an AI agent actually do with my AnyDesk data? With AnyDesk connected, an agent can list your AnyDesk clients and pull up a single device, read its system information, and update details such as its alias or comment, or remove a client that is no longer in use. It can list remote sessions, open one to see who connected to what and when, and update the notes on a session. It can also read your rosters and your sign-in records, so questions like who connected to this laptop last week get a direct answer. ### Does connecting AnyDesk give the AI access to my whole AnyDesk account? No. Everything an agent does in AnyDesk runs inside the access of the person who connected it, so it can only see the clients, sessions and rosters that AnyDesk account can see. Elaichi can narrow that further, for example to reading only, but it can never widen it beyond what AnyDesk itself allows. ### Can my team share one AnyDesk connection? Yes. One person connects AnyDesk in Elaichi and shares the connection with a team, and nobody else ever handles the AnyDesk API key. Each teammate still signs in to Elaichi as themselves, so the audit log records who looked up a device or changed a session note, not just that the shared AnyDesk connection was used. ### Can I stop an agent from deleting or changing things in AnyDesk? Yes. Restrictions in Elaichi apply per action, so you can allow reading AnyDesk clients and sessions while blocking updates or the removal of a client. A blocked action is never advertised to Claude, ChatGPT or any other client, so no prompt, however worded, can reach it. ### What happens to an AnyDesk connection when someone leaves? When a person is offboarded in Elaichi, their access to AnyDesk through Elaichi ends at once, in every client they were using. If AnyDesk was connected by that person and shared with a team, the connection keeps working for everyone else. If you want AnyDesk gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time. ## All 10 AnyDesk tools Every tool below is callable through https://api.elaichi.ai/mcp once AnyDesk is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all AnyDesk clients** (List). List AnyDesk clients. Returns a collection of client objects. - **Get single AnyDesk client by ID** (Get). Get a single AnyDesk client by id. Returns the full client object. Required: id. - **AnyDesk clients partial update** (Update). Partially update an existing AnyDesk client by id. Only the fields supplied in the request body are modified. Required: id. - **Delete a AnyDesk client by ID** (Delete). Delete an AnyDesk client by id. Returns an empty response on success. Required: id. - **List all AnyDesk sessions** (List). List AnyDesk sessions. Returns a collection of session objects from the AnyDesk account. - **Get single AnyDesk session by ID** (Get). Get a single AnyDesk session by id. Returns the full session object for the specified session. Required: id. - **AnyDesk sessions partial update** (Update). Partially update an AnyDesk session by id. Sends a PATCH request with the fields to modify and returns the updated session object. Required: id. - **List all AnyDesk rosters** (List). List rosters in AnyDesk. Returns a collection of roster entries. - **List all AnyDesk sysinfo** (List). Get system information from AnyDesk. Returns details about the AnyDesk system status and configuration. - **List all AnyDesk auth** (List). List authentication details for the AnyDesk integration. Returns available auth information associated with the configured account.