AnyDesk MCP connector

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.

Yes. Once AnyDesk is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect AnyDesk once and every client you use picks it up.

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.

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.

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.

Yes. Restrictions in Elaichi apply per action, so you can allow reading AnyDesk clients and sessions while restricting updates or the removal of a client. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.

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, Microsoft Copilot and every other client at the same time.

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, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

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.

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.