Solisk PC Control MCP
Exposes the local MCP server through a Cloudflare tunnel, either as a quick tunnel or via a custom domain, enabling remote MCP clients to reach the PC over HTTPS.
Publishes the MCP server and web dashboard over a tailnet using Tailscale serve, allowing private remote access from devices on the same tailnet.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Install · Windows GUI · Connect an AI · Security · Self-host · CLI · FAQ
Let your AI work with files and apps on your PC
Solisk connects MCP-compatible AI clients to your machine. Read a project file, inspect a Git diff, or use Windows desktop tools without building a separate integration for each app. Start locally; use the hosted relay or run your own relay when the client needs a remote URL.
Local or self-hosted: the runtime and relay are MIT-licensed and included here.
A Windows control room: manage connections and approve supported shell commands locally.
CLI on Windows, Linux and macOS: capabilities differ by platform; see OS support.
PC access is powerful. Use a test folder first and read the trust boundaries before granting shell or desktop access. Approval is not a universal gate for every tool.
See the first win
Run a complete local workflow before connecting a real project or remote relay:
node examples/first-win.jsThe demo uses synthetic data and real MCP stdio calls to read a CSV, write and verify a Markdown report, then prove a path outside the allowed folder is denied. No account, model API key, relay or network is required. See LAUNCH.md for the recording script, interactive product film and launch copy.
Open the interactive product film at assets/launch/solisk-brand-film.html
for the visual overview, then run the technical demo to verify the local MCP path.
Related MCP server: Windows Computer Bridge MCP
Install
npm install -g solisk # requires Node 22.5+
solisk setup # configure identity and approval modeThen choose one connection path below. For Windows users who prefer an installer, skip npm and use the Windows GUI.
Local client on the same machine
For an MCP client that accepts command-based servers, add this entry to its MCP configuration. The client starts and stops Solisk; don't also start an HTTP server for this connection.
{
"mcpServers": {
"solisk": {
"command": "solisk",
"args": ["--mode=stdio"]
}
}
}If the client cannot find solisk, restart it after installation or configure the
absolute path to the installed command. Stdio uses the permissions of the local
process, not a bearer-key login. It does not open the web dashboard or a relay.
Hosted or HTTP clients
Start the server and leave this terminal running:
solisk --mode=httpIn a second terminal, open the control room:
solisk dashboardUse the MCP URL shown by the running instance for remote clients. For local HTTP,
the default endpoint is http://127.0.0.1:3000/mcp and requires authentication.
Use solisk --mode=http --no-relay to disable the hosted relay for that run;
also leave Cloudflare and Tailscale exposure off for a local-only setup.
Windows GUI
Open the latest release and download its
PC Control MCP Setup … .exeasset andSHA256SUMS.txt. An MSI is not included in every release.Run it: point-and-click control room, same engine as the CLI.
Already have the CLI?
solisk gui setup --installer "<path-to-downloaded-installer.exe>"installs it silently.On Linux/macOS,
solisk guirefuses by design and points you to the web dashboard.
The Windows installer is unsigned and may trigger SmartScreen. Download only from the official release and compare its SHA-256 hash withSHA256SUMS.txt before deciding whether to run it. A checksum is not a publisher signature. Older release assets may still carry a 1.0.0 filename; consult the release notes rather than guessing a download URL.
Connect an AI
For a remote connector, use your instance's URL and complete the client's authorization flow. Keep the room key out of chat messages and screenshots. Available connector features depend on the client and account.
flowchart LR
A[Copy MCP URL<br/>from your running instance] --> B[Add a remote MCP connector]
B --> C[Approve once<br/>consent + room key]
C --> D[Verify tools are listed<br/>then try a read-only task]
style D fill:#4fd1b5,color:#03211bConnect | Authorize | Control |
If discovery fails, first check that the runtime and selected connection path are online. If a client cached an earlier failed connection, removing and re-adding the connector may help; it is not a substitute for checking the server error.
Your first successful task
Choose a non-sensitive text file in a folder you have allowed, then ask:
Use Solisk's
read_filetool to read the file at the absolute path I provide and summarize it in three bullets. Do not run shell commands or change files.
Success means the client lists Solisk's tools, read_file returns that file's
contents, and the summary matches. If access is denied, correct the allowed path
or key scope rather than switching to Turbo. Next, try inspecting a Git diff
in a test repository. Desktop automation can wait until this basic flow works.
Security model
# | Control | Boundary |
1 | HTTP authentication | Owner/scoped keys and OAuth authenticate HTTP clients; remembered device cookies also authorize web-console access. Stdio trusts the process launching it. |
2 | Authenticated relay | TLS terminates at the relay, which can see forwarded requests and results. There is no client-to-PC end-to-end encryption. |
3 | Relay OAuth | PKCE S256, redirect checks and resource-bound tokens protect the relay authorization flow. |
4 | Credential storage | Relay API keys are scrypt-hashed. Local config keys and local OAuth tokens are stored in plaintext files; protect the profile and backups. |
5 | Tool permissions | Use scoped keys and file-path rules, but do not treat them as an OS sandbox around shell commands or desktop automation. |
6 | Approval and audit | Approval behavior depends on the tool and runtime. Tool audit records include arguments, which may contain sensitive data. |
Full policy: SECURITY.md · found something? Security advisory — not a public issue.
Everything, live
Four paths in | Hosted relay · Cloudflare tunnel (quick or your own domain) · tailnet · web dashboard. Each toggles live; killing the dashboard returns |
Honest sessions | One live AI reads |
Keys that fit | Scoped client keys, fail-closed defaults, zero-downtime rotation, 30-day remembered devices. |
No-fight runtime | CLI attaches to a running GUI, borrows its key transparently, and refuses to boot a second server over it. |
Updates | In-app release notes, skip-a-version supported, mandatory releases cannot be skipped. |
Architecture
flowchart TB
AI["AI client<br/>Claude.ai / ChatGPT / Cursor"]
AI -->|MCP URL + OAuth 2.1<br/>PKCE S256, resource-bound tokens| RELAY
subgraph RELAY["Cloud relay"]
R1[rooms · tokens · rate limits<br/>scrypt-hashed keys]
end
RELAY -->|one outbound WebSocket per PC<br/>takeover-protected| PC
subgraph PC["Your machine :3000"]
P1[StreamableHTTP · 97 tools · 5 sessions max]
P2[Cloudflare tunnel<br/>quick or your domain]
P3[tailnet serve · web dashboard /app]
endOne config file, one event bus, one session store. Thin faces (Electron, CLI, web shim) never own state.
OS support
OS | CLI ( | Web dashboard ( | GUI | Tools |
Windows 10/11 x64 | ✅ local + relay + tunnel | ✅ | ✅ full control room | 97 native |
Linux | ✅ server · stdio · tunnels · Tailscale | ✅ | ❌ — | Portable tools + |
macOS | ✅ server · stdio | ✅ | ❌ — same | Portable tools + |
Windows-only implementations stay off elsewhere. macOS includes native screenshot
and input tools that need Screen Recording and Accessibility permissions. Run
solisk --list-tools for the actual inventory on your machine. Platform support
does not imply identical tool behavior or security coverage.
Requirements
Node ≥ 22.5 for the CLI.
Windows 10/11 x64 for the GUI.
Nothing else — no Docker, no reverse proxy needed for localhost use.
Self-host the relay
ssh root@YOUR_VPS
bash -c "$(curl -fsSL https://raw.githubusercontent.com/Kyzenkms/solisk-pc-mcp/main/self-hosted-setup/vps/install.sh)"Picks your domain type (yours or sslip.io for testing), then runtime (Docker or PM2), then prints the room + key to paste into the app. Backups, firewall, updates: self-hosted-setup/README.md.
CLI reference
solisk is the command — pc-control remains as a compatibility alias.
solisk dashboard [--no-open] web console for the running server
solisk doctor [--fix] 11 health checks — 0 failing is the goal
solisk logs [--lines N] live server log, whichever face owns it
solisk setup step-by-step onboarding wizard
solisk backup config snapshot for restoressolisk config get|set|validate ports, modes, domains (secrets refused)
solisk rotate-key new owner key, zero-downtime rotation
solisk keys list|add|revoke scoped client keys (fail-closed defaults)
solisk devices list|revoke remembered browsers
solisk relay status|retry room state, redialsolisk tunnel off|quick|custom + login, create, route, forget, status
solisk tailscale status|serve|off funnel is deliberate and confirmed
solisk gui status|setup detect install, install from .exe or .msiEvery attach command works with zero flags next to a running GUI.
Verify
npm ci
npm ci --prefix relay-server
npm test # isolated config; unit, HTTP, stdio and relay checks
npm run test:stdio # registry launch arguments + actual MCP file read
npm run test:package # extracted npm tarball: dashboard + API authRun these from the repository root. CI runs the full suite on Windows and stdio
smoke tests on Linux/macOS; release builds depend on those jobs. npm run test:live
targets a running server rather than an isolated fixture; use it only deliberately.
For an installed runtime, use solisk doctor to inspect local setup.
The packaging test needs tar on PATH and reuses the checkout's installed
dependencies; it does not replace a fresh-machine install test.
FAQ
MIT · Solisk PC Control MCP · Releases · solisk.org
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Give your AI hands on every computer you own. Remote control of your Windows, Mac and Linux machines from one ChatGPT, Claude or Cursor chat — even from your phone. Ask it to find out why the office server is crawling, update every PC in the house, sort out your mom's laptop from another city, or ship the site from your work machine while you're on a train. It runs commands, reads files and takes a screenshot when it needs to see the screen. You decide what each computer allows, and you can cut any of them off in a second.
- DNS-DATA RemoteDeprecatedcom.dns-data
Connect AI assistants to authorized Windows and macOS devices for files, commands, and management.
Secure AI access to Windows, macOS, Linux computers and a hosted Cloud Browser.
Connect AI assistants to your approved computer for files, commands, browser and desktop tasks.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to drive Windows desktop automation — opening and interacting with applications, native UI controls, keyboard/mouse input, files, processes, clipboard, and Chrome/Edge browsing via UI Automation and CDP. All actions pass through a safety policy with human approval, emergency stop, and deterministic verification.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to inspect and control allowlisted Windows applications using screenshots, mouse actions, Unicode keyboard input, UI Automation, and an Esc/F12 emergency stop.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables an AI agent to inspect and operate a remote Windows machine over a private tailnet, listing and reading files, transferring and mutating them within a configured sandbox root, capturing screenshots, and — only when explicitly double-opted-in — executing commands and sending keystrokes. It runs self-hosted with no third-party client or vendor cloud in the session path, and reports its live policy rather than asserting its own safety.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to operate Windows desktops through native UIA control, OCR text targeting, screenshots, and 54 tools for window, process, input, clipboard, file, registry, and document tasks with pause, observe-only, and privacy safeguards.MIT