Work on your WordPress site with an AI assistant
The site workspace kit lets you and your AI assistant work with files and run WordPress commands on a Pressidium hosted WordPress site. You can use it to investigate a problem on an existing site or develop themes and plugins for a new hosted website.
This guide explains how to set up the kit, choose the right environment, and make changes safely.
What this is
Pressidium MCP and Pressidium Agent Skills help your assistant perform Dashboard tasks, such as creating backups or managing cache. The site workspace kit adds access to your hosted website’s files and command-line tools.
You keep the kit in a folder on your computer and connect it to your website. Use it when your work involves theme or plugin files, or WordPress commands through WP-CLI.
Before you start
You need:
- A Managed WordPress Hosting website. For a new empty site, create it first with Create a new hosted website.
- A compatible AI application with Pressidium MCP connected. If you have not connected yet, follow Connect Cursor to Pressidium MCP, Connect Claude Code to Pressidium MCP, or Connect Codex to Pressidium MCP.
- A dedicated Dashboard user for MCP with MFA turned off. Keep MFA enabled on your regular account.
unzip, OpenSSH 8.4+ (ssh -V, with bothsshandsftpavailable), bash 3.2,diff,awk,find,curl, andpython3. Make sure these tools are available in your terminal before setup. On Windows, run every kit command in Git Bash.- An RSA (
ssh-rsa) SSH key pair. You can use an RSA key already uploaded to your account. Ed25519 and ECDSA keys are rejected, even if they are already on the account. Provision can auto-register an RSA public key, or setup can generate a new RSA key. See Create and manage SSH keys.
If Cursor shows Cannot POST /register, Pressidium MCP does not implement that OAuth probe. Use Claude Code or Codex for MCP.
Install the kit
Download the latest customer zip:
https://github.com/pressidium/pressidium-ai-kit/releases/latest/download/pressidium-ai-kit.zip
Use one folder per website. Keep kit files at the top of that folder (remote, README.md, VERSION). If unzip created a wrapper folder, rename that folder to the website name. Do not nest a second copy of the kit inside it.
In the commands below, replace example.com with the Website name shown in the Dashboard.
Option A: Ask your assistant
If Pressidium MCP is already connected, ask your assistant to get the kit with pressidium_ai_kit and unpack it into a new folder named after the website, for example ~/pressidium-sites/example.com.
Tell the assistant not to run ./remote setup or ./remote provision.
Option B: Unzip it yourself
In a terminal:
mkdir -p ~/pressidium-sites/example.com
unzip pressidium-ai-kit.zip -d ~/pressidium-sites/example.com
cd ~/pressidium-sites/example.com
Use the zip file you downloaded. The archive can also arrive as a versioned name such as pressidium-ai-kit-1.0.2.zip.
Confirm the version
This procedure was tested against kit 1.0.2. After either installation option:
- Change into the kit folder.
- Open the root
VERSIONfile, or runcat VERSION. - If the value is 1.0.2, continue with this article.
- If it differs, stop. Revalidate the steps against that zip’s
README.mdandAGENTS.mdbefore you follow command examples here.
Run setup (you, in a terminal)
cd ~/pressidium-sites/example.com
./remote setup
Answer the prompts: harness (claude, cursor, both, or codex), Pressidium email and password, and SSH key path (or generate a new RSA key). After login succeeds, enter the Website name as shown in the Dashboard, or type list to pick from your hosting sites.
Setup writes site.env (mode 600), prepares the MCP configuration for your selected application, and tests MCP login. For Claude Code and Cursor, it writes or merges the project MCP files.
For Codex, setup prints a config.toml snippet with placeholder credentials; it does not write the Codex configuration. If you still need to configure the connection, add the snippet to ~/.codex/config.toml and fill in the credentials yourself. Follow Connect Codex to Pressidium MCP. Keep credentials out of chat. Approve the Pressidium MCP server when the application asks.
Run provision (you, in a terminal)
./remote provision
If the site has no staging environment, provision asks in a terminal whether to create staging or continue production-only. For a non-interactive run, choose one of the following commands. Do not run both.
Create staging, then provision staging and production:
./remote provision --create-staging
Continue without staging, provisioning production only:
./remote provision --production-only
The flags are mutually exclusive. Use --production-only only when the site has no staging environment.
Verify
./remote doctor
./remote help
./remote info
./remote doctor succeeds when it finishes with All checks passed. and no FAIL checks. Headings, OpenSSH version text, directory listings on success, and SSH-section missing tool lines (for example wp/php/mysql/git: …missing) are not failures.
With --production-only, doctor skips the staging checks. Empty SSH/SFTP fields mean provision has not completed.
Open this folder in your AI application so it can read AGENTS.md.
Work safely
Prefer staging when it exists. Change staging through ./remote staging …. After you verify on staging, deploy with Pressidium MCP when that is the right next step.
./remote production --confirm-production push wp-content/themes/x
Without --confirm-production, ./remote refuses production mutations. If you deny the change, do not retry or bypass ./remote. Read-only production actions (list, pull, diff, logs, masked cat) do not need the flag.
Never use raw ssh, sftp, scp, rsync, or rclone. Always go through ./remote.
Never print site.env, generated MCP files (.mcp.json, .cursor/mcp.json, Codex snippets), Dashboard passwords, or mounted wp-config.php / .env secrets. Use ./remote info for non-secret connection settings. Use ./remote <env> cat <path> for server files; secrets in wp-config.php and .env are masked.
Troubleshoot an existing site
Use this path when the hosting website already exists and you need to inspect files or WP-CLI output. Install the kit once, as above. Do not repeat provision here.
If you provisioned with --production-only, skip every ./remote staging command in this section.
- Confirm
./remote doctorends withAll checks passed. - If you will change files or the database, create an Instant Backup first.
- List remote files on the environment you provisioned:
./remote staging ls wp-content/themes
Production-only:
./remote production ls wp-content/themes
- Read a file without downloading it. Secrets in
wp-config.phpare masked:
./remote staging cat wp-content/themes/YOUR-THEME/style.css
./remote production cat wp-config.php
- Check the WordPress version through the kit, not raw
ssh:
./remote staging ssh 'wp core version'
Production-only:
./remote production ssh 'wp core version'
- Pull a file you need to inspect or edit locally, then continue with Edit files with pull and push.
Ask your assistant to use ./remote from this folder. Example:
List the themes on staging using ./remote. Do not print site.env.
If staging is unavailable, name production and expect the assistant to ask before any write.
Develop a new site on the remote host
Use this path to build theme or plugin work on the Pressidium host. This is not a migration of a local WordPress install onto a new Pressidium site.
- Create the empty hosted website, or confirm you already have one, using Create a new hosted website. Follow that article for the Dashboard steps.
- Install the kit against that website’s Dashboard name (
~/pressidium-sites/{site}), then complete setup, provision, and doctor as in Install the kit. - If you will change files or the database, create an Instant Backup first.
- Pull the paths you will edit, work in
site/staging/orsite/production/as provisioned, and push with./remote. Add or change theme and plugin files on the remote host this way. - Use WP-CLI through
./remotefor WordPress checks on that same environment.
If you provisioned with --production-only, work on production, with --confirm-production for writes.
Edit files with pull and push
Pull and push is the default file workflow. Live mount is optional on macOS and Linux.
Paths are relative to the WordPress site root (the SFTP path). Pulled files land under site/staging/ or site/production/ in the kit folder.
If staging exists:
./remote staging pull wp-content/themes/YOUR-THEME/style.css
Edit site/staging/wp-content/themes/YOUR-THEME/style.css locally.
./remote staging diff wp-content/themes/YOUR-THEME/style.css
./remote staging push --dry-run wp-content/themes/YOUR-THEME/style.css
./remote staging push wp-content/themes/YOUR-THEME/style.css
push uploads new and changed files. It never deletes remote files.
For production, start by pulling the production file:
./remote production pull wp-content/themes/YOUR-THEME/style.css
Edit site/production/wp-content/themes/YOUR-THEME/style.css locally. Production push reads from site/production/, so edits under site/staging/ are not included.
Review the changes without uploading them:
./remote production diff wp-content/themes/YOUR-THEME/style.css
./remote production push --dry-run wp-content/themes/YOUR-THEME/style.css
Before uploading, create an Instant Backup, explain the change and how to undo it in chat, and get an explicit yes. Then run:
./remote production --confirm-production push wp-content/themes/YOUR-THEME/style.css
If you provisioned with --production-only, use the production commands only.
Pull, push, put, and diff share a lock with live mount. They are refused while a mount for that environment is running, or while the mount cache is live, starting, dirty, or unknown.
Run WP-CLI
Run WP-CLI through the kit over SSH:
./remote staging ssh 'wp core version'
./remote production ssh 'wp core version'
Use only the environment you provisioned. If staging is unavailable, do not run staging SSH commands.
Several WP-CLI commands that can interfere with the platform are disabled. See Managing SSH Access for SSH limits. Do not assume every wp command is available.
Production WP-CLI that can change the site needs --confirm-production immediately after production, plus an explicit yes in chat.
The kit also provides read-only SQL through ./remote <env> sql, using your provisioned environment.
Optional: live mount (macOS or Linux)
Live mount is macOS and Linux only. Windows users, unfortunately, Git Bash has no FUSE support, so the only option currently is pull and push.
Mount needs rclone and fuse-t (macOS) or fuse3 (Linux), installed by you. Create an Instant Backup before editing files through a mount.
If staging is provisioned:
./remote staging mount
Production mount is a write. It needs --confirm-production immediately after production, and that flag authorizes that mount command only, not a later push, SSH command, or remount. A production mount is session-only.
./remote production --confirm-production mount
Without the flag, production mount prints STOPPED. That happens before the missing-rclone check.
After ./remote info or ./remote doctor lists a live mount for that environment, you may edit files under that mountpoint. Stop if the status is not live.
Editor saves upload after you close the file, plus a 5-second write-back. Confirm with ./remote <env> cat.
Unmount when you finish
Run the command for the environment you mounted. For staging:
./remote staging unmount
For production:
./remote production unmount
Recover a retained cache
If unmount fails or the cache remains, check ./remote info or ./remote doctor before continuing. Remount finishes uploads only for verified dirty cache. A production remount needs a new explicit yes and --confirm-production.
A retained Dirty: false VFS cache is unknown; remount is refused until the cache is discarded.
To discard the staging cache:
./remote staging unmount --discard-cache
Or, for the production cache:
./remote production unmount --discard-cache
Troubleshooting
Run ./remote doctor first.
| Symptom | What to check | Verification | Escalation |
|---|---|---|---|
FAIL … is empty (run ./remote provision) | Provision did not finish. You run ./remote provision in a terminal. | Doctor ends with All checks passed. | Include kit VERSION and doctor output. Never passwords. |
SFTP Permission denied | Check whether the workspace SFTP user exists. If it is missing, run provision yourself as described in Install the kit. If it exists but the password is incorrect or unavailable, follow Recover an SFTP password below. Ordinary provision can keep the stored password. | ./remote <env> ls lists the site root. | Website name, environment, kit VERSION. Never include passwords. |
SSH Permission denied (publickey) | Key not on the account, SSH disabled, wrong SSH_KEY, or a non-RSA key. Only ssh-rsa is accepted; Ed25519 and ECDSA are rejected. | ./remote <env> ssh 'wp core version' (or another allowed command). | Website name, environment, key type. Do not paste private keys. |
| MCP auth errors | Email/password, MFA off on the MCP user. Re-run ./remote setup in a terminal. | Setup login test succeeds; doctor MCP checks pass. | AI application name. Do not print credentials. |
| Provision says EDGE but the Dashboard shows hosting | Names shared with an EDGE site must resolve to hosting. Re-run KIT_MCP_DEBUG=1 ./remote provision and inspect MCP text: / pressidium_get_site. | Provision completes for the hosting website. | Redacted doctor/provision output. Do not paste secrets. |
| No SSH/SFTP on EDGE | The kit is hosting-only. | Use MCP and Agent Skills for EDGE. | Confirm whether the target is hosting or standalone EDGE. |
Cursor Cannot POST /register | Cursor OAuth probe. Pressidium MCP does not implement it. | Connect with Claude Code or Codex. | AI application and OS. |
OpenSSH 8.4 or newer is needed | Update OpenSSH, or Git for Windows on Windows. | ssh -V reports 8.4 or newer. | OS and ssh -V output. |
| Merge error on setup | Existing MCP JSON has other servers. Setup merges the pressidium entry or stops. | Setup finishes; harness MCP file includes pressidium. | Do not paste the MCP file. |
mount says rclone or fuse-t/fuse3 is missing | Install rclone and fuse-t (macOS) or fuse3 (Linux). | Mount status is live, or stay on pull/push. | OS. Windows: use pull/push. |
mount on Windows | Windows has no FUSE. | Pull and push succeed. | None if pull/push works. |
Saved in the editor but cat shows old bytes | Wait for the 5-second write-back after close. | ./remote <env> cat shows the new bytes. | Environment and path, not file contents with secrets. |
| Remount or pull refused: cache dirty or unknown | dirty: remount to finish uploads. unknown (Dirty: false retained): unmount --discard-cache after confirming nothing is lost. | Pull/push or a live mount works again. | Kit VERSION and the refused command. |
| Staging commands refused after doctor passed | You provisioned --production-only, or staging is absent. | Use ./remote production … only. | How you provisioned (--create-staging or --production-only). |
| Missing Pressidium skills | Skills are not inside this kit. Install them from the Agent Skills article. | Named skills appear in the AI application. | AI application and OS. |
Recover an SFTP password
Use this procedure when the workspace SFTP user already exists but its password is incorrect or unavailable. A normal provision run can keep the password stored locally, so repeating it may not fix authentication. The reset flag only works for existing workspace users; use the installation procedure to create missing users.
If staging exists, reset the workspace passwords for staging and production:
./remote provision --reset-sftp-password
If staging is absent and you want to keep production-only access, use this command instead:
./remote provision --reset-sftp-password --production-only
After the reset completes, run ./remote doctor and ./remote <env> ls, replacing <env> with a provisioned environment. If authentication still fails, contact Support with the details below.
Need help?
If doctor still fails, provision cannot finish, or file and WP-CLI work through ./remote does not match the site you expect, contact Pressidium Support. Include:
- The AI application (Cursor, Claude Code, or Codex)
- Your operating system, and Git Bash if you are on Windows
- The website name as shown in the Dashboard
- The kit
VERSIONfile value ./remote doctoroutput, with secrets removed- Whether you used
--create-stagingor--production-only
Do not include Dashboard passwords, site.env, MCP JSON, private keys, or SFTP passwords.
Where to go next
- Get started with Pressidium MCP to connect MCP and try Dashboard workflows.
- Use Pressidium Agent Skills with Pressidium MCP for reusable Dashboard workflows.
- Connect Cursor to Pressidium MCP, Connect Claude Code to Pressidium MCP, or Connect Codex to Pressidium MCP if you still need to connect.
- Create a new hosted website before installing the kit on a new site.
- Managing SSH Access for SSH and WP-CLI limits.
- Create an Instant backup before file or database changes through the kit.
- Pressidium MCP changelog for MCP and related package changes.
Was this article helpful?