Skip to content

Remote Support

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.

  • 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 AnyDesk to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect AnyDesk once

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

  2. Optionally set Share with to give a team access, 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.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

anydesk
AnyDesk
1Password
360learning
7shifts
Acquire
Ada
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.

Connect AnyDesk to 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.

Connect AnyDesk to 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.

Connect AnyDesk to 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 AnyDesk 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 AnyDesk through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Support

    Find out who is connected right now

    Ask which AnyDesk sessions are active, who started each one and which device they are on, without opening the management console.

  • IT

    Look up a device before you help

    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.

  • IT

    Rename and tidy the device list

    Fix an alias or comment on an AnyDesk client after a laptop changes hands, and remove clients for devices that have been retired.

  • Security

    Review recent sign-ins for anything odd

    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.

  • Operations

    Check which sites have devices online

    Read your AnyDesk rosters to see how the fleet is grouped by office or customer, and which clients are online or unreachable.

  • Compliance

    Answer who accessed what and when

    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.

Try asking

  • “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.”

See all 10 AnyDesk tools below

AI tools

AnyDesk tools for your AI agents

10 tools are ready to call through Elaichi's MCP endpoint the moment you connect AnyDesk, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting AnyDesk gets you

6 screens from the product, each doing one job for your AnyDesk account.

The agent

Ask about AnyDesk sessions, get real answers.

Plain language questions answered from live AnyDesk clients, sessions and sysinfo records.

  • clients
  • sessions
  • rosters
  • sysinfo

Ask Elaichi to work across your apps.

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.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach AnyDesk here.

One governed MCP endpoint for AnyDesk over OAuth, no SDK, 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

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

10 AnyDesk tools ready with no custom code.

Clients, sessions, rosters, sysinfo and auth records with their methods already mapped.

  • List all AnyDesk clients
  • Get single AnyDesk client by ID
  • AnyDesk clients partial update
  • Delete a AnyDesk client by ID
ElaichiTools
Tool Action Description
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.

Toolboxes

Every team gets its own AnyDesk toolbox.

Scope support, IT and security to the AnyDesk toolboxes each one needs.

  • Support
  • IT operations
  • Field service
  • Security
ElaichiToolboxes
Name Source template Tools Created

Support toolbox

AnyDesk · sessions and clients

AnyDesk starter 18 Mar 4, 2026

IT operations toolbox

AnyDesk · rosters and sysinfo

9 Mar 2, 2026

Field service toolbox

AnyDesk · on site client sessions

24 Feb 27, 2026

Security toolbox

AnyDesk · auth records and access

AnyDesk starter 6 Feb 19, 2026

Onboarding toolbox

AnyDesk · new client provisioning

31 Jan 30, 2026

Service management toolbox

AnyDesk · session reporting and SLAs

12 Jan 22, 2026

Shared connections

Share AnyDesk access, never the credential.

See who connected each AnyDesk account and how many teams and members use it.

  • Support EMEA
  • Support APAC
  • IT operations
  • Field service
ElaichiConnections
Connection Scope Status Access
AN

AnyDesk (Support EMEA)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
AN

AnyDesk (Support APAC)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
AN

AnyDesk (IT operations)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
AN

AnyDesk (Field service)

Connected by Daniel Ortega

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

AnyDesk (Security review)

Connected by Clara Nowak

Personal • Active Not shared
AN

AnyDesk (Onboarding)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every AnyDesk call is on the record.

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

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

AnyDesk Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

AnyDesk Clients Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

AnyDesk Clients 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, AnyDesk work gets done.

Fetch sessions, group them, draft a digest, approve it, post back to AnyDesk.

AnyDesk digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch clients

    AnyDesk

    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

    AnyDesk

    Queued

Collections and dashboards

AnyDesk health counted, not asked for.

Four metrics, 14 days of sessions created and a team breakdown, refreshed on schedule.

AnyDesk health

Refreshed 4 minutes ago · every 15 minutes · from the clients collection

Live

Clients

1,284 ↓ 12%

Sessions

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Clients created

Last 14 days

By team

Share of activity

Support EMEA 34%

Support APAC 27%

IT operations 21%

Field service 18%

FAQ

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.

Put AnyDesk in front of your team

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