Docs > MCP Guides > Connect Webdock MCP to Claude

Connect Webdock MCP to Claude

Last updated September 7, 2026

mcp Become an author

Introduction

This guide shows how to connect Claude to Webdock using Webdock’s remote MCP server.

Webdock MCP URL: https://mcp.webdock.io

Webdock uses OAuth, so Claude can authenticate to your Webdock account without you pasting a Webdock password or general-purpose API token into Claude.

Supported Claude clients

Anthropic currently supports remote custom MCP connectors across Claude web, Claude Desktop and other Claude surfaces. Availability and administration differ by Claude plan.

For individual plans, you can normally add your own custom connector. On Team and Enterprise plans, an Owner or Primary Owner may need to add the connector to the organization first, after which individual users connect their own Webdock account.

The exact Claude menus can change, so treat the labels below as a guide rather than a permanent UI contract.

Add Webdock as a custom connector

For an individual Claude account:

Open Customize → Connectors.
Click + and choose Add custom connector.
Give it a name such as: Webdock
Enter the remote MCP URL: https://mcp.webdock.io
You should not need to supply a fixed OAuth client ID or secret; Webdock supports the normal OAuth flow used by compatible MCP clients.
Add the connector.
Click Connect.
Sign in to Webdock in the browser window that opens.
Review the Webdock permissions and approve the access you want Claude to have.

For Team or Enterprise, an organization Owner may first need to add the custom connector under the organization’s connector settings. Each user then connects their own Webdock account.

Enable Webdock in a conversation

After the connector is installed and authenticated:

Start a Claude conversation.
Open the + menu near the message box.
Open Connectors.
Enable Webdock for the conversation.

If you use many connectors, Claude’s connector tool-access controls can affect how eagerly tools are loaded. The default automatic mode is a good starting point.

Test the connection

Start with something read-only:

Use Webdock to show me the available server locations and the cheapest few server profiles. Do not create anything.

Then try:

Show me my Webdock servers and summarize their current state. Do not make changes.

If Claude can discover and call the relevant Webdock tools, the connection is working.

Recommended prompting style

Claude is capable of multi-step infrastructure work, but it will still make planning decisions based on how you phrase the goal.

Be explicit when a managed Webdock feature matters.

For example:

Create an inexpensive WordPress server in Denmark using Webdock’s managed WordPress tooling. First inspect profile capabilities and choose the cheapest compatible profile. Show me the monthly price before provisioning.

That is clearer than simply asking for “the cheapest WordPress server,” which could reasonably be interpreted as permission to choose a cheaper raw VPS and install WordPress manually.

Prefer Webdock-managed operations when you want them

If your goal is to use Webdock’s native management functionality, say so:

Prefer Webdock MCP/API operations over manual shell workarounds when a native Webdock operation exists. If a prerequisite is not met, stop and explain my options.

This is particularly useful for workflows such as managed WordPress.

Use LAMP/LEMP intentionally

If your application needs PHP and a traditional web stack, tell Claude to consider Webdock’s ready LAMP or LEMP images.

Example:

Create a PHP application server using Webdock’s LEMP image. I want Nginx, PHP and database components available from the start rather than assembling the stack manually on a bare OS image.

Ask Claude to snapshot before risky changes

For existing servers:

Before making major package, PHP, web-server or database configuration changes, create a snapshot and wait for it to complete. Then make the change and verify the application afterward.

Snapshots are useful recovery points, although they should not replace a normal backup strategy.

Ask Claude to wait for operations to finish

Some Webdock actions are asynchronous.

For complex tasks, add:

Wait for each Webdock operation to reach a successful terminal state before starting a dependent operation.

This reduces the risk of Claude racing ahead while provisioning, snapshotting or another operation is still in progress.

Use a capable Claude model

For real infrastructure work, use a capable Claude model rather than optimizing for the lightest model available.

In Webdock’s testing, a lightweight Haiku variant performed poorly on multi-step infrastructure tasks and made tool/planning mistakes that stronger models avoided.

Smaller models can be useful for simple read-only questions. For provisioning, reconfiguration and troubleshooting, use a stronger general-purpose model.

Example prompts

Managed WordPress

Create an inexpensive WordPress server in Denmark using Webdock’s managed WordPress functionality. Choose the cheapest profile where managed WordPress is supported, use an appropriate LEMP image, show me the monthly price, then provision it and install a basic site called “Hello World”.

Safe upgrade

Inspect my-server. Before making any significant changes, create a snapshot and verify it completed. Then upgrade the PHP application stack, verify the site is healthy, and summarize what changed.

Read-only audit

Review my Webdock servers and tell me which ones deserve attention. Do not modify anything.

Troubleshooting

If Webdock tools do not appear:

check that Webdock is enabled for the current conversation;
reconnect the connector under Claude’s connector settings;
confirm you completed the Webdock OAuth flow;
review the permissions you approved;
if you are on a managed Claude organization, ask an Owner to confirm that the custom connector is enabled.

If a tool is available but Claude receives a permission error, reconnect the Webdock connector and approve the additional Webdock permission required for the task.