Skip to main content
Each app below connects to your Dashboard’s MCP address. Before you start, turn on remote AI connections and run the self-test, as described in the overview. The examples on this page use https://your-dashboard.com. The Connect an app section of MainWP > AI > MainWP MCP > Connect directly shows the same configurations with your Dashboard’s real address, so copy from there when you can.
App menus and settings screens change between versions. The configuration shown for each app comes from the Dashboard; if a menu label in the app differs from the one named here, look for the app’s custom connector or MCP server settings.

How each app signs in

Jan and LM Studio can also use a connection token. Sign-in details the Dashboard ships. Claude, Claude Code, ChatGPT, VS Code, Codex CLI, Zed and Goose are known to the Dashboard by their published client IDs. You only add the MCP address. Fixed client IDs. Cursor and Gemini CLI use the client IDs mainwp-cursor and mainwp-gemini-cli, which their configurations below already contain. Each has a switch under Which apps can connect in the panel, on by default. The panel and the consent screen name Cursor as “Cursor, or another program using Cursor’s settings” and Gemini CLI as “Gemini CLI, or another program on your computer using Gemini CLI’s settings”, because any program can use those client IDs. Apps on your computer. Apps that run on your machine can register with the Dashboard on their own, as long as their callback address is on that computer (a loopback callback). This needs Let apps on your own computer connect switched on under Which apps can connect; it is on by default. Registered apps appear under Apps on this computer, marked name not checked, because any program can choose its own name. Their consent screen says the same. Turning the switch off stops new registrations. Apps that already registered keep working until you Remove them under Apps on this computer. Signing in. After you add the configuration, the app opens your Dashboard in a browser. Sign in if WordPress asks, review the consent screen, and click Approve. See what the consent screen shows.

Hosted chat apps

Claude

For claude.ai custom connectors. The Dashboard shows:
1

Add a custom connector

In Claude, open the connector settings and add a custom connector. Enter MainWP as the name and paste the MCP address as the URL.
2

Connect

Click to connect. Claude opens your Dashboard’s consent screen, which names the app Claude (claude.ai). Approve it.
Claude puts the approval link for Dashboard-tier actions in the chat. Open it, approve, then ask Claude to try again.

Claude Desktop

Claude Desktop uses the same custom connectors as claude.ai and the same configuration:
Add the connector the same way as for Claude. The consent screen names it Claude (claude.ai) too.

ChatGPT

1

Add the connector

In ChatGPT, open Plugins, select + > Add custom MCP server, and enter MainWP with the MCP address and OAuth authentication. Review the server’s risk warning before creating the plugin. Your account and workspace must allow custom MCP servers; follow OpenAI’s current setup and workspace-permission instructions.
2

Connect

ChatGPT opens your Dashboard’s consent screen, which names the app ChatGPT (chatgpt.com). Approve it.
3

Install and use the plugin

Install the resulting MainWP plugin. Start a new conversation, type @ in the prompt box, and select MainWP.
Custom MCP availability and write tools depend on your ChatGPT plan and workspace policies. The current Plugins flow does not require Developer Mode; older interfaces may differ. Check OpenAI’s linked instructions if the setup controls are missing. ChatGPT keeps its own copy of the tool list. The Dashboard always lists the write tools, even on a view-only connection, so they are in that copy when you later allow changes. If you change which tools are switched on in the panel, refresh the connector in ChatGPT so its copy matches.

Coding tools and command-line apps

Claude Code

Run this in a terminal:
Then start Claude Code, run /mcp, select mainwp and sign in. The consent screen names the app Claude Code (claude.ai). For Dashboard-tier actions, Claude Code asks you to open the approval link itself.

VS Code

Add this to your MCP configuration file, either the workspace MCP configuration or your user configuration:
Start the server from VS Code. VS Code asks you to sign in and opens the consent screen, which names the app VS Code (vscode.dev). Like Claude Code, VS Code asks you to open the approval link for Dashboard-tier actions.

Codex CLI

Add this to Codex’s config.toml MCP configuration:
Then sign in with codex mcp login mainwp. The consent screen names the app Codex CLI (chatgpt.com).

Zed

Add this to Zed’s settings.json:
Zed opens the consent screen when it first connects. It names the app Zed (zed.dev).

Goose

Add this extension to Goose’s config.yaml:
Goose opens the consent screen when it starts the extension. Goose picks a new callback port each time, and the Dashboard accepts that for Goose’s local callback address.

Cursor

Add this to Cursor’s mcp.json configuration:
Then connect the mainwp server from Cursor’s MCP settings. The mainwp-cursor client ID works with Cursor’s desktop and cloud-agent callbacks. It needs the Cursor switch (mainwp-cursor) on under Which apps can connect.

Gemini CLI

Add this to Gemini CLI’s settings.json configuration:
Then run /mcp auth mainwp in Gemini CLI. The client ID accepts Gemini CLI’s loopback OAuth callbacks and needs the Gemini CLI switch (mainwp-gemini-cli) on under Which apps can connect.

Qwen Code

Add this to Qwen Code’s settings.json:
Qwen Code registers itself as an app on your computer, then opens the consent screen.

Cline

Add this to Cline’s MCP settings file:
Cline registers itself as an app on your computer, then opens the consent screen.

Continue

Add this to Continue’s config.yaml:
Continue registers itself as an app on your computer, then opens the consent screen.

Desktop chat apps

Cherry Studio

Add an MCP server in Cherry Studio’s settings with these values:
Cherry Studio registers itself as an app on your computer, then opens the consent screen.

Jan

Add this MCP server in Jan:
Jan registers itself as an app on your computer, then opens the consent screen. If you prefer pasting a token, create a connection token and use the header configuration the panel shows with the token:

LM Studio

Add this to LM Studio’s mcp.json:
If LM Studio signs in with OAuth, it registers itself as an app on your computer and opens the consent screen. Otherwise, create a connection token and use the configuration with a header:

Apps that only run local servers

mcp-remote

mcp-remote lets an app that only starts local (stdio) MCP servers reach a remote one. It needs Node.js. The Dashboard shows this command:
In an app that takes an mcpServers command, the same command looks like this:
mcp-remote registers itself as an app on your computer and opens the consent screen in your browser.

Web apps

Open WebUI

Open WebUI is a multi-user web app that returns to its own HTTPS address after sign-in. Because that address is on the internet, an administrator has to add it first.
1

Add the web app (administrators without Team Control limits)

In MainWP > AI > MainWP MCP > Connect directly, find Web apps. Enter an App name and the redirect URI your Open WebUI instance uses for MCP sign-in under Redirect URIs, one per line (up to 3). Click Add web app.Each redirect URI must be an exact https:// address with no query string, fragment, wildcards, @, %, backslashes or spaces. Otherwise the panel shows “Each redirect URI must be an exact https:// address with no query strings, fragments, wildcards, @, %, backslashes or spaces.”
2

Copy the client ID and secret

The panel shows the Client ID and the Client secret once, with “Copy the client secret now. It isn’t shown again.”
3

Add the server in Open WebUI

Use these values, filling in the client ID and secret from the previous step:
Click Register Client, then Save. See Open WebUI’s static OAuth setup.
4

Each user connects

Each user opens a chat, selects + > Tools, enables the MainWP tool, and signs in to the Dashboard to approve their own connection. The consent screen names the app with the administrator who added it, for example “Open WebUI, added by Jane Admin on October 1, 2026. You’ll return to chat.example.com.”
Under Web apps, each app has a switch, Reissue secret and Delete. Switching it off, reissuing the secret or deleting it ends every connection through that app. Turning the connector off and on, or Disconnect all AI apps, also ends the connections, but the app and its secret keep working for new sign-ins. Administrators without Team Control limits see a notice in the panel whenever a web app is added, switched, deleted or gets a new secret.

Apps that use a connection token

These apps send a header but can’t sign in with OAuth. Create a connection token first; the panel then shows each configuration with your token filled in. The examples use the placeholder mwpct_....

AnythingLLM

5ire

Msty

Roo Code

Allow changes later

If you connected with View only and the app tries a change, it gets a refusal:
  • Claude, Claude Code and VS Code get a sign-in request for more access. Claude and VS Code ask you to sign in again. Claude Code tells you to run /mcp and sign in again.
  • ChatGPT gets “This connection can only view. Reconnect and allow changes.”
  • Other apps get “Reconnect with changes allowed.”
  • Connection tokens get “This token can only view. Create a token with changes allowed in AI > MainWP MCP > Connect directly.”
When you reconnect, pick View and make changes on the consent screen. To go the other way, use Change to view only on the connection in the panel; that takes effect on the app’s next request.

If an app can’t connect

  • “MainWP doesn’t support this app yet”: the app isn’t one of the apps on this page, or its switch under Which apps can connect is off. If Let apps on your own computer connect is off, an app that registers itself can’t register at all, and it reports a “not found” error from the Dashboard.
  • “This app needs to be added again”: the app’s registration was removed. Remove MainWP from the app and add it again.
  • “This app can’t connect right now” after an app changed its callback addresses: updating MainWP Dashboard may fix it, because the Dashboard ships each known app’s addresses.
  • “Sign in first” or “You can’t connect apps”: sign in to the Dashboard with an administrator account, then start again from the app.
  • The app never reaches the Dashboard: ten minutes after you approve, the panel shows a line such as “Claude hasn’t reached this Dashboard yet.” Follow its What to check on your host link or see Troubleshooting.
If your app still can’t connect, the local MCP server works with most of these apps through an Application Password.