Skip to main content

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.

Redop HTTP is a long-running Bun server. That means the best production fit today is a platform that runs a persistent Bun process, not a purely serverless request model.

​
Choose a platform

PlatformBest forRecommended transportcreate-redop-app presetFit today
RailwayFastest hosted setuphttprailwayRecommended
Fly.ioAlways-on Docker deploymenthttpfly-ioRecommended
DockerSelf-hosting or custom infrahttpfly-io gives you a starting DockerfileRecommended
UnkeyDocker deployment with preview environments, rollbacks, and SentinelhttpnonePrivate beta
VercelCustom constrained setupsnot recommended for the built-in HTTP transportvercelCaveat only

​
Redop hosting model

  • Use http for hosted MCP servers.
  • Bind to 0.0.0.0.
  • Read PORT from the environment.
  • Expose the MCP endpoint at /mcp.
  • Do not assume Redop mounts /mcp/health or /mcp/schema by default.
  • If your platform wants a separate health route, enable one explicitly with health: true or health: { path: "/health" }.
stdio is for local MCP host integrations such as command-based clients. It is not the normal production path for a hosted Redop HTTP server.

​
Quick verification shape

No matter which platform you choose, a healthy Redop deployment should answer an MCP initialize request on /mcp. 
curl -i -X POST http://localhost:3000/mcp \
  -H 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":0,"method":"initialize","params":{"protocolVersion":"2025-11-25","capabilities":{},"clientInfo":{"name":"manual-check","version":"1.0.0"}}}'
You should get a JSON-RPC response with result.protocolVersion, serverInfo, and capabilities. If you keep testing manually after initialize, copy the Mcp-Session-Id response header into later HTTP requests. Redop expects that header on follow-up JSON-RPC calls.
  • Choose Deploy to Railway if you want the shortest path to a hosted Bun service.
  • Choose Deploy to Fly.io if you want Docker-based deployment with an always-on app shape.
  • Choose Deploy with Docker if you want to run Redop on your own infra or in a monorepo.
  • Choose Deploy to Unkey if you already have Unkey Deploy beta access and want Docker-based deploys with preview environments and built-in edge controls.
  • Read Deploy to Vercel only if you specifically need Vercel and understand the built-in transport caveat.