Affordable MCP server hosting
A remote MCP server can run on JustRunMy.App when it is packaged as a compatible container application with a network transport supported by its clients. Map its HTTP port for automatic HTTPS, configure authentication in your application, and pay for allocated resources.
A good fit for: Custom tool servers, internal API adapters, and lightweight remote integrations for MCP-capable clients.
Choose a transport that works remotely
A server that communicates only through standard input and output is designed to be launched as a local subprocess. Putting that executable in a container does not by itself create a remote MCP endpoint. Use an HTTP transport supported by both your server SDK and client.
Configure the server to listen on the mapped container interface and port. Publish the HTTPS endpoint in the client configuration, then test discovery and one real tool call. Transport compatibility and client authentication must work together before the integration is usable.
Treat tool access as application access
Keep upstream API credentials in environment variables. Implement the authentication and authorization your clients require; HTTPS encrypts the connection but does not decide who may execute a tool. Validate inputs and return useful errors when a dependency fails.
Separate tools that only read data from operations that change it in your application design. Set timeouts and concurrency limits around expensive calls. Record enough operational information to debug failures without placing credentials or private tool inputs in logs.
Your MCP server and the platform MCP integration
Hosting your own MCP server runs your tools as an application. JustRunMy.App also provides a built-in MCP integration that lets an AI coding assistant manage application deployments. You can use that integration to deploy a project, but it is a different service from the tool server you are hosting.
For your own server, choose Zip, Git, or Docker, include the SDK dependencies, and define the startup command. Add persistent storage if the tools maintain local state. Count any external APIs or databases separately from the container hosting estimate.
Deployment checklist
Confirm client compatibility
Choose the remote transport and authentication flow supported by your server implementation and intended client.
Package and deploy the server
Include runtime dependencies and a startup command, then deploy with Zip, Git, or Docker.
Configure HTTPS and access
Map the listening port, set environment variables, and enable application-level authentication before connecting clients.
Test a complete tool call
Verify tool discovery, access checks, and a real response. Check logs and limits before enabling expensive tools.
Example resource allocations
Monthly USD rates: $1.90 per vCPU, $1.95 per GB RAM, and $0.25 per GB disk. All allocated resources are billed per minute across applications, including idle allocations.
Size for the tools the server executes, not just the protocol handler. Database queries, browser tools, local indexing, and additional services can have very different resource needs.
| Example | vCPU | RAM (GB) | Disk | Monthly estimate |
|---|---|---|---|---|
| Minimal allocation example | 0.15 | 0.15 | 0 GB | $0.58 |
| Lightweight worker example | 0.25 | 0.25 | 0.3 GB | $1.04 |
| More memory for dependencies | 0.25 | 0.5 | 1 GB | $1.70 |
| Larger worker example | 0.5 | 1 | 1 GB | $3.15 |