Connect your account
- Install the latest desktop update and restart Cowork.
- Open Plugins, select Hosting, and choose your provider and account region.
- Use Connect account for browser sign-in, or save a scoped API token where the provider requires one. Keep passwords and API keys out of chat.
- Ask Cowork to check the connected tools and prepare deployment for your project and existing hosting.
A saved configuration is not proof that account authorization or deployment succeeded. Provider client registration, product access and permissions can affect availability; use the official setup guide if sign-in is unavailable.
Available connections
The desktop library includes 17 hosting connections across Hostinger, Namecheap, GoDaddy, OVHcloud, DigitalOcean, Vultr, Vercel, Netlify, Render, Railway and Cloudflare. Some providers have separate region or service entries.
- Hostinger tools depend on your hosting product and permissions.
- Namecheap covers domains and DNS; it does not provide shared-hosting uploads through this MCP.
- GoDaddy’s public connection searches domains only and needs no credentials.
- OVHcloud has regional beta endpoints. DigitalOcean has Apps, Droplets and Networking connections.
- Vultr’s hosted MCP is read-only by default.
- Cloudflare includes the full API MCP plus Workers Builds and Bindings.
Only connected tools that support your specific project and target can perform a deployment. These entries are not a guarantee that every hosting product or app type supports automatic deployment.
Free Cloudflare hosting, domains and HTTPS
Static websites can fit Cloudflare Pages or Workers Static Assets. Free tiers have build, file and runtime limits; a PHP/Laravel application or arbitrary Docker app cannot simply be uploaded to static hosting.
Cowork’s shared hosting guidance covers domain search, DNS, SSL and verification. A domain search does not reserve a name. Domain registration is paid and requires approval of the exact domain and current price before purchase. No paid server provisioning is included.
DNS changes must preserve your email and unrelated records. An SSL certificate at Cloudflare and encryption to an existing VPS origin are separate checks.
A deployment guide with every completed app
Agent Cowork is instructed to create a project-specific DEPLOYMENT.md. It covers runtime and build commands, environment variables, database setup, persistent files, workers, DNS, HTTPS, checks, updates, backups and recovery.
When a suitable official MCP is unavailable, Cowork provides the guide instead of building a custom hosting connector. It can explain deployment to compatible existing OVHcloud, DigitalOcean or other VPS hosting, and shared hosting where your app fits.
Desktop and Cowork Code receive the same hosting instructions regardless of the selected model. The Plugins sign-in interface is a desktop feature; CLI users need their own supported tool connections or can use the documentation fallback. Instructions do not supply missing credentials, tool support or an independent spending lock.
Try: “Prepare deployment for this app using my existing hosting. Check compatibility first, and write a complete DEPLOYMENT.md. Do not purchase anything.”
Know what actually ran
Cowork should report completed provider operations and verified application checks before calling a deployment live. If it only generated instructions, or DNS and certificate checks are still pending, the result should say so. Review account permissions before granting access.