Setting up a store with an AI assistant

You can connect an AI assistant to your WordPress site in three main ways. The simplest is to give Codex or Claude access to Chrome, sign in to WordPress yourself, and let the assistant use the dashboard just as you would. The more managed route is MCP, which gives the assistant a defined set of tools for configuring plugins and maintaining the site. Developers can also connect over SSH, which gives the assistant terminal access to WP-CLI, the site files and any other server tools allowed by the SSH account.

Chrome is much quicker to get going and can cover anything available through the WordPress dashboard, including tasks that have no MCP tool yet. MCP takes a little more setup, but it is usually preferable for repeated or large jobs because each action is structured, access can be limited, and the assistant can verify results without relying entirely on buttons and page layouts. SSH is the most powerful option and can install anything else needed on the site, but it also needs the most care. You can combine the methods: MCP for supported actions, Chrome for anything only available in the dashboard, and SSH when the work genuinely needs server or command-line access.

What is MCP?

MCP stands for Model Context Protocol. It is a standard way for an application or plugin to give an AI assistant a documented set of tools. Instead of visually finding a button and clicking it, the assistant can call a specific action such as listing plugins, updating an article or configuring filters, with clearly defined inputs and results.

That makes MCP faster and more dependable for repeatable work. It also gives the site owner more control because the connection can expose only particular actions and can require confirmation for sensitive changes. Browser control is broader but less structured: the assistant can operate almost anything you can reach in the dashboard, although it depends on the current screen layout and must work through forms one click at a time.

You do not have to choose one permanently. Start with Chrome if you want the fastest setup, or use MCP when a plugin provides it and add Chrome whenever the MCP connection does not cover a task. Reach for SSH when the job needs WP-CLI, site files or other server tools.

Using Super Speedy Plugins with your site through AI

You do not need to learn the names of the individual tools or give your assistant a step-by-step command sequence. Connect it once, then describe the result you want.

Connect your site

1. Install any Super Speedy plugin.
2. Enter your licence on the Super Speedy Plugins settings page.
3. Open the MCP setup page and copy the command shown there.
4. Paste the command into your terminal.

That connects Claude or Codex to your WordPress site. Starting with any Super Speedy plugin is enough: once connected, the assistant can see the available Super Speedy plugins and install the ones needed for the job, asking for confirmation when required.

Ask for the result

Then tell Claude or Codex what you want in ordinary language. For example:

• Migrate my imports from WP All Import to Super Speedy Imports.
• Migrate my filters from traditional WooCommerce filters to Super Speedy Filters.
• Speed up my website.

The assistant inspects the existing site, works out which plugins and changes are needed, explains the plan, asks for confirmation before sensitive changes, completes the work and verifies the result. You do not need to know or copy the internal tool names. The assistant discovers and uses those itself.

General site maintenance

Super Speedy MCP covers the Super Speedy plugin range. If you also want the assistant to read and write ordinary WordPress posts and pages, manage media, or inspect the rest of the site, add a general WordPress MCP plugin.

Recommended WordPress MCP plugins

• AI Engine is the straightforward choice for content and day-to-day site administration. Its MCP server lets compatible assistants manage posts, media and other WordPress data through natural-language requests.
• Novamira gives an assistant much broader access, including PHP execution, the database and files. Its own documentation recommends it for development and staging environments, so do not treat it as the default choice for an ordinary live site.
• Other WordPress MCP plugins can work too. Check that the plugin documents exactly what the assistant can read and change, uses authenticated HTTPS access, supports a restricted WordPress user, and lets you disable or revoke access easily.

Use Codex or Claude Code on your computer

For this kind of work, use the Codex desktop app or Claude Code on your own computer. They can keep the MCP connection, terminal, local files and browser in one working session, which makes it much easier for the assistant to inspect the site, make a change and verify the result.

A typical setup is:

1. Install and configure the WordPress MCP plugin.
2. Create a dedicated WordPress user with only the permissions the assistant needs.
3. Copy the connection command or setup prompt generated by the plugin.
4. Paste it into Codex or Claude Code.
5. Start with a read-only request, then approve writing changes once the assistant has shown you what it found.

Useful first requests include:

• Audit my published articles for broken links and give me the list before changing anything.
• Update this article, keep it as a draft, and show me exactly what changed.
• Find images without alt text and fix the obvious ones.
• Check my plugin updates and tell me which ones need attention.

Using a Chrome extension instead

You do not need to install an AI or MCP plugin on WordPress if you are happy for the assistant to use the dashboard itself. The official ChatGPT Chrome extension can give Codex access to your existing Chrome tabs and signed-in session. Claude Code can do the same through Claude in Chrome.

Set it up

1. Install the browser extension for Codex or Claude Code.
2. Open your WordPress dashboard in Chrome.
3. Sign in yourself when asked. Do not paste your WordPress password into the conversation.
4. Tell the assistant what you want it to do.
5. Watch it navigate the dashboard, click the same buttons you would click, and pause when it needs confirmation or another login step.

For example, you can ask it to update an article, install a plugin, change WooCommerce settings, check an order configuration or work through a maintenance checklist. It can inspect the visible result afterwards instead of assuming the clicks worked.

Connecting over SSH

If your host provides SSH access, Codex or Claude Code can connect to the server through its terminal. The assistant can then use WP-CLI to inspect and update WordPress, install and activate plugins, manage options and content, run database commands, inspect logs and work with site files. It can also install another WordPress plugin or server-side tool needed to complete the job, as long as the SSH account has permission to do so.

The official WP-CLI plugin commands cover installing, activating, deactivating and updating plugins. WP-CLI also supports running commands against a remote server over SSH.

Set it up safely

1. Create a dedicated, non-root SSH user with access only to the site it needs to maintain.
2. Use SSH key authentication. Add the key to your computer yourself rather than pasting a password or private key into the conversation.
3. Tell the assistant the SSH host alias and the path to the WordPress installation.
4. Ask it to confirm the site, environment and available WP-CLI commands without changing anything.
5. Take a current backup and use a staging site for plugin installation, updates, code changes, imports or database work wherever possible.

Good first requests are:

• Connect over SSH, find the WordPress installation and report its status. Do not change anything.
• Check which plugins need updates and show me the plan before installing anything.
• Install the plugin needed for this task on staging, verify it, then stop for approval.

SSH is a good choice for developers, bulk maintenance, debugging and jobs that need both WordPress and server access. For ordinary article edits or plugin settings, Chrome or MCP usually exposes less of the server and is easier to control.

Other ways to set up and maintain your store

Use the WordPress REST API directly

WordPress includes a REST API and revocable Application Passwords. A technical user can create a dedicated WordPress account, generate an Application Password, and let Codex or Claude Code manage posts, pages, media and other supported data over HTTPS without installing a general AI plugin. See the official WordPress REST API authentication guide.

Keep the Application Password in the agent’s secure connection configuration, not in an ordinary chat message. Revoke it from the WordPress user profile when the work is finished.

Choose the narrowest route

Whichever route you choose, ask the assistant to inspect first, explain its plan, make the smallest necessary change, and verify the result. Use drafts for content until you have reviewed it, and use staging for anything that changes code or the database.

Further reading

Related products

Super Speedy FiltersFast product filters and pretty, indexable permalinks on every archiveSuper Speedy ImportsEasy to use. Built for speed.