Agents · Updated 10 November 2026 · 7 min read

How to deploy an app you built in Cursor in 2026

Q: Where do I put the MCP config in Cursor?

Use .cursor/mcp.json in the project root for one project, or ~/.cursor/mcp.json in your home directory for all of them. Each server goes under mcpServers with a name and a url.

Add a hosting provider's MCP server to Cursor and the agent can ship the app for you. Setup, permissions and where Eurobase, Vercel, Netlify, Render and Railway run it.

View as Markdown

You deploy from Cursor by adding your host's MCP server to mcp.json, signing in, and asking the agent to ship the project. Where the app ends up depends on the host you connect: Eurobase if it should run on European infrastructure only, Vercel or Netlify for frontend apps on their networks, and Render or Railway if you also want them to create a database for you.

Hosting MCP servers for Cursor at a glance

Platform	How Cursor connects	What the agent can ship	Where apps run
Eurobase	Remote server, OAuth sign-in	Creates a project from your repository, deploys it and follows it until it responds	European infrastructure
Vercel	Remote server, OAuth sign-in	Deploys your files to a new or existing project	Global
Netlify	Remote server, or a local one	Creates, builds and deploys projects	Functions in Ohio by default
Render	Plugin with OAuth, or an API key	Creates web services, static sites, Postgres and Key Value, triggers deploys	Oregon, Ohio, Virginia, Frankfurt, Singapore
Railway	Railway CLI or OAuth	Creates projects, stages changes and deploys them	California, Virginia, Amsterdam, Singapore

Capabilities come from each provider's MCP documentation, read on 10 November 2026.

How Cursor adds an MCP server

Cursor reads MCP servers from two files. Put the server in .cursor/mcp.json inside the project to use it there only, or in ~/.cursor/mcp.json to have it in every project. A hosted server needs just a url entry under mcpServers.

Cursor supports remote servers over Streamable HTTP and SSE, with OAuth sign-in, so you don't need to paste an API token into the file. Some providers are also listed in the Cursor Marketplace, where Add to Cursor installs the server and starts the sign-in.

By default, Cursor asks you to approve each MCP tool call before it runs, and you can open the arguments the agent wants to send. Keep that on for any tool that deploys or changes settings.

What to check before you connect a host

Code in a repository or on disk. Some servers deploy the files Cursor has open, others build from a Git repository. Push your code first if the host needs it.
Scope of access. Prefer a server that lets you pick the projects or workspace the agent may touch.
Secrets. Decide where API keys and database passwords go. You don't want them typed into a chat.
Logs after a failed build. The agent can only fix a broken deploy if it can read the build output.
The region. The agent ships to wherever the platform runs, not where you are.

1. Eurobase

Eurobase runs only on European infrastructure operated by Scaleway, a French provider, and the company is registered in Warsaw, Poland. Its remote MCP server lives at https://api.eurobase.dev/mcp.

To connect, add this to ~/.cursor/mcp.json, then sign in from Cursor's MCP settings:

{ "mcpServers": { "eurobase": { "url": "https://api.eurobase.dev/mcp" } } }

Sign-in opens Eurobase in your browser. You choose which projects the agent sees, the workspaces where it may create projects, and read or write for each permission. Then ask Cursor to deploy the project on Eurobase. The agent creates the project from your repository and follows the first deployment until the site answers at a .eurobase.dev address. If the app needs secrets, the agent gives you their names and you add the values in the project's Secrets yourself.

With write access the agent can also redeploy, promote, roll back, set public variables and publish Functions. It can't delete anything. Revoking access in Connected apps cuts it off on its next request.

Best for: apps from Cursor that should run on European infrastructure at a flat price.
Price: the Free plan works with the MCP server. Paid plans cost €10 or €20 a month + VAT per workspace, with no usage charges today.
What it lacks: preview deployments, managed Postgres, MySQL or Redis, and Dockerfile builds. Cursor uses the same sign-in as Claude Code and Codex, but Eurobase hasn't tested it end to end yet.

Full setup for every client is in AI agents.

2. Vercel

Vercel's official server is at https://mcp.vercel.com and works on all Vercel plans. Vercel publishes an Add to Cursor link, or you add the URL to mcp.json and click the Needs login prompt. Since July 2026 its deploy_to_vercel tool can deploy your files to a new or existing project, and other tools read deployment logs.

Best for: Next.js apps you want on Vercel's network.
What it lacks: a European company. Vercel also warns that the connection grants the AI tool the same access as your Vercel user account.

3. Netlify

Netlify recommends its remote server at https://mcp.netlify.com/mcp and also offers a local package for setups that need it. According to its repository, the server can create, build and deploy projects and manage environment variables.

Best for: sites already hosted on Netlify.
What it lacks: build logs in its deployment card, which Netlify lists as missing from the first version.

4. Render

Render suggests its Cursor plugin, which signs in with OAuth. You can instead put a Render API key in ~/.cursor/mcp.json. After connecting, tell the agent which Render workspace to use.

Best for: an app plus a Postgres database, created in one conversation.
What it lacks: changes beyond deploys and environment variables. Render says to use its dashboard or API to modify or delete other resources.

5. Railway

Railway's hosted server is at https://mcp.railway.com. Connect it through the Railway CLI, which reuses your railway login, or with OAuth. The hosted server creates projects, redeploys, and uses accept-deploy to commit staged changes and deploy them. Railway marks that tool as destructive, so clients that respect the hint ask before running it.

Best for: agents assembling a whole stack, database included.
What it lacks: a European company, and more than one European region.

How to choose

Pick the region first. If users or contracts require Europe, connect a host that runs there.
Check whether your app needs a managed database. Eurobase doesn't offer one, while Render and Railway create them.
Push the code to a repository if your host builds from Git.
Start with read access, watch one deploy, then allow writes.
Keep Cursor's approval prompt on for deploy tools.

Frequently asked questions

Can Cursor deploy my app by itself?

Not without a host. Cursor writes and runs code on your machine. Once you add a hosting provider's MCP server and sign in, the agent can call that provider's deploy tools, and Cursor asks you before each call unless you change the run mode.

Where do I put the MCP config in Cursor?

Use .cursor/mcp.json in the project root for one project, or ~/.cursor/mcp.json in your home directory for all of them. Each server goes under mcpServers with a name and a url.

Do I need an API key to connect a host to Cursor?

Usually not. Eurobase, Vercel and Railway's OAuth option sign you in through the browser. Render also accepts an API key, and Netlify documents a personal access token as a fallback. Keep any token out of your repository.

How do I host a Cursor app in Europe?

Connect a host that runs in Europe. Eurobase runs only on European infrastructure. Render and Railway each have one European region you can choose. See cloud MCP servers compared for the wider list.

Can the agent see my secrets?

That depends on the host. On Eurobase, the agent sets only public variables and never reads or writes secret values. Netlify's server can create secrets, so check what you approve.