Use Railway when you want the simplest hosted deployment for Redop’s built-in HTTP transport.Documentation Index
Fetch the complete documentation index at: https://redop.useagents.site/docs/llms.txt
Use this file to discover all available pages before exploring further.
Before you start
This guide assumes:- your server uses
listen({ transport: "http" })or the default HTTP path - the app binds
hostname: "0.0.0.0" - the app reads
PORTfromprocess.env.PORT
create-redop-app --transport http --deploy railway, you already have the right starting shape.
Railway fit
| Item | Value |
|---|---|
| Recommended transport | http |
| Start command | bun run src/index.ts |
| Required env vars | PORT is provided by Railway |
| Extra generated files | none |
| Recommended for | first hosted Redop deployment |
Example src/index.ts
Optional Railway health endpoint
If you want Railway to probe a separate route, opt in explicitly:Deploy steps
- Push your Redop project to GitHub.
- Create a new Railway project from that repository.
- Set the start command to:
- Leave
PORTto Railway. Do not hardcode a different production port. - Deploy the service.
Health checks
Redop does not mount/mcp/health by default. If you want a custom Railway health check endpoint, enable one with health: true or health: { path: "/health" }. Otherwise, verify the MCP endpoint directly.
Verify the deployment
Replace the hostname with your Railway service URL:- HTTP
200 - a JSON-RPC response body
result.serverInfo.namematches your Redop server