Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs-staging.skybridge.tech/llms.txt

Use this file to discover all available pages before exploring further.

You can deploy your Skybridge App as a Node.js server on any compatible infrastructure provider, or to Cloudflare Workers via the nodejs_compat runtime. Below are some easy options closely integrated with Skybridge.

​
Alpic Cloud platform

​
Instant deploy to Alpic

Alpic is a developer-friendly cloud platform for deploying and hosting MCP Apps. It is also the company behind Skybridge :) To deploy your App on Alpic you can:
  1. Create a free account on app.alpic.ai
  2. Deploy your App either by:
    • Pushing your App to Github, and connecting it to Alpic for automatic deployment at each commit.
    • Using the Alpic CLI:
npm run deploy
Once your App is deployed, you will be able to access specific MCP analytics, logs, and test your app remotely in the Alpic Playground. Learn more about deploying to Alpic in the Alpic documentation.

​
Alpic MCP App

Alpic also provides its own MCP App that lets you manage your apps directly from your favorite MCP Client. Connect to the Alpic MCP Server using: 
https://mcp.alpic.ai/mcp

​
Cloudflare Workers

Skybridge runs on Cloudflare Workers via Wrangler and the nodejs_compat runtime. Static assets (your built views) are served by Cloudflare’s edge directly; the worker handles /mcp traffic and any other dynamic routes.

​
Configure

Add a wrangler.jsonc at your project root: 
{
  "name": "your-skybridge-app",
  "main": "dist/server.js",
  "compatibility_date": "2025-09-01",
  "compatibility_flags": ["nodejs_compat"],
  "assets": { "directory": "dist/assets" },
  "define": {
    "process.env.NODE_ENV": "\"production\""
  }
}
Each setting is load-bearing:
  • compatibility_date >= 2025-09-01 + nodejs_compat — enables cloudflare:node’s httpServerHandler, which Skybridge uses to bridge the Express app to the Workers fetch event.
  • assets.directory — points at the views built by skybridge build. Cloudflare serves these at the edge before requests reach your worker.
  • define.process.env.NODE_ENV — forces production mode even under wrangler dev. Without it, wrangler defaults to development locally and Skybridge’s dev tooling (Vite, the devtools server) gets pulled into the worker bundle, where neither runs.

​
Build and deploy

npm run build
npx wrangler deploy

​
Test locally

wrangler dev runs your worker in workerd on your machine — the same runtime as production, not a Node.js fallback: 
npm run build
npx wrangler dev
Skybridge’s local dev server (skybridge dev) and the Cloudflare path are independent. Use skybridge dev for fast iteration on Node with HMR; use wrangler dev to validate the production worker bundle before shipping.

​
Docker

Projects created with the Skybridge scaffolder include a multi-stage Dockerfile so you can self-host on any container platform: 
npm install
docker build -t my-app .
docker run -p 3000:3000 my-app
The package manager is detected from the lockfile (package-lock.json, yarn.lock, or pnpm-lock.yaml). Bun and Deno are not supported yet: you’ll need to adapt the build stage inside the Dockerfile.

​
What’s Next?

Core Concepts

Learn how Skybridge extends the raw APIs with React hooks

API Reference

Browse the complete API documentation