SudoWhizzy for Cursor

From your editor to your server, in Cursor

Add SudoWhizzy to Cursor as a remote MCP server and Cursor's agent can work on the servers your code runs on: deploy a module, read the logs when it breaks, tune PHP-FPM or set up a fresh box, without an SSH key in your project.

Free plan: one server, read-only. No card needed.

Connect Cursor to your server in four steps

  1. STEP 1

    Connect your server

    Sign up free, name your server in the dashboard and paste the one-line install as root. It shows up online within seconds.

  2. STEP 2

    Add SudoWhizzy to mcp.json

    Copy your MCP address from the dashboard and add it to Cursor's mcp.json:

    { "mcpServers": { "sudowhizzy": { "url": "https://sudowhizzy.com/mcp/YOUR-ADDRESS" } } }
  3. STEP 3

    Switch it on

    In Cursor's MCP settings, check that sudowhizzy is enabled and lists its tools. After a plan change, turn it off and on again to load the new tools.

  4. STEP 4

    Ask

    In the agent chat, try: Deploy this module to the shop on my server and check it works.

What you can ask Cursor

Describe the outcome in plain words. Cursor looks at the server first, explains its plan, and asks you before anything risky.

Deploy this Magento module to the shop, run setup:upgrade and check the storefront.
The checkout throws an exception on the server. Read the logs and find the cause in this code.
Write a WordPress plugin for this and install it on the staging site.
Compare PHP and extension versions on the server with what this project needs.
Set up a staging copy of the shop on my second server.

More in the prompt library.

The tools Cursor gets

Built for running Linux servers and PHP shops, with built-in playbooks for fresh servers, Magento, WordPress, hardening, backups, check-ups, malware cleanup and migrations.

Commands and files

run, read_file and write_file on any of your servers, with every overwritten file kept.

Long jobs

start_job runs installs, compiles and imports in the background; job_output follows them.

Magento and WordPress

list_sites, magento and wp run bin/magento and wp-cli as the site's owner.

Databases

db_query and db_dump use the site's own credentials, so the password never reaches the chat.

Snapshots and rollback

snapshot before risky work, rollback to undo it, and the rollback can be undone too.

Malware scan

Looks for backdoors, skimmers in the database, disguised PHP and suspicious cron entries.

Health

health_report covers disk, memory, failed services, certificates, updates and Magento cron.

Server moves

transfer copies a site straight from one of your servers to another, never through the chat.

Root access, with you holding the keys

Approvals only you can give

Deleting data, dropping databases, touching SSH or the firewall: Cursor gets a link and waits. Approving needs you signed in on sudowhizzy.com, so text planted in a log or web page cannot approve anything.

Three modes per server

Read-only for looking around, normal for daily work, full trust when you are watching.

Every action logged

Each command, file write and result, with its risk level, in your activity log. Pause one server or all of them in one click.

How approvals and modes work

Tested on real servers

From our own test runs with Claude Code on fresh Rocky Linux 10 servers.

30 min

raw Rocky Linux 10 box to a live Mage-OS shop with OpenSearch, Valkey, cron and Let's Encrypt

56 s

maintenance window when a live shop was moved to a second server (21 minutes in all)

5 of 5

planted attacks found by the malware scan in a 40,000-file shop, with no false positives

Questions about SudoWhizzy and Cursor

Do I need to put SSH keys in my project?

No. Cursor talks to SudoWhizzy over HTTPS with your private MCP address, and the agent on your server does the work. Nothing about the server's access lives in your repository.

Can the agent run destructive commands?

Only with your approval. Deleting folders, dropping databases, removing packages, changing SSH or the firewall: the tool answers with a link, and the command runs once you approve it signed in on sudowhizzy.com.

Does it work with Magento and WordPress tooling?

Yes. The magento and wp tools run bin/magento and wp-cli as the site's owner, and db_query reads the database with the site's own credentials, so the password never reaches the chat.

Is it the same as using SudoWhizzy with Claude?

Yes. The tools, playbooks and safety rules are the same for every client, and one MCP address works in all of them.

Also works with Claude, Claude Code and ChatGPT, and any client that supports remote MCP servers.

Connect Cursor to your first server

Start free with one server in read-only mode. Upgrade when you want Cursor to fix things.

Get started