MCP (Model Context Protocol) is a standard that lets AI agents and LLM-based tools, such as Claude Code or GitHub® Copilot, discover and use the management capabilities of Plesk®. Once you connect an agent, you can hand it real management work instead of performing it step by step. For example, you can provision a subscription, diagnose a mail delivery issue, trace the cause of a 500 error, or hand off a bug fix on a website straight to an AI coding agent.

Plesk exposes its management capabilities over MCP through the WebPros Dashboard. There is no separate Plesk MCP server to install. Any Plesk server you add to the WebPros Dashboard becomes reachable over MCP through it, at https://mcp.webpros.com/api/mcp. Plesk supports two ways to connect to it:

  • You issue a WebPros Dashboard MCP key and use it as a bearer token, for fleet-wide management.

  • An individual user on your server connects their own MCP client by signing in with a WebPros Account. There is no key or credential to copy, paste, or store.

This topic covers setting up both. See the equivalent topic in the Reseller’s Guide or Customer’s Guide if you want to see what your users go through, or if you manage a reseller’s or customer’s account yourself.

How admin and user access differ

Admin scenario

User scenario

Who connects

The server administrator

An individual Plesk user, for their own account

Connects by

Creating an MCP key in the WebPros Dashboard and using it as a bearer token

Signing in with a WebPros Account linked to their Plesk user; no token to manage

What the AI agent can reach

Every subscription on every server you add to the Dashboard account: an entire fleet through one connection

Only what the linked Plesk user’s own account allows, through that Plesk extension’s end-customer API

Typical use

Fleet-wide operations: provisioning, monitoring, and bulk troubleshooting across servers

Managing the user’s own website or subscription: deploying apps, checking mail delivery, and fixing errors

Both scenarios reach the same MCP endpoint and share the same access controls, described below.

Access controls you can set

An AI agent that manages a server needs the same kind of oversight as any other privileged integration. MCP support in Plesk includes the following controls:

  • Scope. You can scope a WebPros Dashboard MCP key to a single subscription or to full server administration. Signing in with a WebPros Account automatically takes its scope from the linked Plesk user’s own account; it can’t exceed what that user’s account type allows.

  • Per-tool read-only or read-write access. You can enable or disable individual MCP tools, and set each enabled tool to read-only or read-write, to control exactly what an agent can see or change.

  • Logging. The WebPros Dashboard records every MCP tool call. To review it, go to Profile > MCP > Logs.

  • Host allowlisting. When a Plesk user links a WebPros Account, Plesk registers that server with the Dashboard. The Dashboard then forwards a user’s access token only to servers Plesk has registered this way, so content an AI agent reads elsewhere cannot redirect it into sending that token to an unrelated host.

Set up admin-level access

Use this scenario when you want a single AI agent connection to reach every subscription and server that your Dashboard account manages. For a walkthrough with screenshots, see How to connect cPanel/Plesk to MCP in WebPros Dashboard?.

An agent you connect this way can act anywhere your administrator account can: provisioning subscriptions, investigating issues, and running maintenance tasks across the fleet. It is limited only by which individual tools you leave enabled and read-write.

To set up admin-level access:

  1. Sign in at dashboard.webpros.com, or create an account.

  2. Add the Plesk server or servers you want to manage to the Dashboard, if you have not already added them.

  3. Go to Profile > MCP, and open the Keys tab.

  4. Click Add, then select Create MCP Key.

  5. Enter a name, set Scope to full server administration, and click Create. For more on naming and scoping conventions, see How to create a WebPros Dashboard MCP key?.

  6. Copy the key and configure it in your MCP-capable client as a bearer token for https://mcp.webpros.com/api/mcp. For example, in Claude Code:

    claude mcp add --transport http webpros-dashboard https://mcp.webpros.com/api/mcp \
  --header "Authorization: Bearer <MCP_KEY>"

    Other MCP-capable clients, including Visual Studio Code, PHPStorm, and GitHub Copilot CLI, accept the same endpoint URL and Authorization: Bearer header in their own configuration format. For examples covering more clients, see How to use WebPros Dashboard MCP?.

  7. Open the Global Tool Availability tab to review which individual MCP tools you have enabled, and set each to read-only or read-write, to match how much you want the agent to do unattended.

Enable self-service MCP access for your users

An individual reseller, customer, or administrator alias account on your server can connect its own MCP client by signing in with a WebPros Account, but only once you turn the feature on. It is off by default.

To enable it, add the following lines to the panel.ini file (/usr/local/psa/admin/conf/panel.ini on Linux, %plesk_dir%\admin\conf\panel.ini on Windows; see Panel.ini Configuration File for more about this file):

[webProsAccount]
enabled = 1
mcp.enabled = 1

By default, once you turn it on, every account type can use it. To limit self-service MCP access to specific account types, add the mcp.enabledTypes setting with a comma-separated list:

[webProsAccount]
mcp.enabledTypes = admin,reseller,client,adminAlias

The accepted values are admin (server administrators and administrator alias accounts), reseller, and client (subscription owners).

For a customer or reseller account, the subscription’s service plan must also allow REST API access. If a customer or reseller can’t complete the setup below even though you have enabled self-service MCP access, check their service plan.

After a user connects, their agent acts as them. It can only do what that user’s account and the relevant Plesk extension’s end-customer API allow. For the step-by-step setup your users follow, see the equivalent topic in the Reseller’s Guide or Customer’s Guide.