Which Hosting Platforms Have an MCP Server So Claude Can Deploy Your App? (I Checked 5)

You built something with Claude. It works on your machine, or it only exists inside the chat as a pile of files. Now you want a URL you can send to someone.

The question I kept seeing was: which hosting platforms have an MCP server, so Claude can deploy the app for me instead of handing me a list of terminal commands?

I went through the official MCP docs of five platforms in November 2026 and wrote down what each server's tools actually do, as opposed to what the landing page implies.

TL;DR

Short answer: if your app is a backend (an Express API, a Flask app, a Discord bot, anything that has to stay running) and the code lives in the conversation rather than in a GitHub repo, InstaPods is the one built for exactly that. If it's a Next.js frontend you already keep on Vercel, use Vercel's MCP. If you already run your stack on Railway or Render, their servers are good at managing what's already there.

Disclosure: I build InstaPods. I've tried to be straight about where the others are the better pick.

Why "has an MCP server" isn't the real question

Every platform on that list has one now. The thing that actually decides whether Claude can get you a live URL is a narrower question:

Can the server accept your code as files, or does it need a Git repo or a CLI on your laptop first?

That matters because of where people are when they ask. If you're in Claude Code with a project folder, any of these work, since Claude can run the platform's CLI. If you're in claude.ai or Claude Desktop, there is no terminal and no repo. The code exists only in the chat. A server whose deploy path starts with "connect a GitHub repo" or "run railway up" can't finish the job from there.

The second question: what does it run? Vercel and Netlify are built around frontends and serverless functions. That's great for a landing page, and awkward for a websocket server, a scraper on a schedule, or a bot that holds a connection open all day.

What each one does

InstaPods

Full disclosure again: this one is mine.

You add https://app.instapods.com/api/mcp as a connector in Claude (Settings -> Connectors -> Add custom connector), approve it in the browser, and Claude gets 21 tools. The one that matters here is deploy_pod:

• It takes the files directly, up to 50 files / 2 MiB per call, as { path, content }.
• It figures out the runtime from the file names: package.json means Node, requirements.txt or a .py file means Python, composer.json means PHP, go.mod means Go, index.html means static.
• It creates the pod if it doesn't exist, writes the files, installs dependencies, restarts the app, and then checks from outside whether a visitor would actually see it.
• Calling it again with the same name updates the same pod. So "change the button color and redeploy" is one more call, not a second app.

That last check is the part I care about most. A process can be "running" and still not answer on the port the proxy expects, which is the most common way an AI-written deploy fails. The tool returns public: true or public: false with a reason, so Claude can tell you it's broken instead of announcing it's live.

There's also create_pod with an app_type, which deploys a ready-made app from the catalog ("deploy n8n for me", "I need an uptime monitor"). Plus exec_command, get_logs, set_env and read_file, so Claude can debug the thing it just deployed.

Every pod is a real Linux server with SSH, so you're not locked into the chat. Pricing is flat: $3/mo on Launch, $7/mo on Build (which Node and Go default to, since the build step wants the memory). No usage bills. You need a card on file, and the first card added gets a $10 credit.

What it isn't: a CDN-first frontend platform. If you want edge-rendered Next.js with preview deployments per branch, that's Vercel's home turf.

Vercel

Vercel's official MCP lives at https://mcp.vercel.com, remote with OAuth, and works in Claude Code, claude.ai, ChatGPT, Cursor and more. It searches docs, manages projects and deployments, reads deployment logs and queries Web Analytics.

Since July 23, 2026 it also has deploy_to_vercel, which deploys code to a new or existing project "without leaving the chat". For frontend work, this is the strongest option on the list.

The catch is the plan model, not the MCP. Hobby is free but explicitly for "personal, non-commercial use". Pro is $20/mo per member. And long-running backends aren't what Vercel runs.

Railway

Railway runs a remote server at mcp.railway.com (OAuth, or reusing your railway login) and a local one via railway mcp local.

The remote server's tools are project-level: list-projects, create-project, list-services, redeploy, accept-deploy, plus railway-agent for multi-step work. The bigger deploy and deploy_template tools are on the local server, which uses the CLI. So it shines in Claude Code next to a project folder, and is more limited in a plain chat.

Railway is excellent for backends and databases. Hobby is $5/mo with $5 of usage included, and usage beyond that is billed, which is the thing to watch if your agent spins up more than you expected.

Render

Render's official MCP server supports OAuth (Claude Desktop, Claude Code, Codex, Cursor) or an API key. It can create web services, static sites, cron jobs, Postgres and Key Value instances, update env vars, trigger deploys, and read logs and metrics.

Their example creates a web service from a GitHub repository URL, and the docs don't describe uploading local code. Render also says plainly that "the MCP server supports limited changes to existing Render resources" and that you can't create image-backed services through it. Strong for "operate my Render account", weaker for "here are some files, put them online".

Netlify

Netlify has a remote server at mcp.netlify.com/mcp (and a local @netlify/mcp). It can create and manage projects, env vars, forms and extensions, and the docs say agents can "build, deploy" with it. What I couldn't find was how code reaches Netlify from a chat with no filesystem, so I've left that column honest rather than guessing. It's a frontend platform first, like Vercel.

So which one should Claude use?

• The code is in the chat, and it's a backend or a full-stack app: InstaPods. It's the one where "here are the files" is the whole deploy, and it tells you whether the URL works.
• The code is in the chat, and it's a frontend: Vercel's deploy_to_vercel or InstaPods. Vercel if you want their edge network and already pay for Pro, InstaPods if you want $3/mo flat and a server you can SSH into.
• You're in Claude Code and already live on Railway or Render: use their server. Managing infrastructure you already have is exactly what they're good at.
• You want a ready-made tool, not your own code (n8n, Uptime Kuma, a password manager): InstaPods' 1-Click apps, since the app arrives pre-installed and nothing needs uploading.

The old way of putting an AI-built app online was: rent a VPS, install the runtime, configure nginx, set up SSL, open the firewall, add a process manager, then point a domain's DNS at it. MCP doesn't remove the server. It removes you having to babysit it.

What are you deploying from Claude these days, and which of these have you actually had finish the job end to end?