How does it work?
Plesk servers added to the WebPros Dashboard can be managed by AI assistants such as Claude, ChatGPT or Gemini through MCP (Model Context Protocol). There are two ways to connect:
-
Option 1: MCP key. For administrators. A key created in the WebPros Dashboard gives the AI assistant access to all Plesk servers added to the Dashboard account. Works with any MCP client.
Note: The Plesk server must be added to the WebPros Dashboard first. An MCP key only reaches servers already added to a Dashboard account.
- Option 2: WebPros Account sign-in (Plesk 18.0.81 and later). For Plesk users (administrator, reseller or customer). No key is needed: the user links a WebPros Account in the Plesk profile, and the assistant acts as that Plesk user, limited to what the user's account and the respective Plesk API allow. It does not give access to the WebPros Dashboard or other servers. Currently works with Claude Code only.
Before you start
- A WebPros account is required. Sign in or create one at dashboard.webpros.com.
- The Plesk server must accept incoming connections on port 8443 from the following IP addresses:
- 52.51.23.204
- 52.213.169.7
- 34.254.37.129
- Log in to the WebPros Dashboard and add the Plesk server if it is not added yet.
- Go to Profile > MCP, press Add > Create MCP Key, enter a name, choose the Scope and press Create.
- Copy the key and add it to your assistant, replacing
WEBPROS_MCP_KEY:
Claude Desktop (requires Node.js): go to Settings > Developer > Edit Config, add the following to claude_desktop_config.json, then fully quit and reopen Claude Desktop.
CONFIG_TEXT: {
"mcpServers": {
"webpros-dashboard": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.webpros.com/api/mcp", "--header", "Authorization:${AUTH_HEADER}"],
"env": { "AUTH_HEADER": "Bearer WEBPROS_MCP_KEY" }
}
}
}
Claude Code: run the following command, then type /mcp in Claude Code to confirm.
# claude mcp add --transport http webpros-dashboard https://mcp.webpros.com/api/mcp --header "Authorization: Bearer WEBPROS_MCP_KEY"
ChatGPT desktop app: it shares its MCP configuration with Codex. Add the following to ~/.codex/config.toml (Windows: %USERPROFILE%\.codex\config.toml), then fully quit and reopen the app.
The server appears in Settings > MCP servers.
CONFIG_TEXT: [mcp_servers.webpros-dashboard]
url = "https://mcp.webpros.com/api/mcp"
http_headers = { "Authorization" = "Bearer WEBPROS_MCP_KEY" }
Note: ChatGPT web (chatgpt.com) connectors support only OAuth or no authentication, so an MCP key cannot be used there.
Codex CLI, the Codex IDE extension and the ChatGPT desktop app share the same configuration. Add the server with the CLI:
# export WEBPROS_MCP_KEY="your_key_here"
# codex mcp add webpros-dashboard --url https://mcp.webpros.com/api/mcp --bearer-token-env-var WEBPROS_MCP_KEY
Or add the same block as in the ChatGPT tab to ~/.codex/config.toml. Type /mcp in Codex to confirm.
Run the following command, then type /mcp in Gemini CLI to confirm:
# gemini mcp add --scope user --transport http --header "Authorization: Bearer WEBPROS_MCP_KEY" webpros-dashboard https://mcp.webpros.com/api/mcp
Any client that supports remote HTTP MCP servers with custom headers can use the URL https://mcp.webpros.com/api/mcp and the header Authorization: Bearer WEBPROS_MCP_KEY.
Some examples:
Visual Studio Code: add to .vscode/mcp.json (project) or the user mcp.json, then click Start above the server name.
CONFIG_TEXT: {
"servers": {
"webpros-dashboard": {
"type": "http",
"url": "https://mcp.webpros.com/api/mcp",
"headers": { "Authorization": "Bearer WEBPROS_MCP_KEY" }
}
}
}
Cursor: add to ~/.cursor/mcp.json or .cursor/mcp.json:
CONFIG_TEXT: {
"mcpServers": {
"webpros-dashboard": {
"url": "https://mcp.webpros.com/api/mcp",
"headers": { "Authorization": "Bearer WEBPROS_MCP_KEY" }
}
}
}
GitHub Copilot CLI:
# copilot mcp add --transport http --header "Authorization: Bearer WEBPROS_MCP_KEY" webpros-dashboard https://mcp.webpros.com/api/mcp
1. Enable it on the server. Add the following to panel.ini. The mcp.enabledTypes line is optional and limits which account types can use it. For resellers and customers, the service plan must also allow REST API access.
CONFIG_TEXT: [webProsAccount]
enabled = 1
mcp.enabled = 1
mcp.enabledTypes = admin,reseller,client,adminAlias
2. Connect Claude Code.
- In Plesk, open your user profile, click Link in the WebPros Account section and sign in.
-
Click Connect next to MCP Connection and copy the Connection Command. It contains no secret and looks like this:
# claude mcp add --transport http webpros-mcp <MCP_ENDPOINT> --client-id <CLIENT_ID> --callback-port <CALLBACK_PORT>
- Run the command where Claude Code is installed, start Claude Code and type
/mcp. - Sign in with the linked WebPros Account in the browser window that opens, then confirm the connection in Claude Code.
More details: MCP in Plesk
Comments
Please sign in to leave a comment.