What an AI assistant can do with your Noiz account
AI assistants such as Claude can now do more than answer questions. Connected properly, an assistant can read and change your WordPress site, manage products and orders in your WooCommerce shop, write and deploy code on your hosting, and walk you through tasks in your control panel. This article is the starting point of our series on using AI with Noiz: what is possible today, which plan each task needs, and the rules we ask every client to follow so that an assistant helps rather than harms.
Last reviewed: 19 October 2026, against WordPress 6.9, the WordPress MCP Adapter plugin and Plesk Obsidian.
Official Documentation Reference
- WordPress MCP Adapter: the plugin that lets an AI client talk to a WordPress site.
- WooCommerce: MCP: how WooCommerce exposes products and orders to AI clients.
- Anthropic: Model Context Protocol: how Claude connects to tools and services.
- Plesk Obsidian Customer Guide: the control panel on Noiz shared hosting.
How an AI assistant connects to your services
An assistant on its own can only talk. To act on your site or hosting it needs a connection, and the connection is what you control. Three kinds matter for Noiz clients:
- A connector (MCP). The Model Context Protocol is an open standard that lets an AI client such as Claude Desktop or Claude Code call a defined set of tools on a service. WordPress and WooCommerce now provide one through the MCP Adapter plugin. You give the assistant a username and an application password for your site, and it can only do what that user may do.
- A terminal (SSH). An AI coding tool such as Claude Code can work inside a shell on your hosting: read and edit files and deploy. This needs shell access, which is included on sPremium and not available on sLegacy.
- Your browser. Some assistants can drive a web browser and click through a control panel or the console for you. This is the least safe option for anything that involves a login, and we explain why in the article on what not to let an AI do.
In every case the assistant acts with the permissions of the credential you gave it. The whole of our safety advice follows from that one fact: give it a credential of its own, with the least access that does the job, and take it away when you are done.
What you can do today, plan by plan
| Task | What you need | Plan |
|---|---|---|
| Build a static website with an AI tool and publish it over FTP | An FTP account in Plesk, a free Let's Encrypt certificate | Any Noiz plan; sLegacy is made for it |
| Let an assistant search, summarise and draft replies in your email | A mailbox on your domain, a desktop mail client such as Thunderbird, a connector for it | Any Noiz plan with email |
| Ask an assistant to draft posts, pages and product descriptions, and publish them to WordPress | WordPress 6.9 or later, the MCP Adapter plugin, a dedicated user with an application password | Any Noiz plan with WordPress |
| Query and update products and orders in WooCommerce, add order notes | As above, with WooCommerce current | Any Noiz plan with WooCommerce |
| Let an AI coding tool edit theme or plugin code over SSH and deploy from Git | SSH access with its own key, Git in Plesk | sPremium |
| Build a plugin or theme with an AI tool and deploy it without downtime | SSH, Git deployment, a staging copy in WP Toolkit | sPremium |
| Run your own AI models and agents (Ollama, Open WebUI, long-running automations) | A server of your own | Noiz Cloud, orderable now |
Two things are true of every row. The site tasks work on both shared hosting families, sLegacy and sPremium, because they only need WordPress and a secure connection. The server-side tasks need sPremium, because sPremium includes SSH access limited to your own hosting account, Git deployment, Node.js and a dedicated PHP pool, and sLegacy includes none of them. If you find yourself wanting the second group, compare the shared hosting plans or open a ticket and we will recommend the right one from your actual usage.
The rules we ask every client to follow
- One credential per assistant, and never your own. Create a separate WordPress user, application password or SSH key for each AI tool. Never give an assistant the password you log in with, and never your Noiz console login.
- Least access. A user that only needs to write posts does not need to install plugins. A key that only needs to deploy does not need the whole account. Start read-only where the tool allows it and add write access when you see it behaving.
- Back up first. Take a backup in your control panel before an assistant changes anything, and know how to restore it. Weekly backups are included on every Noiz shared plan; a backup you took five minutes ago is the one you will want.
- Review before publish. Let the assistant draft; you approve. For code, let it work on a staging copy or a branch, and deploy when you have checked the result.
- Revoke when done. Application passwords, keys and users that an assistant no longer needs are removed, not left running.
- Some things stay manual. Passwords, DNS, payment settings, deleting anything, agreeing to terms, and your Noiz account itself. The article on what not to let an AI do lists them with reasons.
The series
Your sites
- Build a static website with an AI tool and publish it over FTP. A site in an afternoon on sLegacy, no database, nothing to patch.
- Connect Claude to your WordPress site safely. A dedicated user, an application password, the MCP Adapter, and how to revoke it.
- Manage your WooCommerce shop with an AI assistant. Products, orders and notes, read-only first, and what to do about customer data.
- Use an AI assistant with your managed application. Nextcloud and Odoo on Managed hosting, by each application's API.
Your email
- Use an AI assistant with your Noiz email. What works with an IMAP mailbox on your own domain, and what to never paste into a chat.
- Outlook users: what Copilot can and cannot do with a Noiz mailbox, and the better route.
- Triage your inbox with Thunderbird and an AI assistant, the way we do it.
Your hosting and the sPremium toolset
- Let an AI coding tool work on your site over SSH. Claude Code on sPremium with its own key and Git.
- Build and deploy a plugin or theme with an AI coding tool. From a broken plugin to one of your own.
- The sPremium toolset, tool by tool. Git, Node.js, PHP versions and staging.
- Let an AI assistant work in Plesk for you. What it can reach, what it guides you through, and why there is no client API today.
- Mailboxes, forwarders and spam settings with an AI guiding you.
Your account
- Your Noiz console and AI. The console today and sub-accounts with limited permissions.
- Domains with an AI assistant. Searching and registering, and what stays manual.
Safety
- Back up before you let an AI change anything. The backup and restore steps in Plesk, and a staging copy in WP Toolkit.
- How to decide what not to let an AI do. The short list, and why.
- Troubleshoot it with AI. Prompts you can paste for the common faults.
Noiz Cloud
- Run your own AI tools on Noiz Cloud follows, and the OpenStack API is coming.
Articles are added to this page as they are published. If a task you want is not here, open a ticket and tell us what you are trying to do; it helps us decide what to write next.
Why we are writing this
Clients are already using AI tools to build and run their sites, and we would rather show the safe way than find out afterwards. We also think this is what hosting is for: Noiz provides the infrastructure, you bring the tools, and the assistant works for you on your terms, on hosting you have a contract for.
