If you have ever asked Claude to help with WordPress, you know the routine. You describe the problem, Claude writes some code without seeing your actual site, you paste it into WordPress, test it, and half the time something breaks because the AI was guessing about your theme and setup the whole time.
Connecting Claude directly to your site ends that. Once connected, Claude can read your files, edit your theme, create pages, and manage content from inside the same chat window, working on your real site instead of a hypothetical one. This guide walks through the setup step by step. It takes about five minutes.
Prefer to watch instead of read? Here is the full setup as a video walkthrough:
What you need before you start
This setup assumes a few things are in place. None of them take long:
A WordPress site on version 6.9 or higher, running PHP 8.0 or higher.
Administrator access to that site. Only admins can connect, by design.
Claude Desktop installed on your computer (or Claude Code, Cursor, or Windsurf, the steps are nearly identical).
Node.js 18 or higher installed on your local machine. Note this goes on your computer, not your WordPress server. Nothing extra is installed on the site itself.
If you do not have Node.js yet, install it first. It is a quick, standard install, and the SproutOS docs have an OS-by-OS walkthrough if you need it.
Step 1: Install the SproutOS plugin
SproutOS is the plugin that turns your WordPress site into something Claude can connect to. You download it directly from the SproutOS site, then upload it to WordPress like any other plugin:
Download the SproutOS plugin ZIP from sproutos.ai.
In your WordPress admin, go to Plugins > Add New > Upload Plugin.
Choose the ZIP you downloaded, click Install Now, then Activate.
Once activated, you will see a new SproutOS menu in your WordPress admin sidebar.
Step 2: Generate your connection password
Claude connects to your site securely using a WordPress Application Password. This is a special password just for the connection, separate from your normal login, and you can revoke it any time.
In your WordPress admin, open the SproutOS menu and go to the MCP Connect tab.
Generate a new Application Password there.
Copy it and keep it somewhere safe for the next step. WordPress only shows it once.
Step 3: Add your site to Claude
Now you tell Claude where your site is and how to reach it. The MCP Connect tab gives you a ready-made configuration snippet for this. You copy that snippet into Claude's MCP configuration file, filling in your site URL and the Application Password you just created.
The exact snippet and file location depend on which client you use (Claude Desktop, Claude Code, Cursor, or Windsurf). SproutOS gives you the correct one for your client right in the MCP Connect tab, so you do not have to write it by hand. Follow the copy-paste steps in the SproutOS Quick Start guide for your specific client.
Step 4: Restart and confirm the connection
Save the config file and fully restart your AI client so it picks up the new connection. When it reopens, Claude should now list your WordPress site as an available connection.
To confirm it worked, type a simple read-only request, something that looks but does not change anything:
"List the pages on my WordPress site."
If Claude comes back with your actual page list, you are connected. That is the whole setup.
Start safe: turn on read-only mode first
Before you let Claude change anything, a strong habit for your first session is to keep it in read-only mode. In the AI Abilities tab, turn on Safe Mode. This lets Claude see everything on your site but write nothing, so you can explore what it can do with zero risk.
Try prompts like:
"What theme am I using and what plugins are active?"
"Show me the structure of my homepage."
Once you are comfortable, switch Safe Mode off and let Claude start making changes. A few first tasks worth trying:
"Create a draft About page with placeholder content."
"Check which of my plugins have updates available."
A note on doing this safely
Giving an AI direct access to a live site is powerful, so treat it with the same care you would any admin tool. Two sensible habits:
Start on a staging site if you have one, get familiar with the workflow, then move to production once you trust it.
Keep a backup before any big session, the same as you would before a major plugin update.
SproutOS has safety layers built in for exactly this reason. Sensitive files like wp-config.php are blocked entirely, any custom PHP runs in an isolated sandbox rather than against your core files, and if something errors, Crash Guard disables the offending file and flips on Safe Mode automatically. You stay in control the whole time.
That's it
Five minutes of setup, and Claude goes from guessing about your site to working on it directly. No more copy-paste loop, no more explaining your setup over and over.
Top comments (0)