Deploy and manage your Webdock servers from your AI
Connect Claude, ChatGPT, Devin or GitHub Copilot to Webdock using MCP.
Deploy, inspect, resize and manage your servers in plain language, without switching to the dashboard.Secure OAuth. Scoped permissions. No password or general-purpose API token to paste. Included with your Webdock account.
https://mcp.webdock.ioHow it works
Stay in the AI client you already use
Step 1
Open your AI client
Claude, ChatGPT, Devin or any MCP-compatible AI client you already use.
Step 2
Connect to Webdock MCP
Approve access through OAuth. No password or general-purpose API token to paste.
Step 3
Start managing your infrastructure
Describe the outcome you want. Your AI picks the right Webdock tools.
Works with your AI client
Use Webdock MCP with Claude, ChatGPT, Devin and GitHub Copilot
Pick your AI client and watch it deploy and manage a Webdock server in plain language.
Claude
ChatGPT
Devin
GitHub Copilot
Add Webdock as a custom connector in Claude on the web or desktop, then sign in to Webdock in your browser.
See the Claude guideREFERENCE
Webdock MCP at a glance
- What it is
- A remote MCP server operated by Webdock.
- Endpoint
- https://mcp.webdock.io
- Transport
- Streamable HTTP over HTTPS (some AI clients label it HTTP)
- Authentication
- OAuth sign-in in your browser. No password or general-purpose API token to paste.
- Permissions
- Chosen by you at sign-in, from read-only to full server management.
- Works with
- Claude, ChatGPT, Devin, GitHub Copilot in VS Code, and other AI clients that support remote MCP servers.
- Setup
- From the Webdock dashboard (Account, then AI and MCP) or manually in your AI client.
- Price
- Included with your Webdock account. You only pay for the servers you run.
- Available since
- September 2026.
THE STANDARD
One connection. No more dashboard switching.
Webdock MCP gives your AI access to the real state of your Webdock account: Servers, profiles, locations, images and supported operations.
What you can do with Webdock MCP
Deploy Servers
Create a new VPS, choose profile and image, in Webdock's own datacenter in Denmark, and deploy it directly from your AI.
Inspect infrastructure
Ask about your servers, configurations, locations, images, account details and current state.
Upgrade or downgrade
Upgrade or downgrade a server and review the new configuration before applying the change.
Create snapshots
Take a snapshot before making risky changes so you have a recovery point.
Diagnose Issues
Inspect server state and metrics before making changes to your infrastructure.
Automate
Execute supported server-side operations and chain multiple steps into a single workflow.
Built to keep you in control
OAuth, not passwords
You don't need to paste a password or a general-purpose API token into your AI client. You sign in to Webdock and approve what it can do.
Scoped permissions
Read-only for audits and troubleshooting. More only when you want changes. Reconnect any time to change what it's allowed to do.
Waits for real results
Some Webdock operations run in the background. Ask your AI to wait for each one to finish before starting the next.
Snapshot first
Ask for a snapshot before big changes. It's a safety net alongside your normal backups, not a replacement for them.
Try it yourself
Tell your AI what you want. Let it handle the Webdock tools.
"Show me all my Webdock servers and their current status."
"Create a snapshot of my production server before we make changes."
"Set up a new WordPress server using Webdock's managed WordPress functionality."
"Upgrade my staging server to a bigger profile. Show me the new monthly price before you change anything."
SETUP
Connect in a few steps
Fastest route: set it up from your Webdock dashboard. Or connect manually:
- 01
In your MCP client, add a new custom or remote server.
- 02
Choose HTTP or Streamable HTTP if asked for a transport.
- 03
Enter https://mcp.webdock.io
https://mcp.webdock.io - 04
Choose OAuth if asked for an authentication method. Most AI clients detect it automatically.
- 05
Sign in to Webdock in the browser window that opens and approve the permissions you want to grant.
- 06
Return to your AI chat and confirm the Webdock tools are available.
Full guides at docs.webdock.io/mcp-guides
Know the difference
AI across the Webdock platform
AI Assistant
Answers your questions inside the Webdock panel. It never touches your account.
AI AssistantAI Agent hosting
Deploy autonomous agents on Webdock infrastructure and keep them running 24/7.
AI Agent hostingWebdock MCP
Let your AI manage your entire infrastructure
FAQ
Webdock MCP questions
Everything you need to know about connecting your AI client to Webdock.
Webdock MCP is a remote MCP server operated by Webdock at https://mcp.webdock.io. MCP (Model Context Protocol) is an open standard that lets an AI client use external tools in a consistent way. With Webdock MCP, Claude, ChatGPT and other AI clients can deploy and manage servers on your Webdock account in plain language.
No. Webdock MCP is included with your Webdock account. You only pay for the servers you run, at normal Webdock prices.
Claude, ChatGPT, Devin and GitHub Copilot in VS Code, each with its own setup guide. Any other AI client that supports remote MCP servers can connect using the guide for other clients.
No. Webdock runs the MCP server, so there is nothing to install. Add https://mcp.webdock.io in your AI client, sign in once, and work entirely from the chat. The dashboard setup page (Account, then AI and MCP) is an optional shortcut.
You sign in to Webdock through OAuth in your browser, so you don't need to paste a password or a general-purpose API token into your AI client. Claude does not need a separate OAuth client ID or secret either. You choose the permissions at sign-in, from read-only to full server management. Read-only works well for inventory, audits and troubleshooting. Reconnect at any time and approve a different set of permissions to change them.
Yes, with the right permissions. It can pick a profile and a software image, including Webdock's LAMP and LEMP images, and create the server in Webdock's own datacenter in Denmark (DK-DC1). It reads monthly prices, so you can ask it to confirm the cost before anything billable happens.
Yes. It can manage MySQL databases on your servers and supported WordPress functionality. For Webdock-managed WordPress, ask it to pick the cheapest compatible profile that includes it and to use Webdock's managed tooling instead of a manual install.
With good habits, yes. Ask for a snapshot before major changes, name the exact server it may touch, and ask it to verify the result afterwards. Review anything billable or destructive before approving it. A snapshot is a recovery point, not a replacement for your backups.
No. The AI Assistant answers questions inside the Webdock panel and never changes anything. Webdock MCP lets your own AI client deploy and manage servers on your account.
Yes. An organization Owner usually adds the Webdock connector first, then each team member connects their own Webdock account.
Check that Webdock is enabled for the current conversation, reconnect it, and confirm you completed the OAuth sign-in and approved the permissions you need. For a permission error in the middle of a task, reconnect and approve the permission that operation needs.