Pressidium MCP changelog
This page lists customer-visible changes to the Pressidium MCP beta and the optional Pressidium Agent Skills package.
Use it if you manage Pressidium websites through an AI assistant (Cursor, Claude Code, or Codex). Your assistant can treat this page as current product behavior.
Pressidium hosts the MCP server. You do not deploy it. Keep the same server URL, including /dashboard. After a release, restart or reconnect the MCP session if a new tool or action is missing, a retired tool still appears, or your assistant reports a connection error. Update Agent Skills separately when a new skills package is listed below.
Versions are listed newest first.
Version 0.2.17
16 November 2026
This release lets your assistant offer the Pressidium site workspace kit: a zip for live files, WP-CLI, SQL, and an SFTP mount on Managed Hosting. Pressidium MCP only tells the assistant where to download. You confirm the download and the folder. After unpack, you run setup in a terminal.
What improved
- You can ask to install or update the site workspace kit. The assistant should call
pressidium_ai_kitand report the zip URL. - The zip comes from the public GitHub Release:
https://github.com/pressidium/pressidium-ai-kit/releases/latest/download/pressidium-ai-kit.zip. - The kit is Managed Hosting only. Pressidium EDGE sites do not get a kit.
- Default folder is a new directory named with a path-safe website slug (for example
myshopormyblog), under~/pressidium-sites. - The assistant must not overwrite an existing kit folder. Updates unpack beside the old copy. You copy
site.envyourself. - After unpack, you run
./remote setupthen./remote provisionin a terminal. The assistant must not run those commands. That is by design: setup and provision collect your Dashboard password and writesite.env. Running them in chat would risk sending those credentials to the assistant.
See Work on your WordPress site with an AI assistant.
Behavior your assistant should follow
These are the behavior changes your assistant should follow in 0.2.17.
Call pressidium_ai_kit for the zip URL and rules. Optional website only suggests a default folder name. It does not select a Dashboard site.
Never download until the user confirms the download. Never unpack until the user confirms the destination. After download and validation, recheck that the destination is still empty, then unpack.
Do not unpack into a skills directory. Do not replace a live kit folder in place. Do not run ./remote setup or ./remote provision. Those commands stay in the user’s terminal so credentials are not sent to the assistant. After a successful unpack, tell the user to run those two commands in a terminal, in that order.
If the user already has a kit and asks for files, WP-CLI, SQL, or a mount, continue with ./remote. Do not start another update check in the same conversation unless they ask.
If the assistant says pressidium_ai_kit is missing, reconnect the MCP session.
Pressidium Agent Skills
Version 0.2.17 of Pressidium MCP works with Agent Skills package 1.0.3.
- Skills package 1.0.3 adds
act-install-ai-kit(offer the zip, confirm destination, unpack into a new folder, then stop so you can run setup and provision). - The library is now 45 skills (36 building blocks and 9 composites).
- After updating Skills, start a new chat if the assistant still follows the old workflow.
See Use Pressidium Agent Skills with Pressidium MCP.
Version 0.2.16
12 November 2026
This release has no assistant-visible product change. Your tools, skills, and login are unchanged.
What improved
- Nothing you need to do differently. Website lookups, SFTP, backups, and the rest behave as in 0.2.15.
Behavior your assistant should follow
You may see a tool named get_more_tools. It is not a Pressidium Dashboard action. Do not use it to manage websites.
Pressidium Agent Skills
Version 0.2.16 of Pressidium MCP still works with Agent Skills package 1.0.2. You do not need a skills update for this release.
What you do not need to change
- Your MCP server URL is unchanged. Keep
/dashboardon the end. - Reconnect only if the assistant reports a connection error.
Version 0.2.15
2 November 2026
This release lets your assistant find a Pressidium EDGE site by display name, the same way it finds a Managed Hosting website. Waiting for a finished job (backup, staging, clone, and similar) is also more reliable.
What improved
- You can say an EDGE display name (for example
mystore) instead of only theenv_…site id. - Website lists and site details show EDGE as
mystore #env_123456789when a name exists, or#env_123456789when it does not. - If the same name exists on Managed Hosting and EDGE, the assistant should not guess. It should ask you to pick:
siteIdfor EDGE, orwebsitewithkind=hostingfor Managed Hosting. - If several EDGE sites share a name, pass
siteId. - Staging, clone, migrate, backup list/create/download, and certificates still use Managed Hosting targeting. They do not accept an EDGE name.
Behavior your assistant should follow
These are the behavior changes your assistant should follow in 0.2.15.
For site-scoped tools that accept website, treat that value as a Managed Hosting website name or an EDGE display name. Use optional kind: "hosting" or kind: "edge" only together with website, and only after a clash error (or when the user already said which kind).
Do not invent an EDGE siteId. If the tool says the name is missing, duplicated, or over the lookup cap, follow that message: pass siteId, or website with kind=hosting.
When the user asks to wait for a job to finish, wait for the real completed result. Do not stop at “job not found” if the work already finished.
Pressidium Agent Skills
Version 0.2.15 of Pressidium MCP works with Agent Skills package 1.0.2.
read-site-identitymatches Managed Hosting vs EDGE by name and retries clash or duplicate errors as the tool text says.- You do not need a new skills version number for 0.2.15. After a skills replace, start a new chat if the assistant still cannot resolve an EDGE name.
See Use Pressidium Agent Skills with Pressidium MCP.
What you do not need to change
- Your MCP server URL is unchanged. Keep
/dashboardon the end. - Your Dashboard login is unchanged.
- SFTP connection lookup from 0.2.14 still applies.
Version 0.2.14
29 October 2026
This release lets your assistant look up where to SFTP on a Managed Hosting website: host, port, and path. After you create an SFTP user and wait for that create to finish successfully, the assistant should also report the new username, host, port, path, and a pasteable sftp command.
What improved
- You can ask how to SFTP to a Managed Hosting website without creating a user. The assistant should report host, port, and path.
- After you create an SFTP user and wait for it to finish, the assistant should also report the new username, host, port, path, and a pasteable command like
sftp -P {port} {username}@{host}. - SFTP connection lookup is Managed Hosting only (production or staging). Pressidium EDGE sites are not supported.
- This is not a new MCP tool. It is a new action on
pressidium_sftp_users(connection). If the assistant says that action is missing, reconnect the MCP session.
Behavior your assistant should follow
These are the behavior changes your assistant should follow in 0.2.14.
Look up SFTP details without creating a user. For “how do I SFTP to this site?”, call pressidium_sftp_users with action: connection. Report host=, port=, and path= from the tool text. Do not invent a username or an sftp command on a connection-only lookup.
Creating an SFTP user still needs the full username and password. You supply both. Pressidium MCP does not add the {website}-prod- or {website}-stag- prefix. Important: Never print the password.
The pasteable command appears only after a successful create you waited for. Report the new username, host, port, and path, plus a command like sftp -P {port} {username}@{host}. Listing users, deleting a user, or setting a password does not include connection details.
Username rules from 0.2.13 still apply. Replace {website} with the website name returned by Pressidium. Production usernames must start with {website}-prod-. Staging usernames must start with {website}-stag-.
Pressidium Agent Skills
Version 0.2.14 of Pressidium MCP works with Agent Skills package 1.0.2.
- Skills package 1.0.2 adds two building blocks:
read-sftp-state(look up host, port, and path) andact-create-sftp-user(create a user, wait, then print connection details). The create skill never prints the password. - The library is now 44 skills (35 building blocks and 9 composites).
- After updating Skills, start a new chat if the assistant still follows the old workflow.
See Use Pressidium Agent Skills with Pressidium MCP.
What you do not need to change
- Your MCP server URL is unchanged. Keep
/dashboardon the end. - Your Dashboard login is unchanged.
- SFTP list, create, delete, and set password still work as in 0.2.13. SSH, backups, cache, and the other tools from 0.2.13 still apply.
Version 0.2.13
26 October 2026
This release makes assistant answers clearer and safer. Request rules now match the Dashboard more closely. It also adds guided Agent Skills install and update.
What improved
- Website and backup lists stay short by default. Ask for full detail only when you need it.
- Database passwords, SSH private keys, and similar secrets are no longer included in assistant results.
- Website summaries include mapped hostnames, plugin and theme counts, and the active theme.
- Backup, cache-exclusion, and SFTP lists are easier to read (IDs, types, and dates where they apply).
- Usage figures use clear labels such as visits this month, CDN this month, and last disk check.
- An idle MCP session now lasts 8 hours. If the session is no longer valid, the assistant should reconnect and continue.
- Database info (name, size, prefix) comes from the website record, not phpMyAdmin.
- Certificate signing requests (
create_csr) return the CSR and private key in structured data. UsecommonName,organizationName,organizationUnit,city,state, andcountryCode(2-letter). Do not sendcountryName. - If object cache is off, a cache purge says so in plain language instead of a raw error.
- If a website-refresh request is denied for your role, the assistant should report a permission problem, not an expired session.
Behavior your assistant should follow
These are the behavior changes your assistant should follow in 0.2.13.
CDN is always on for Managed Hosting. There is no enable or disable CDN action in Pressidium MCP. Do not call pressidium_cdn. Treat hosting CDN as included. You can still purge CDN cache with pressidium_purge_cache and scope=cdn when the website has a mapped domain. If it has none, the assistant should say to add a domain and retry — not retry enable or disable.
SSH keys are RSA only. New keys must start with ssh-rsa followed by a space. Ed25519 and ECDSA are rejected.
SFTP usernames need a prefix. Replace {website} with the website name returned by Pressidium. Production usernames must start with {website}-prod-. Staging usernames must start with {website}-stag-. Pressidium MCP does not add the prefix for you.
Cache exclusions are one path at a time. Add or update a single exclusion. Paths must start with /, must not be the homepage /, and must not include ?.
PerfAudit start needs a mapped domain on production. If none exists, the assistant should report: PerfAudit requires a mapped domain. This website has none. Add a domain, then retry. Default is one iteration unless you ask otherwise.
Firewall activity is not available on website staging. Ask for production (or platform/user groups, as supported).
Plugin activate and deactivate send a list of plugin slugs. Ask the assistant to confirm the exact plugins before approving.
Log download no longer pulls gzip or CSV files through MCP. The assistant should use the log lines returned in the conversation. If Pressidium MCP also returns a Dashboard path or next step, follow that instead of downloading a file through MCP.
Pressidium Agent Skills
Version 0.2.13 of Pressidium MCP works with Agent Skills package 1.0.1.
pressidium_skillstells the assistant where to download the public skills zip and how to install or update it. Confirm the destination before any download or replacement.- Important: Local edits in that folder will be lost if you replace the package.
- Skills package 1.0.1 matches the CDN change above: hosting CDN is treated as always on. Do not ask a Skill to toggle CDN.
- After updating Skills, start a new chat if the assistant still follows the old workflow.
See Use Pressidium Agent Skills with Pressidium MCP.
What you do not need to change
- Your MCP server URL is unchanged. Keep
/dashboardon the end. - Your Dashboard login is unchanged.
- Existing Cursor, Claude Code, and Codex connection guides still apply.
- Cache purge, backups, plugins, staging, and the rest of the supported tools remain available within your account permissions.
Need help?
If something in this changelog does not match what your assistant reports, contact our support and include:
- The AI application you are using
- The website name and environment
- The version on this page (for example 0.2.17)
- Whether Pressidium MCP connects successfully
- The request you made and the message you received
Do not include your Dashboard password, credential environment variables, or other secrets.
Where to go next
Was this article helpful?