Solisk Pc Mcp

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.js

The 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.

Install

npm install -g solisk      # requires Node 22.5+solisk setup              # configure identity and approval mode

Then 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=http

In a second terminal, open the control room:

solisk dashboard

Use 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

1. Open the latest release and download its PC Control MCP Setup … .exe asset and SHA256SUMS.txt. An MSI is not included in every release.
2. Run it: point-and-click control room, same engine as the CLI.
3. Already have the CLI? solisk gui setup --installer "<path-to-downloaded-installer.exe>" installs it silently.
4. On Linux/macOS, solisk gui refuses by design and points you to the web dashboard.

[!WARNING] The Windows installer is unsigned and may trigger SmartScreen. Download only from the official release and compare its SHA-256 hash with SHA256SUMS.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:#03211b

[!NOTE] 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_file tool 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

Full policy: SECURITY.md · found something? Security advisory — not a public issue.

Everything, live

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]    end

One config file, one event bus, one session store. Thin faces (Electron, CLI, web shim) never own state.

OS support

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_VPSbash -c "$(curl -fsSL https://raw.githubusercontent.com/Kyzenkms/solisk-pc-mcp/main/self-hosted-setup/vps/install.sh)"

CLI reference

solisk is the command — pc-control remains as a compatibility alias.

solisk dashboard [--no-open]      web console for the running serversolisk doctor [--fix]             11 health checks — 0 failing is the goalsolisk logs [--lines N]           live server log, whichever face owns itsolisk setup                      step-by-step onboarding wizardsolisk backup                     config snapshot for restores

solisk config get|set|validate    ports, modes, domains (secrets refused)solisk rotate-key                 new owner key, zero-downtime rotationsolisk keys list|add|revoke       scoped client keys (fail-closed defaults)solisk devices list|revoke        remembered browserssolisk relay status|retry         room state, redial

solisk tunnel off|quick|custom    + login, create, route, forget, statussolisk tailscale status|serve|off funnel is deliberate and confirmedsolisk gui status|setup           detect install, install from .exe or .msi

Verify

npm cinpm ci --prefix relay-servernpm test                         # isolated config; unit, HTTP, stdio and relay checksnpm run test:stdio               # registry launch arguments + actual MCP file readnpm run test:package             # extracted npm tarball: dashboard + API auth

Run 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