ZionDesk

app.ziondeskPublished by ziondesk.appOfficial publisherv1.0.0Updated Oct 29, 2026

Connect ChatGPT, Claude, Cursor or VS Code to your Windows PC: files, terminal, browser, apps.

VerifiedStreamable HTTPWeb executableBrowser AutomationDeveloper Tools

Overview

AI-generated overview

ZionDesk is a remote MCP endpoint that connects AI assistants such as ChatGPT, Claude, Cursor or VS Code to a Windows PC for files, terminal, browser and apps.

What you can do
  • Access files on the connected Windows PC
  • Run commands through the PC's terminal
  • Control the browser on that machine
  • Interact with installed applications
  • No tool list is published, so exact capabilities are only described at a high level.
When to use it
When you want an assistant to work directly on your own Windows machine rather than in a sandbox: reading or changing local files, running commands, or driving the browser and desktop apps from a chat client.
Requirements
A remote MCP endpoint at mcp.ziondesk.app over streamable HTTP, with OAuth sign-in required. A Windows PC running the ZionDesk side that the endpoint connects to. No environment variables or headers are declared.
Before you install
The server is described as giving an assistant access to your PC's files, terminal, browser and apps, so it can read, change or delete local data and run commands on your machine. Access is granted through OAuth; review which account and permissions you authorize and limit what the connected PC exposes.

Installation

In SourceWeft

  1. Open ZionDesk in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.ziondesk%2Fziondesk/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "ziondesk": {
      "type": "http",
      "url": "https://mcp.ziondesk.app/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.