Introduction

This guide provides steps on how to connect Devin to Webdock MCP (via custom remote MCP server)

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

Use HTTP / Streamable HTTP with OAuth authentication.

Add Webdock to Devin

In Devin:

1. Open the MCP integrations or MCP Marketplace area.
2. Choose Add Your Own for a custom MCP server.
3. Choose HTTP / Streamable HTTP as the transport.
4. Enter: https://mcp.webdock.io
5. Choose OAuth authentication.
6. Save/connect the integration.
7. Follow the authorization link or browser prompt Devin provides.
8. Sign in to Webdock.
9. Review the Webdock permissions and approve the access you want Devin to have.

Devin’s exact integration UI can change. If your organization supports both personal and organization-wide MCP connections, choose the connection scope that matches how the Webdock account should be used.

Important Devin permission quirk

In our testing, Devin does not reliably perform progressive OAuth permission escalation.

That means a session can start with a limited set of Webdock permissions, later discover that it needs another permission, and fail instead of cleanly asking you to authorize the additional scope.

To reduce this problem, Webdock recognizes the Devin OAuth client and pre-selects the available MCP permissions on the Webdock authorization screen.

You can deselect permissions before approving them. However, if you expect Devin to handle broad infrastructure tasks, we recommend leaving the permissions it will need selected from the beginning.

If you deliberately restrict permissions and Devin later fails with an authorization error, reconnect/re-authorize the Webdock MCP integration and grant the missing permission.

Test the integration

Start a Devin session with a read-only task:

Use Webdock MCP to list the available server locations and profiles. Do not create or change anything.

Then:

Show me my Webdock servers and summarize their state. This is read-only.

Give Devin clear infrastructure constraints

Devin is designed to autonomously work through tasks, so good constraints matter.

For example:

I need a small PHP server in Denmark. Prefer Webdock’s LEMP image instead of a bare OS because the application needs Nginx, PHP and a database. Show me the proposed profile and monthly price before provisioning.

For managed WordPress:

Create an inexpensive WordPress server in Denmark using Webdock’s managed WordPress tooling. Filter profiles by wordpressManagementIncluded=true first, then choose the cheapest eligible profile.

Tell Devin when not to improvise

For important infrastructure, consider adding:

Prefer native Webdock MCP operations when they exist. If an operation is unavailable because of permissions, profile capabilities or another prerequisite, stop and explain the options instead of automatically building a shell workaround.

This is especially useful when you want Webdock’s managed functionality rather than a manually maintained equivalent.

Create a snapshot before major changes

Example:

Before changing packages, PHP, Nginx/Apache, database configuration or deploying a large application update, create a Webdock snapshot and wait for it to finish.

For particularly sensitive work:

After the snapshot is complete, explain the risky step and wait for my approval before executing it.

Make Devin wait for asynchronous operations

Many infrastructure workflows depend on one operation completing before the next begins.

Add:

For asynchronous Webdock operations, wait for the exact operation/event to finish successfully and verify the resulting state before proceeding.

Use sufficient reasoning/model capability

Avoid using the lightest possible model configuration for infrastructure operations.

The agent must plan across multiple tools, interpret Webdock preconditions and keep track of asynchronous work. In our testing, lightweight models made materially more infrastructure mistakes than stronger models.

Example Devin prompts

Deploy a PHP app

Prepare a Webdock server in Denmark for this repository. Use a suitable LEMP image, choose a sensible inexpensive profile, show me the monthly cost before provisioning, and do not make a billable change until I approve the proposed configuration.

Managed WordPress

Provision the cheapest Denmark profile compatible with Webdock-managed WordPress, install WordPress, and create a basic “Hello World” site. Do not fall back to a manual WordPress installation if managed WordPress is unavailable; explain the issue instead.

Safe production change

Inspect production-web. Create and verify a snapshot before any major change. Then make the requested configuration update, verify application health, and summarize what changed.

Troubleshooting

If Devin cannot see Webdock tools:

• verify the custom MCP server uses HTTP/Streamable HTTP;
• verify the URL is exactly https://mcp.webdock.io;
• confirm OAuth completed successfully;
• check Devin’s MCP/session logs.

If Devin can see a tool but gets a permission error, re-authorize Webdock and grant the required permission. Because of Devin’s current escalation behavior, reconnecting can be more reliable than waiting for Devin to request a new scope automatically.

Vendor reference

Devin’s current MCP setup guide:

https://docs.devin.ai/work-with-devin/mcp

Please reach out to Webdock Support if you need assistance.