Run hosted MCP servers

MCP hosting platform: pick a server from the Docker MCP catalog or the Official MCP registry, or write your own Dockerfile, and we run it for you. It joins your list like any other server.

From the directory to a server in your catalog

Deploy an MCP server in four steps: pick it, set up the machine it runs on, watch it from one place, or build your own from a Dockerfile.

  1. 01 Pick

    Pick a server from the official list

    Docker MCP hosting starts in the directory: search the Docker MCP catalog and the Official MCP registry by name and pick a server. Each entry shows what it does, how many tools it has and its category.

    • Search by name, no URL to paste
  2. 02 Set up

    Set up the machine, then add more servers to it

    Choose the region, machine type, architecture and size for your MCP cloud hosting, and give the server its share of memory. Next time, add another server to the same machine instead of ordering a new one.

    • Shared machines burst to 100% CPU; dedicated ones keep their CPU to themselves
    • EU and US regions available, more coming
    • A separate process for every connected agent
  3. 03 Monitor

    Watch every machine live, from one place

    Each machine has its own page in the console: its health, the servers running on it and how it is used.

    • Health checks for CPU, memory and disk, updated every minute
    • How the machine's memory is split between the servers on it
    • CPU, memory, disk and network usage, from the last hour to the last week
  4. 04 Build

    Run your own MCP server from a Dockerfile

    Write the Dockerfile in the console, or start from the one Meandr generates for a registry server. Meandr builds the image and runs it on a machine you choose.

    • Meandr builds the image, and you can rebuild it at any time
    • Secrets go in variables and never into the image
    • One built image can run several servers

You pick the server, we take care of the rest

Managed MCP hosting: we run the machine, keep its secrets and put the server behind the same rules as every other one.

We keep the machine running

The server runs on MCP server infrastructure we operate. If the machine fails, it is replaced, and the server comes back with its settings.

Secrets stay safe

The secrets a server needs are stored encrypted and delivered only to the machine that runs it. Nobody can read them back.

Same rules as every server

A hosted server joins your catalog through the same tunnel as a server on your own machine, so your policies, approvals and audit log apply unchanged.

Questions about MCP server hosting

How do I host an MCP server with Meandr?
Pick it in the directory, choose a machine and select Run server; it then sits in your catalog like any remote MCP server.
What does it cost?
You pay per machine, not per MCP server. Several servers can share one machine, and you see the price of each size before you order it.
How many servers can one machine run?
As many as its memory allows. Each server gets its own share of the machine's memory, from 80 MB up, and you decide how it is split.
What happens to files the server writes?
Files last only as long as the machine. A machine can be replaced after a hardware failure, a resize or a failed payment, and anything on its disk goes with it. The server and its settings are kept, so keep data in a service the server connects to.
Does choosing the EU region keep my data in the EU?
The region decides where your server runs. Calls to it go through Meandr like any other call, and their records are stored the same way. Where your data is stored →
Can Meandr run any server in the registry?
Most of them. From the Official MCP registry Meandr runs npm and PyPI packages, and, for Docker MCP server hosting, container images from the Docker MCP catalog as published, with the version pinned when you create the server. Servers that mount a local folder can't run; remote entries connect by URL.
Who can see the secrets I give it?
No one through Meandr. Each secret is stored encrypted in Meandr. When the server starts, the machine's own agent hands it over, only for servers on that machine. It is never written into the machine's or container's configuration and never shown back.
Does this replace connecting my own servers?
No. Your own servers stay exactly as they are, on your machines, your network and your credentials. Hosting is for the ones you would rather not run at all.

Run your first hosted MCP server

Pick it from the directory, choose the machine, and point your agent at one endpoint.

Try for free

Questions? Email us