Run a cloud MCP server

Many servers need a key or a setting of their own, such as an access token for the service they talk to. The form asks for exactly those. Values are stored encrypted and delivered only to the machine that runs the server. Nobody can read them back, your agents included.

Put the server on a machine you already have, or order a new one. Pick the region, shared or dedicated CPU, the architecture and the size, then give the server its share of the machine's memory. Several servers can share one machine, and so can hosted agents.

The console shows the server coming up: the machine starts, the server installs and starts, and it turns ready once it answers MCP. Ready means the server actually works, not just that something started. If it fails, the console says why.

Each machine has its own page with its health, the servers on it, how its memory is split between them, and CPU, memory, disk and network use from the last hour to the last week.

Keep data that matters elsewhere. If a machine fails, Meandr replaces it and the server comes back with its settings and secrets. Files the server wrote to the machine's disk do not come back, so keep anything you need in a database or storage service.

The server now sits in your servers like any other. Add it to a workspace and pick which of its tools the workspace offers. Every agent connected to that workspace gets them, under the workspace's policies, approvals and audit log.

Not in the directory? Write a Dockerfile in the console, or start from the one Meandr generates for a registry server, and change what you need. Meandr builds the image and runs it on the machine you choose, the same way as above.