Skip to content

Managing OAuth Access in Easy MCP AI ​

When an OAuth-capable AI client connects, WordPress shows an Easy MCP AI consent screen before issuing credentials.

In this article

Choose an access level ​

The consent screen shows the access requested by the AI client. Choose the smallest level that supports what you want the client to do:

  • Read-only allows the client to inspect content and settings without changing them.
  • Match a role is available to approvers with the manage_options capability. Choose an offered site role to cap this connection at that role's capabilities without changing your WordPress account role. Easy MCP AI offers only roles whose granted capabilities are already available to the approver. This cap still cannot exceed the connected WordPress user's actual permissions, requested scopes, or other site restrictions.
  • Full access allows all current and future tools within the connected WordPress user's permissions. It is offered when the client requests full MCP access or supplies no scope. It includes any privileged tool switched on for the site, and the screen shows a notice listing those actions.
  • Custom lets you approve read and write access by category. Select or clear categories to decide which areas the client can use, or use Select all and Clear to change every category at once. Select all never ticks a Privileged row; tick those individually. Clear unticks them. Each privileged tool switched on for the site has its own row, marked Privileged.

When a client explicitly requests specific scopes (permissions), Easy MCP AI caps the grant at those scopes. Choosing Full access cannot widen a request limited to specific permissions.

If a client omits the scope parameter or sends an empty scope, the request does not limit which permissions you can approve. On first authorization, Custom is preselected with the plugin's default permissions ticked. You can select additional permissions, including settings write and WooCommerce write when available. Full access is offered but is not preselected. If you leave the selection unchanged, the grant includes only the selected defaults.

The same behavior applies to device login. Omitting a scope does not automatically grant Full access, enable disabled tools, or bypass the connected WordPress user's permissions or other site restrictions.

Role-matched grants store the selected role instead of a one-time capability snapshot. If that role's capabilities change later, the updated capabilities apply on subsequent requests that use this connection. On multisite, this ceiling still applies even to super admins.

Review each permission row before approving. Privileged rows identify the action each checkbox grants, and the table can show when Read is already included by Write. Permissions unavailable to the connected WordPress user stay unavailable and cannot be approved.

When the AI needs another permission ​

An OAuth client that supports this flow can request an additional permission while you are working. The AI cannot grant itself access; the action that needs the permission is not performed until you review and approve the request.

  1. Follow the client's prompt to open the focused consent screen in WordPress.
  2. Review the permissions marked New. Your existing permissions remain selected, and the newly requested permissions are selected for review. Custom is selected by default; Full access is not automatically selected.
  3. Approve only the additional permissions you want to grant. Return to the AI client and retry the task. If you deny the request, the additional permissions are not granted.

This request works only for an enabled tool that the WordPress user is allowed to use. It does not enable disabled tools or bypass WordPress capabilities or other site restrictions. API tokens do not use this flow, and their access does not change.

If your client does not offer this consent flow, reconnect it through its OAuth setup and request the required access during consent.

Review, edit, or revoke a grant ​

  1. In WordPress, open Easy MCP AI > Connections > OAuth.
  2. Review each grant's WordPress user, client, access level, and activity. A grant that includes privileged tools has + privileged added to its access level, for example Full access + privileged, or reads Privileged only when it includes nothing else.
  3. Click Edit scope to narrow the permissions for a grant (the dialog also has Select all and Clear buttons), or click Revoke to disconnect the client and invalidate its OAuth credentials.

After a site address change ​

OAuth credentials are tied to the MCP resource URL where they were issued. After you change your site's address, grants issued for the previous address are marked in Connections > OAuth and no longer authenticate at the new address.

Use Revoke grants in the site-move notice to remove credentials issued for the previous address. This does not revoke grants issued for the current address.

Each affected AI client must authorize again from the new address. Update the client with the new MCP endpoint, start its OAuth connection, and approve the requested access. Grants issued for the current address continue to work.

Was this helpful?