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.
10 tools
How to connect
How to connect AnyDesk to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect AnyDesk once
-
Open Connections, choose Add connection, and pick AnyDesk.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
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.
AnyDesk MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
AnyDesk MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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.
AnyDesk MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.”
Compare
Elaichi vs Zapier MCP vs Composio for AnyDesk
All three can connect AnyDesk to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| 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 AnyDesk tools | Allow or restrict single AnyDesk 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 AnyDesk 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
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.
No tools match your search.
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 clientsClaude
ChatGPT
Cursor
Copy the endpoint
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
ElaichiToolsToolboxes
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
ElaichiToolboxesShared 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
ElaichiConnectionsAudit 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 logLaunching 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 Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch clients
AnyDesk
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
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
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%
Related connectors
More from the catalog
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 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.
Does the AnyDesk MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. AnyDesk 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 AnyDesk?
Yes. Both let Claude, ChatGPT or Cursor use AnyDesk. 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 AnyDesk call.
How is Elaichi different from Composio for AnyDesk?
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 AnyDesk: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put AnyDesk in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
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.