WP Remote MCP is Live: Ask your sites anything

You can now ask ChatGPT:

“Which of my 100 sites need attention today?”

And get the answer within seconds.

WP Remote MCP is now officially live, and it gives your AI deep visibility across all the sites you manage.

Instead of opening site after site and bouncing between different tabs, now you can just ask ChatGPT and get what you need, instantly.

This is our first step towards making WP Remote completely agentic. Available now in Beta, we’re actively collecting agency feedback and adding new capabilities quickly.

So try out the MCP now, and you can shape what we prioritise next!

Deep visibility across every site you manage

WP Remote MCP has 30+ capabilities covering what agencies use every day.

It has “read-only” access, for you to safely connect your client sites and start using it to save time.

Some of the capabilities are —

• Sites: status, connectivity and account activity
• Tasks: what’s running, completed or failed
• WordPress: core, plugins, themes, updates and vulnerabilities
• Backups: recovery points, files, database tables and backup status
• Security: activity logs, firewall activity and login attempts
• Users: roles and 2FA status
• Clients & reports: client information, completed reports and scheduled reports
• Staging: staging sites, status and expiry

And this is just the start. 3 years ago, the WP Remote API launched with just 10 GET APIs. Today, it has 150+ read-and-write capabilities. Similarly, we’ll keep improving this MCP as well. 

How this starts saving you time

Which tasks failed overnight? What’s the latest recovery point for this site?

These aren’t difficult questions. And they’re just annoying when the answer is spread across 100 sites.

So here are some quick examples of how our MCP helps you out:

1. A new vulnerability drops

If you manage a handful of sites, checking them isn’t a big deal.

But if you manage 200, then it is.

First, you need to know which sites have the affected plugin or theme. Then which versions they’re running. Then which ones actually need your attention.

WP Remote MCP can look across your portfolio for plugin and theme versions, available updates, and vulnerability information.

So you can just ask: “Which of my sites are affected by this vulnerability?”

And save yourself a ton of time.

2. Client says something broke

This is where having context gets really useful. Usually the first part of debugging isn’t fixing anything. It’s figuring out what happened.

• What changed recently?
• Were there updates?
• Is there a recent backup?
• Was there unusual activity?
• What plugins and themes are running?

WP Remote already holds a lot of that information. The MCP can pull updates, activity logs, backups, and security context together so the team gets a useful starting point instead of manually investigating across different tools.

3. You have a client call in 10 minutes

You don’t always need another report. Sometimes you just need to remember what’s been happening.

• Which sites does this client have?
• Are updates pending?
• Are backups healthy?
• Has anything happened on the security side?
• What reports have gone out?

MCP can pull from the client, site, WordPress, backup, security, and reporting information WP Remote already has.

So instead of spending ten minutes preparing to get context, you can spend those ten minutes thinking about the client.

Set up MCP in 60 seconds

WP Remote MCP is live now and uses the same API token that’s already in your WP Remote dashboard.

It works with any AI client like ChatGPT Codex and Claude Code, and takes less than 60 seconds to set up.

1. Get your WP Remote API token

Sign in to your WP Remote dashboard.

1. Open the three-dot menu in the top-right corner and select My Account.
2. Open API Credentials.
3. Under API Token, select Generate API Token.
4. Copy the token and store it somewhere safe.

Note: The token is only shown once. If you generated one earlier and no longer have it, you can regenerate it. Just remember that regenerating the token invalidates the old one, so anything using the previous token will need to be updated.

2. Set your API token

Now open the Terminal on your device, replace “your_token_here” with your API key, and enter this command:

export WPREMOTE_MCP_TOKEN=”your_token_here”

3. Connect to WP Remote’s MCP

Once you’ve set up your API token, you only need to run one command to connect to WP Remote.

If you use Codex

Open the Terminal on your computer, then copy and paste this command:

codex mcp add wpremote \
–url https://mcp.blogvault.net/mcp \
–bearer-token-env-var WPREMOTE_MCP_TOKEN

Now, open Codex and ask: Is the WP Remote MCP connected and working?

If everything is set up correctly, Codex should show that WP Remote is connected.

If you use Claude Code

Open the Terminal on your computer, then copy and paste this command:

claude mcp add \
–transport http \
–scope user \
–header ‘Authorization: Bearer ${WPREMOTE_MCP_TOKEN}’ \
wpremote https://mcp.blogvault.net/mcp

Now, open Claude Code and ask: Is the WP Remote MCP connected and working?

If everything is set up correctly, Claude Code should show that WP Remote is connected.

4. Try it on a real task

Once WP Remote shows as connected, you can start asking Codex or Claude Code to work with your WordPress sites.

Start with:

Check all the sites I manage. Tell me which ones need my attention today and why.”

Then try something your team actually had to figure out this week. That’s where you’ll see whether it saves you time.

Need help getting connected?

We’re happy to jump on a quick demo call and set it up with you.

What’s coming next

Deep visibility is the starting point. The bigger goal is to make WP Remote increasingly agentic. We already have a long list of things on the roadmap, but we don’t want to build that list in a vacuum.

If there’s a workflow you repeat every week, tell us.

If you get halfway through something and think, “It would be amazing if it could do this next part too,” definitely tell us.

We’re adding capabilities quickly, and the agencies using MCP now have a chance to shape what we prioritise next. Email us at support@wpremote.com.

Frequently asked questions