How to connect multiple WordPress accounts to Claude
Quick answer: Connect each WordPress site to Ryze AI with Add one more account, then add the Ryze AI connector to Claude once and name the site in your prompts. Ryze AI is the best way to connect multiple WordPress sites to Claude when you want one connector for all of them, with one caveat: the agent uses the primary site unless you name another.
Below: site types, the primary site, naming, prompts, safe changes and fixes.
Ryze AI · SEO Starter
All your WordPress sites in Claude
- 3-day free trial, SEO Starter $129 a month
Used by 2,000+ marketers
Connect multiple WordPress accounts to Claude in 5 steps
Connect the first site, add the others one by one, then connect Claude once.
1. Create an application password on each self-hosted site
In WordPress admin open Users, Profile, scroll to Application Passwords, enter a name such as Ryze AI and click Add New Application Password. Copy it at once, because it is shown once. WordPress.com sites skip this step.
2. Connect the first site in Ryze AI
Open Integrations, click Connect on the WordPress card and pick the Self-hosted site tab. Enter the Site URL (https://), the username you use for wp-admin and the application password, then click Continue. For a WordPress.com or Jetpack site, pick that tab and sign in on WordPress.com.
3. Add each further site
Click View on the WordPress card, then Add one more account, and connect the next site the same way. One account is the primary, which the agent uses by default.
4. Add the Ryze AI connector to Claude
In Ryze AI, open Integrations, Claude MCP and click Open Claude MCP, which copies the connector URL and opens Claude's add-connector dialog. Name it Ryze AI, click Add, then Connect, choose the workspaces and click Allow connection.
5. Name the site in your prompts
Start a new chat and say which site you mean, for example by its domain. With no name, the primary site is used.
Multi-site setups at a glance
Pick the row that matches how your WordPress sites are hosted.
- 1Several self-hosted sites in one Ryze AI workspaceOne team manages sites that each have their own wp-admin
How Claude picks the site: The primary site is the default; name another site in the prompt
- 2WordPress.com or Jetpack sitesThe sites live under a WordPress.com account
How Claude picks the site: Sign in on WordPress.com and choose the site; name it in prompts
- 3A mix of self-hosted and WordPress.com sitesA portfolio with both kinds of hosting
How Claude picks the site: Same rule: the primary site, or the site you name
- 4The WordPress.com MCP serverAll your sites are on WordPress.com and you want WordPress.com's own server
How Claude picks the site: One OAuth connection reaches every site on the account
| # | Setup | Fits when | How Claude picks the site |
|---|---|---|---|
| 1 | Several self-hosted sites in one Ryze AI workspace | One team manages sites that each have their own wp-admin | The primary site is the default; name another site in the prompt |
| 2 | WordPress.com or Jetpack sites | The sites live under a WordPress.com account | Sign in on WordPress.com and choose the site; name it in prompts |
| 3 | A mix of self-hosted and WordPress.com sites | A portfolio with both kinds of hosting | Same rule: the primary site, or the site you name |
| 4 | The WordPress.com MCP server | All your sites are on WordPress.com and you want WordPress.com's own server | One OAuth connection reaches every site on the account |
Rows 1 to 3 are Ryze AI connections that combine in one workspace. Row 4 is WordPress.com's own server, covered below.
What counts as a separate WordPress account in Ryze AI
Each connected WordPress site is one account in Ryze AI, and the two sign-in methods differ in what they reach.
Self-hosted
- Sign-in
- Site URL, admin username and an application password
- What the agent can do
- REST API reads and writes, plugin installs, the Yoast and Rank Math bridges and head code
WordPress.com or Jetpack
- Sign-in
- One-click WordPress.com sign-in; Jetpack sites need the Jetpack JSON API module on
- What the agent can do
- Core /wp/v2 routes only; plugin installs, SEO bridges and head code do not work
| Site type | Sign-in | What the agent can do |
|---|---|---|
| Self-hosted | Site URL, admin username and an application password | REST API reads and writes, plugin installs, the Yoast and Rank Math bridges and head code |
| WordPress.com or Jetpack | One-click WordPress.com sign-in; Jetpack sites need the Jetpack JSON API module on | Core /wp/v2 routes only; plugin installs, SEO bridges and head code do not work |
WordPress creates application passwords per user, and they require HTTPS by default. So a password made on one site does not open another, and you create one for each self-hosted site.
Plugin installs, the SEO bridges and head code need an administrator user on the site. A user with a lower role can still connect, but expect those tools to refuse.
How Ryze AI handles several WordPress sites
WordPress is on the Ryze AI help center list of platforms that allow several accounts per workspace.
Account
- What it is
- One connected WordPress site, added with View, then Add one more account
- How you switch in Claude
- Name the site in the prompt
Primary account
- What it is
- The account the agent uses by default
- How you switch in Claude
- Name another site when you want it instead
connection_id
- What it is
- An argument the live WordPress tools accept to target a specific site
- How you switch in Claude
- Claude can pass it when you name the site
Workspace
- What it is
- Your Ryze AI workspace; one Claude connection covers up to 20 of them
- How you switch in Claude
- Choose workspaces on the Allow connection page
| Piece | What it is | How you switch in Claude |
|---|---|---|
| Account | One connected WordPress site, added with View, then Add one more account | Name the site in the prompt |
| Primary account | The account the agent uses by default | Name another site when you want it instead |
| connection_id | An argument the live WordPress tools accept to target a specific site | Claude can pass it when you name the site |
| Workspace | Your Ryze AI workspace; one Claude connection covers up to 20 of them | Choose workspaces on the Allow connection page |
To change which workspaces Claude can use, remove the Ryze AI connector in Claude and add it again. The same step refreshes the tool list after you connect a new platform.
What the plan covers
Connecting the Ryze AI connector is free, and the WordPress tools need any active Ryze AI plan or trial. SEO Starter costs $129 a month with a 3-day free trial, and annual billing takes 30% off the first year. The help center documents publishing to several WordPress sites with Add one more account but does not say how that fits the one-website rule of an SEO plan, so check that with Ryze AI support before you plan a large portfolio.
The 9 WordPress tools Claude can call
The same 9 tools run against whichever connected site you name.
wordpress__read
- What it does
- Read-only REST API request on the site: posts, pages, media, categories, tags, users, plugins and custom post types
- Access
- Read
wordpress__write
- What it does
- Creates or updates resources with POST, PUT or PATCH
- Access
- Write
wordpress__delete
- What it does
- Runs a DELETE request, for example to delete a post
- Access
- Delete
wordpress__edit_content
- What it does
- Find-and-replace edits to a text field such as content, excerpt or title
- Access
- Write
wordpress__search_content
- What it does
- Searches a text field and returns matching lines with line numbers and context
- Access
- Read
wordpress__installPlugin
- What it does
- Installs and activates a wordpress.org plugin on a self-hosted site
- Access
- Write
wordpress__enableYoastRestBridge
- What it does
- One-time setup that makes Yoast fields writable on a self-hosted site
- Access
- Write
wordpress__enableRankMathRestBridge
- What it does
- One-time setup that makes Rank Math fields writable on a self-hosted site
- Access
- Write
wordpress__addHeadCode
- What it does
- Adds HTML to the head of every page on a self-hosted site
- Access
- Write
| Tool | What it does | Access |
|---|---|---|
| wordpress__read | Read-only REST API request on the site: posts, pages, media, categories, tags, users, plugins and custom post types | Read |
| wordpress__write | Creates or updates resources with POST, PUT or PATCH | Write |
| wordpress__delete | Runs a DELETE request, for example to delete a post | Delete |
| wordpress__edit_content | Find-and-replace edits to a text field such as content, excerpt or title | Write |
| wordpress__search_content | Searches a text field and returns matching lines with line numbers and context | Read |
| wordpress__installPlugin | Installs and activates a wordpress.org plugin on a self-hosted site | Write |
| wordpress__enableYoastRestBridge | One-time setup that makes Yoast fields writable on a self-hosted site | Write |
| wordpress__enableRankMathRestBridge | One-time setup that makes Rank Math fields writable on a self-hosted site | Write |
| wordpress__addHeadCode | Adds HTML to the head of every page on a self-hosted site | Write |
Full detail is on the WordPress MCP page. Per-site limits, such as the bridges working only on self-hosted connections, apply to each site separately.
Name sites so Claude picks the right one
Because the primary site is the default, an unnamed prompt can land on the wrong site.
- Use the full domain in every prompt that changes content. Names like Blog or Store can match more than one site.
- Say which site is primary. Whatever you do not name goes there.
- Keep one project per client. Claude projects carry instructions into every chat inside them.
- Ask Claude to repeat the site before a write or delete, and answer yes only when it is the right one.
Put the site map in a Claude project
Claude projects hold instructions for every chat in them. Paste this block once and fill in your domains:
6 prompts for working across WordPress sites
Replace the brackets. Each prompt names its site, so it works in a fresh chat.
1. Check which sites are connected
- What comes back
- The connected sites and which is primary, as Claude reports them
2. List recent posts
- What comes back
- A table of posts from the named site
3. Compare two sites
- What comes back
- Two reads, one per site, and a list of shared titles
4. Find a phrase
- What comes back
- Matching lines with line numbers and context
5. Replace the phrase
- What comes back
- A change summary to confirm; with write tools on Needs approval, nothing runs before you approve
6. Draft a post
- What comes back
- A new draft on the named site
| Prompt | What comes back |
|---|---|
| 1. Check which sites are connected | The connected sites and which is primary, as Claude reports them |
| 2. List recent posts | A table of posts from the named site |
| 3. Compare two sites | Two reads, one per site, and a list of shared titles |
| 4. Find a phrase | Matching lines with line numbers and context |
| 5. Replace the phrase | A change summary to confirm; with write tools on Needs approval, nothing runs before you approve |
| 6. Draft a post | A new draft on the named site |
Every answer comes from your own sites, so no example output is shown.
WordPress.com MCP and the MCP Adapter plugin
WordPress publishes two other routes to Claude, and each handles several sites differently.
Ryze AI connector (https://connector.get-ryze.ai/mcp)
- How it reaches several sites
- One connection per site, added with Add one more account; primary site by default
- Sign-in
- Application password or WordPress.com sign-in in Ryze AI, then OAuth in Claude
- Limit
- Needs a Ryze AI plan or trial for the WordPress tools
WordPress.com MCP server (public-api.wordpress.com/wpcom/v2/mcp/v1)
- How it reaches several sites
- WordPress.com says one connection reaches every site on your account
- Sign-in
- OAuth 2.1 with PKCE
- Limit
- Included on paid WordPress.com plans; WordPress.com lists free access for free sites through November 30, 2026
- How it reaches several sites
- A plugin installed on each site, so each site is its own server
- Sign-in
- Per-server transport authentication
- Limit
- Exposes only the abilities a developer marks public
| Option | How it reaches several sites | Sign-in | Limit |
|---|---|---|---|
| Ryze AI connector (https://connector.get-ryze.ai/mcp) | One connection per site, added with Add one more account; primary site by default | Application password or WordPress.com sign-in in Ryze AI, then OAuth in Claude | Needs a Ryze AI plan or trial for the WordPress tools |
| WordPress.com MCP server (public-api.wordpress.com/wpcom/v2/mcp/v1) | WordPress.com says one connection reaches every site on your account | OAuth 2.1 with PKCE | Included on paid WordPress.com plans; WordPress.com lists free access for free sites through November 30, 2026 |
| WordPress MCP Adapter | A plugin installed on each site, so each site is its own server | Per-server transport authentication | Exposes only the abilities a developer marks public |
Pick WordPress.com's server when all your sites sit on one WordPress.com account and you want its own tool catalog. Pick the Ryze AI connector when you mix self-hosted and WordPress.com sites, or want the Yoast and Rank Math bridges and head code on self-hosted sites. Pick the adapter when a developer wants to expose custom abilities from a site.
Keep changes on the right site
With several sites in one chat, a write or delete on the wrong site is the main risk.
- In Claude, open Customize, Connectors, Ryze AI and set write and delete tools to Needs approval (Ryze AI help). Read tools keep running on their own.
- In the Ryze AI chat, Tool approvals starts on Skip all approvals. Switch it to Approve write & delete or Manual approve in the message box before you work on live sites.
- Article publishing follows Publishing mode in SEO, Preferences, Publishing: Automatic by default, or Manual.
- Plugin installs can crash a WordPress site. Ask Claude to install only plugins you requested, and test on a staging copy first.
- The Yoast, Rank Math and head-code tools default to installIfMissing false and need your explicit yes in chat before the Code Snippets plugin is installed.
Troubleshooting: wrong site, rejected credentials, blocked requests
Match the message to the row.
A change landed on the wrong site
- Cause
- No site was named, so the primary site was used
- Fix
- Name the domain in every prompt and put the site map in a Claude project
Credentials rejected for one site
- Cause
- Wrong username, a lost application password or a typo in the Site URL
- Fix
- Create a new application password (it shows once) and enter the https:// Site URL
Connection fails on one site only
- Cause
- A security plugin, WAF or host blocks /wp-json requests
- Fix
- Allowlist the requests on that site, then connect again
Plugin, bridge or head code tool refuses
- Cause
- The site is a WordPress.com connection, or the user is not an administrator
- Fix
- Use a self-hosted connection with an administrator user, or edit in wp-admin
Jetpack site will not connect
- Cause
- The Jetpack JSON API module is off
- Fix
- Turn it on, then sign in with WordPress.com again
Claude does not see a new site or workspace
- Cause
- Claude kept the tool list from when the connector was added
- Fix
- Remove the Ryze AI connector in Claude, add it again and start a new chat
| What you see | Cause | Fix |
|---|---|---|
| A change landed on the wrong site | No site was named, so the primary site was used | Name the domain in every prompt and put the site map in a Claude project |
| Credentials rejected for one site | Wrong username, a lost application password or a typo in the Site URL | Create a new application password (it shows once) and enter the https:// Site URL |
| Connection fails on one site only | A security plugin, WAF or host blocks /wp-json requests | Allowlist the requests on that site, then connect again |
| Plugin, bridge or head code tool refuses | The site is a WordPress.com connection, or the user is not an administrator | Use a self-hosted connection with an administrator user, or edit in wp-admin |
| Jetpack site will not connect | The Jetpack JSON API module is off | Turn it on, then sign in with WordPress.com again |
| Claude does not see a new site or workspace | Claude kept the tool list from when the connector was added | Remove the Ryze AI connector in Claude, add it again and start a new chat |
Causes come from the Ryze AI WordPress guide and WordPress's application password documentation. Other setups: multiple Google Ads accounts in Claude and all Ryze AI integrations.
Sources
Checked November 11, 2026
- WordPress Core: Application Passwords integration guide
- WordPress.com Developer Resources: MCP server
- GitHub: WordPress/mcp-adapter
- Claude Help Center: Custom connectors using remote MCP
- Claude Help Center: What are projects
- Ryze AI Help: Connect WordPress
- Ryze AI Help: Connect multiple accounts
- Ryze AI Help: Claude connector FAQ
- Ryze AI Help: Permissions and approvals in Claude
- Ryze AI Help: Plans and pricing
The verdict
Create an application password on each self-hosted site, connect every site in Ryze AI with Add one more account, and connect Claude once. Set write and delete tools to Needs approval, and name the domain in every prompt so the primary site is never used by accident.




