Authorization header but can’t run an OAuth sign-in. AnythingLLM, 5ire, Msty and Roo Code are examples. For them, the Dashboard issues a connection token: one string you paste into the app’s configuration. Jan and LM Studio can use one too.
A connection token is a connection like any other. It belongs to you, it has its own access and approval policy, and it shows up under Connections in the panel, where you can revoke it.
Create a token
1
Open the token form
In MainWP > AI > MainWP MCP > Connect directly, find Connect with a token.
2
Pick the settings
- Name: up to 64 characters, so you can recognize the token later. The connection appears as
Connection token "<name>". - Access: View only (the default) or View and make changes.
- Approval policy: Standard (the default) or Strict. Administrators without Team Control limits can also pick Hands-off. See Approval Policies.
- Expires after: 30 days, 90 days (the default) or 365 days. There is no option for a token that never expires.
3
Create it and copy it
Click Create token. The panel shows the Connection token once, with “Copy the token now. It isn’t shown again.” Below it are the header and a ready configuration for each app that uses tokens, with the token filled in.
4
Paste it into your app
Use the configuration for your app from Set Up Your AI App. For any other app that sends a header, use:Replace
mwpct_... with your token, and send it to your MCP address.Where a token works
A connection token signs in only on the MCP address. On the WordPress Abilities API, the MainWP REST API and admin-ajax it doesn’t sign anyone in, so it can’t replace an Application Password or an API key. A token can do what the connection’s access and approval policy allow, as you, and nothing more. Actions in the Dashboard tier still need your click on the approval page while you’re signed in. A leaked token alone can’t delete or disconnect sites, because those actions wait for that click. Under Hands-off it can, since Hands-off replaces most of those clicks with a confirmation in the chat.Keep the token safe
Many apps store the token in a plain-text configuration file. Anything that copies that file, such as dotfile sync or a backup, copies the token too. To limit the damage if a token leaks:- Give each app its own token and name it after the app.
- Use View only when the app only needs to read.
- Pick the shortest expiry that works for you.
- Revoke a token as soon as you stop using the app.
