How this differs from the local MCP server
The MainWP MCP Server runs on your own computer and signs in with an Application Password. Remote connections run inside the Dashboard instead.
Both can be used side by side. If your app can’t connect remotely, the local server remains the fallback: see Connect Your AI Client.
Requirements
- MainWP Dashboard 6.5 or later. Earlier versions do not have the Connect directly view on the MainWP MCP page.
- HTTPS site address. The Dashboard’s site address must start with
https://. With anhttp://address the connector can’t be turned on. - PHP 8.3 or newer, as required by MainWP Dashboard 6.5.
- WordPress 6.9 or newer. The connector uses the WordPress Abilities API.
- The activity log turned on. AI apps can only make changes, or use tools MainWP hasn’t reviewed, while each call is recorded, so the connector can’t be turned on until Enable Network Activity logging is on under MainWP Settings > Network Activity Settings. If you turn the log off later, the Dashboard refuses those calls until you turn it back on. The read tools MainWP has reviewed keep running, but they aren’t recorded while the log is off.
- An administrator account. Managing the panel and connecting an app both need the
manage_optionscapability. Turning the connector on or off, and the switches under Tools and Which apps can connect, also need an administrator without Team Control limits. - A web server that passes two addresses to WordPress:
/.well-known/oauth-authorization-serverand/.well-known/openid-configuration. Apps read them to learn how to sign in. The self-test checks this for you.
Turn on remote AI connections
1
Turn on the activity log
Open MainWP Settings > Network Activity Settings from the top-right user menu and turn on Enable Network Activity logging. Save the settings.
2
Open Connect directly
In MainWP Dashboard, open MainWP > AI > MainWP MCP > Connect directly (
/wp-admin/admin.php?page=mainwp-mcp&tab=direct). The Remote AI connections section shows whether the connector is on.3
Run the self-test
Click Run the self-test. Each line shows
pass, warn, fail or info. Fix every fail line first. Troubleshooting explains each line and its fix.The self-test runs from the Dashboard itself, so it can’t see what an app on the internet sees. Click Check from the internet for that view. It sends only your Dashboard’s address to MainWP’s checker, and nothing is stored.4
Turn it on
Click Turn on. If a blocking check still fails, the panel shows “Remote AI connections can’t be turned on yet. Fix the checks below first.” and lists the reasons.When it works, the panel reads “On. AI apps you approve can connect to this Dashboard over the internet.”
5
Connect your app
The Connect an app section shows a ready configuration for each supported app. Follow the steps for your app in Set Up Your AI App.
Your MCP address
Every app connects to the same address. With pretty permalinks it is:What you see when an app connects
The app opens your Dashboard in a browser. If you aren’t signed in, WordPress asks you to sign in first. Then the consent screen, titled An app wants to connect to your Dashboard, shows:- the app’s name and the host its identity comes from, for example Claude Code (claude.ai). An app on your computer that named itself shows that name followed by “(name not checked by MainWP), an app on this computer”.
- the warning “Only approve if you just started this in your own app.”
- where you return after deciding: “After you decide, you’ll return to” followed by a host name
- the account you’re signed in as, with Not you? Log out
- a Team Control line when your account is limited to some sites, because the app sees only what you can see
- What the app can do: View and make changes or View only. Apps that ask only for view access show no choice.
- Approval policy: Standard or Strict, plus Hands-off for users without Team Control limits. It appears only when the app asks to make changes. See Approval Policies.
The security model
The app acts as you. Each connection belongs to the user who approved it. The app gets your WordPress permissions and your Team Control limits, never more. If you lose themanage_options capability, change your password or are deleted, your connections end.
You choose the access. View only lets the app read data and list tools. View and make changes also lets it call tools that change sites, each one through an approval tier. You can change a connection to view only in the panel at any time. Allowing changes again needs a new connection.
The Dashboard enforces approvals. Every tool has a tier. Read and Write tools run directly. A Confirm tool runs only after a confirmation in the chat that is bound to a preview. A Dashboard tool waits until you approve it on a page of your Dashboard, signed in as yourself.
The connection’s approval policy moves tools between tiers. The Dashboard tier is the only one that proves a person approved: the app can’t click it for you. Approval Policies lists which tools are in which tier.
Tokens only work on the MCP address. On the WordPress Abilities API, the MainWP REST API and admin-ajax, the app’s tokens don’t sign anyone in. Access tokens last 30 minutes. Apps that ask for offline access renew them on their own; an app that doesn’t has to sign in again when its token expires. A connection lasts up to 30 days, or until it goes 14 days without use, then the app asks you to sign in again.
Only known apps can connect. The Dashboard ships the sign-in details of seven apps: Claude, Claude Code, ChatGPT, VS Code, Codex CLI, Zed and Goose. Cursor and Gemini CLI use fixed client IDs. Apps on your own computer can register themselves, but only with a callback address on that computer. Multi-user web apps such as Open WebUI need an administrator to add them. Any other app is refused before sign-in with “MainWP doesn’t support this app yet”. The Dashboard never downloads an app’s details from the internet.
You control the tools. The Tools section of the panel has a switch per category and per tool. A tool you switch off is neither listed nor callable. Extension tools that MainWP hasn’t reviewed appear under Not reviewed by MainWP and always need your approval on the Dashboard, unless the connection uses Hands-off.
Large jobs run in the background. By default, an action over more than 10 sites runs as a background job in steps of 10 sites. The app follows its progress with the get_remote_job_status_v1 tool.
You can stop everything. Revoke one connection, disconnect all of yours, or force the connector off with a wp-config.php constant. See Revoke Connections and the Kill Switch.
A changed site address ends every connection. The panel then shows “Your site address changed. Connected AI apps need to reconnect.” A staging copy with a different site address can’t use tokens copied from the live site. A copy that keeps the same site address can’t be told apart from the original.
What the remote connection offers
AI apps get the Dashboard’s tools and a set of prompts adapted from the local MCP server’s prompts. The local server’smainwp:// resources, completions and setup tools aren’t part of the remote connection.
Next steps
Set Up Your AI App
Steps and configuration for Claude, ChatGPT, Cursor, VS Code and the other supported apps.
Approval Policies
Standard, Strict and Hands-off, and the approval page.
Troubleshooting
Every self-test line, the check from the internet, and host-specific help.
Revoke Connections and the Kill Switch
End one connection, all of yours, or turn the connector off from
wp-config.php.