AskYourStack for Cursor

From your editor to your server, in Cursor

Add AskYourStack 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 the user who owns your sites, or as root for the whole server. It shows up online within seconds.

  2. STEP 2

    Add AskYourStack to mcp.json

    In Cursor Settings, Tools & MCP, New MCP server, add (the address is the same for everyone):

    { "mcpServers": { "sudowhizzy": { "url": "https://askyourstack.com/mcp" } } }
  3. STEP 3

    Sign in and allow

    Save. In the MCP list AskYourStack shows Needs login: press it. An AskYourStack page opens, sign in if it asks and press Allow. AskYourStack then lists its 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.
Audit the structured data on these product pages and fix the template so they get rich results.

More in the prompt library, and for SEO see technical SEO with Cursor.

The tools Cursor gets

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

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.

Search Console, GA4 and SEO

Google Search Console, Analytics 4, Core Web Vitals, page audits and your access logs, read-only, next to the server.

Server access, with you holding the keys

A change window you open

Nothing changes on a server until you open changes on it, for 1 to 8 hours, never for good. Outside that window Cursor can look, diagnose and plan, and is told to ask you.

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 askyourstack.com, so text planted in a log or web page cannot approve anything.

An open-source agent you can verify

The only thing on your server is public code (github.com/shopwhizzy/askyourstack-agent). Every release names its source commit, so you can rebuild it and compare the hash. It runs as an ordinary Linux user unless you choose root, and one command on the server locks it to reads.

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 windows, approvals and modes work · Check every claim yourself

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 AskYourStack and Cursor

Do I need to put SSH keys in my project?

No. Cursor talks to AskYourStack over HTTPS, signed in to your account, 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 askyourstack.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 AskYourStack with Claude?

Yes. The tools, playbooks and safety rules are the same for every client, and the same sign-in 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