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.

Vercel is not a drop-in production target for Redop’s current built-in HTTP transport.

​
Why this is a caveat

Redop’s built-in HTTP transport is a long-running Bun server. Vercel is a function-oriented platform, so the default Redop server shape does not map cleanly to it the way Railway or Fly.io does.

​
Current posture

ItemValue
Recommended for built-in Redop HTTP transportno
Recommended transportno default recommendation for the built-in HTTP server
create-redop-app presetstarting point only
Generated filesvercel.json
Required env varsdepends on your custom Vercel path
Better choices todayRailway, Fly.io, Docker
Use Vercel only ifyou are building a custom constrained deployment path

​
Generated vercel.json

This is the exact file create-redop-app --deploy vercel adds today: 
{
  "$schema": "https://openapi.vercel.sh/vercel.json",
  "bunVersion": "1.x"
}

​
What the preset means

If you choose --deploy vercel, the generated files help you start exploring a Vercel-compatible shape, but they do not mean Redop currently ships a first-class Vercel transport. Do not read the preset as “production-ready parity with Railway or Fly.io.” The difference from frameworks like Elysia is that Redop does not yet ship a Vercel-style fetch/function adapter. Its built-in HTTP transport is still a long-running Bun.serve(...) server shape.
We do plan to add a proper Vercel-compatible adapter so this deployment path can become first-class instead of caveat-only.

​
When Vercel can still make sense

Vercel can still be reasonable if:
  • you are intentionally building a custom Fetch-based or function-based adapter
  • you understand the limits of the platform for long-lived MCP HTTP behavior
  • you are optimizing for a broader Vercel deployment environment, not the default Redop hosting model

​
How to validate a custom Vercel path

If you do build a custom Vercel adapter, validate it the same way you would validate any MCP HTTP deployment: 
curl -X POST https://your-app.vercel.app/mcp \
  -H 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":0,"method":"initialize","params":{"protocolVersion":"2025-11-25","capabilities":{},"clientInfo":{"name":"vercel-check","version":"1.0.0"}}}'
What success looks like:
  • the request reaches your custom handler
  • /mcp returns a valid JSON-RPC initialize response
  • you are not relying on the default long-running Redop HTTP transport shape
If you want the built-in Redop HTTP transport today:

​
Next