MCP Gateway hosting
Host your Model Context Protocol servers where your agents can always reach them.
MCP Gateway hosting at AIHostBox means a dedicated, single-tenant MCP Gateway instance on our infrastructure: we install it, pin it to a reviewed release, put it behind TLS on your domain, back it up nightly and keep it patched. Plans start at $5.99 per month and the admin account, the data and any API keys are yours.
The Model Context Protocol standardised how assistants reach tools and data, and the ecosystem responded with hundreds of servers. Almost all of them are designed to run on a developer’s machine over stdio — which is fine until the assistant that needs them is a hosted agent, a phone, or a colleague.
An MCP gateway plan gives your servers a permanent home: they run continuously, they are reachable over HTTP with authentication, and several can sit behind one endpoint. Bring the servers you want — filesystem, database, search, your own — and we keep the process, the TLS certificate and the updates in order.
MCP Gateway hosting plans
Every plan is a dedicated single-tenant instance with NVMe storage, nightly off-box backups, TLS and managed patching. Quarterly, semi-annual and annual terms are discounted at checkout. Model tokens are not included — you bring your own key.
How we run MCP Gateway
Each MCP server you choose runs as its own supervised process (Node via npx, Python via uvx, or your own code); stdio servers are bridged to streamable HTTP, and a TLS reverse proxy publishes them under one hostname with a path per server and key authentication.
What we configure for you
- One path per server, for example /github or /postgres, listed for your client configuration
- A gateway access key checked on every request, rotatable whenever you like
- Per-server environment variables for API tokens and connection strings
- Pinned server package versions, upgraded deliberately rather than on every restart
- Process supervision with automatic restart, and logs you can read in the console
Which plan fits
Starter (2 GB, 1 vCPU) runs several lightweight servers such as filesystem, fetch, Git or a database connector. Plus (4 GB, 2 vCPU) suits a team’s shared set of ten or more servers, or ones making heavy API calls. Pro (8 GB, 3 vCPU) is for browser-automation servers or anything that loads data into memory.
The honest limits
Servers built around a local desktop, such as ones that read your laptop’s files or drive a local application, will see the server’s filesystem rather than yours. Some hosted clients expect OAuth rather than a static key, so check your client’s remote-server support first.
What people run MCP Gateway for
Tools for hosted agents
Give a cloud assistant access to your internal tools.
Team-wide tooling
One reviewed set of MCP servers instead of one per laptop.
Your own MCP server
Deploy something you wrote without running your own box.
Licence and version policy
| Item | Position |
|---|---|
| Upstream licence | MIT |
| Sold as managed hosting | Yes |
| Tenancy | Single tenant — one customer per instance |
| Patching | Critical advisories within 24 hours, high severity within 72 |
Our full position on licences, including the applications we decline to sell, is on the licensing page.
Reading on MCP Gateway
Works well with MCP Gateway
MCP Gateway hosting: your questions
Which MCP servers can you host?
How do agents authenticate?
Which transport do clients connect over?
Can you host a server that only speaks stdio?
Where do the credentials my MCP servers need live?
How many MCP servers fit on a plan?
Run MCP Gateway without running a server
A dedicated MCP Gateway instance, deployed and maintained by us. Month to month, cancel whenever.