Connect Manus to WordPress over MCP
Point Manus at your site's MCP endpoint as a scoped user. Connect once, then it can call only the abilities you switched on, and every call is checked and logged.
Set it up in four steps
Manus is a hosted web app, so it connects by adding your endpoint as a custom connector and approving once over OAuth. You do not need a config file or an application password.
Manus specifics: In Manus, add your site as a custom MCP connector using your MCP endpoint URL, and approve it once over OAuth. No local bridge to install and no Application Password to copy.
Turn on what you want
Open the Agent Abilities for MCP screen and enable only the abilities you want the agent to have. Everything starts off.
Copy your endpoint
On the Connection tab, copy your site’s MCP endpoint.
Add it as a custom connector
In your app’s connector settings, add your site as a custom connector using that endpoint URL, then approve the connection once over OAuth in the browser. Approve while logged in as the account you want the agent to be. The connection takes that account’s capabilities, so approving as an administrator gives the agent administrator reach.
Check the connection
Use the connection check on the Connection tab to confirm the endpoint is reachable, then run a call from your client.
Connect over OAuth. Least privilege.
Manus authenticates as a real WordPress user, never an admin-equivalent key, and it takes that account’s capabilities. Approve while logged in as the account you want the agent to be.
Approve once in the browser
Approve the agent once in the browser, while logged in as the account you want the agent to be, because it takes that account’s capabilities. There is no secret to store.

Where to get your real endpoint and token: open Agent Abilities for MCP in wp-admin, go to the Connection tab, and copy the endpoint there. The same screen builds the client config for you and runs a connection check so you can confirm the endpoint is reachable before you connect Manus.
If the connection will not start
A few common snags and their fixes. These apply to MCP setup generally, not just Manus.
OAuth discovery returns 403 or 404
Some servers deny anything that starts with a dot before PHP runs, which blocks the /.well-known/ documents MCP clients need. On nginx, add a location block so /.well-known/ falls through to WordPress.
Once Manus is connected
Decide what it can reach, then check the details.
Choose which abilities to expose
All 153 governed abilities, each off until you switch it on. Enable only what Manus needs.
Browse the catalogConnecting a client, in full
The full reference for both routes in: OAuth in the browser, or an Application Password on a scoped user.
Read the connection docsHow a WordPress MCP server works
What your site exposes over MCP, and how governance sits in front of every call Manus makes.
See the server modelOther clients
Governed by default, from the first call.
Install the plugin, connect Manus as a scoped user, and enable one ability at a time. Requires WordPress 6.9+ and PHP 7.4+. Free on WordPress.org, no paid tier, no API key to buy, no usage limits.
Governed from the first call. Nothing leaves your site without you.