Slipway
Uses Cloudflare quick-tunnel to expose local previews as public HTTPS URLs for sharing.
Allows deploying apps to Cloudflare Pages hosting.
Enables exporting generated apps to a GitHub repository, with private repos by default and secrets excluded.
Supports sending email through Gmail's SMTP server using an app password and configurable SMTP settings.
Allows deploying apps to Netlify hosting.
Provides a per-app SQLite database with query capabilities for data storage and retrieval.
Allows deploying apps to Vercel hosting.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Slipway Build a habit tracker with streaks, store data, and share a public preview link."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Slipway ⛵
Build and ship real apps directly from Claude or ChatGPT — free, open source, and yours.

40-second demo of an app Claude built through Slipway — dashboard, signup, private per-user notes (mp4 version).
Claude and ChatGPT can already write you an app. Getting it live is another story — git, hosting, databases, email services, push providers: a stack that was never built for you.
Slipway fixes that with one MCP (Model Context Protocol) server. Connect it, and the model you already pay for can scaffold apps, edit code, run live previews, share them at a public URL, store data, send email, send push notifications, deploy to real hosting, and hand you the finished repo. No meter, no credits, no lock-in: Slipway just executes what your model decides, on your machine, into your accounts.
flowchart LR
A["Claude / ChatGPT<br/>(the subscription you already have)"] -- MCP --> B["Slipway<br/>(your machine)"]
B --> C["Apps in ~/.slipway/apps<br/>plain directories — yours"]
B --> D["Live preview<br/>+ public share URL"]
B --> E["SQLite · SMTP email · Web Push"]
B --> F["Deploy: Vercel / Netlify / Cloudflare<br/>+ export to your GitHub"]The 60-second demo
git clone https://github.com/Sandeepbhuiya29/Slipway.git && cd Slipway
npm install && npm run build
claude mcp add slipway -- node "$PWD/dist/index.js"Then tell Claude:
"Build me a habit tracker with streaks. Keep the data in the database, give me a link to try it, and a public link I can open on my phone."
It scaffolds the app, writes the code, starts a preview, opens a share_preview tunnel, and hands you both URLs. Say "ship it" and it deploys; say "give me the repo" and export_app pushes the code to your own GitHub, secrets excluded.
Related MCP server: CreateOS Builder
How it compares
Slipway | Hosted AI app builders | |
Price | Free, MIT-licensed | Their pricing, their terms |
AI usage | Your existing Claude/ChatGPT subscription, any model tier | Depends on their integration |
Where your code lives | Plain directories on your machine + your GitHub | Their platform |
Hosting | Your Vercel/Netlify/Cloudflare accounts (free tiers, your domains) | Their infrastructure |
Database | Built-in SQLite per app, zero setup | Their managed backend |
Email / push | Any SMTP · Web Push with local VAPID keys | Their bundled providers |
Lock-in if the company disappears | None — it's all on your disk | Everything |
Inspect what the AI can do | Read | Closed |
The full tool surface (22 tools)
Capability | Tools |
Apps |
|
Code |
|
Preview |
|
Share |
|
Data |
|
Secrets |
|
Deploy |
|
Own it |
|
| |
Push |
|
Meta |
|
Plus a web dashboard: run node dist/index.js --http 8788 and open http://localhost:8788 — every app with preview/share/deploy buttons and live logs. The saas template ships working signup/login (scrypt-hashed passwords, cookie sessions, per-user data in SQLite) with zero dependencies.
New here? The full walkthrough with copy-paste prompts is in GETTING_STARTED.md.
Connecting
Claude Code
claude mcp add slipway -- node /absolute/path/to/Slipway/dist/index.jsClaude Desktop — add to claude_desktop_config.json:
{
"mcpServers": {
"slipway": { "command": "node", "args": ["/absolute/path/to/Slipway/dist/index.js"] }
}
}ChatGPT, claude.ai on the web, or your phone — run the HTTP transport and tunnel it:
SLIPWAY_TOKEN=some-long-secret node dist/index.js --http 8788
cloudflared tunnel --url http://localhost:8788Point the client's MCP connector at https://<your-tunnel>/mcp with header Authorization: Bearer some-long-secret. ChatGPT accepts remote MCP connectors in developer mode; claude.ai accepts custom connectors.
Where things live
Apps are plain directories in ~/.slipway/apps/<name> (override with SLIPWAY_HOME). Per app:
data.sqlite— the database.env— secrets, injected on preview/deploy, never echoed back through the AI.slipway-push.json— Web Push VAPID keys; the private key never leaves your machine
Nothing is proprietary about the output: every app is ordinary code you can open in an editor, export_app to GitHub, or move anywhere.
Email and push, without the SaaS
Email:
set_envthe five SMTP values (SMTP_HOST,SMTP_PORT,SMTP_USER,SMTP_PASS,MAIL_FROM) — a Gmail app password is enough to start — andsend_emailworks.Push:
push_generate_keysgives your frontend a VAPIDapplicationServerKey;push_senddelivers to any browser subscription. No OneSignal, no accounts.
Security model
Slipway executes code on the machine it runs on — that is the point — so the design is containment:
All file operations are jailed to the workspace; path traversal is rejected.
Secrets are write-only through the AI (
list_envreturns names, never values).delete_apprequires explicit confirmation;export_appdefaults to private repos and gitignores secrets before staging.HTTP mode warns loudly unless
SLIPWAY_TOKENis set. Treat a tunneled Slipway like SSH access, because that's what it is.
Details and reporting: SECURITY.md.
Verified, not vibes
npm run smoke drives the built server over a real MCP stdio session: create → write → preview → fetch the page over HTTP → SQLite roundtrip → env → push keys → teardown. CI runs it on every push, on Linux and macOS, Node 22 and 24.
Roadmap
Postgres behind the same
query_databasetoolMagic-link login (email-based) in the saas template
More templates: Next.js, Expo, Astro
A hosted multi-tenant mode so one Slipway can serve a team
Windows support
Contributions welcome — see CONTRIBUTING.md. Good first issues are listed there.
License
MIT. Slipway is an independent open-source project, not affiliated with Anthropic, OpenAI, or Cloudflare.
Available Tools
22 toolscreate_appCreate appA
Scaffold a new app from a template. Templates: static (Plain HTML/CSS/JS site. Zero dependencies, instant preview.); react (React + Vite single-page app. Run install_dependencies before previewing.); api (Node.js JSON API server. Zero dependencies.); fullstack (Node.js server + static frontend + SQLite database. Zero dependencies.); saas (Fullstack + built-in user accounts: signup/login/sessions (scrypt + SQLite) and per-user data. Zero dependencies.)
Inputs: name (required), template (required).
delete_appDelete appB
Permanently delete an app and its data. Requires confirm=true.
Inputs: app (required), confirm (required).
delete_fileDelete fileC
Delete a file or directory inside an app.
Inputs: app (required), path (required).
deployDeploy appA
Deploy the app. "local" builds and serves it persistently on this machine; "vercel" / "netlify" / "cloudflare" publish to a real public URL via that provider's CLI (free tiers work; custom domains are configured in the provider dashboard).
Inputs: app (required), provider (required).
export_appExport app to GitHubA
Turn an app into the user's own GitHub repository (git init + commit + gh repo create + push). Secrets (.env, keys, databases) are gitignored automatically. Requires the gh CLI, logged in. Ask the user before making a repo public.
Inputs: app (required), repo, visibility.
install_dependenciesInstall dependenciesC
Run npm install in the app directory.
Inputs: app (required).
list_appsList appsA
List all apps in the Slipway workspace, with running preview/deploy URLs.
Inputs: no named parameters.
list_envList env keysB
List the env keys set for an app (keys only, never values).
Inputs: app (required).
list_filesList filesB
List all files in an app (node_modules and .git are skipped).
Inputs: app (required).
preview_logsPreview logsC
Recent stdout/stderr from a running preview — use this to debug.
Inputs: app (required), lines.
push_generate_keysGenerate Web Push keysA
Generate (or return existing) VAPID keys for Web Push. Returns the public key to use with pushManager.subscribe() in the app's frontend; the private key never leaves this machine.
Inputs: app (required).
push_sendSend push notificationB
Send a Web Push notification to a browser subscription (the JSON from PushSubscription.toJSON(), which the app's frontend should send to its backend).
Inputs: app (required), body (required), title (required), subscription (required).
query_databaseQuery databaseA
Run SQL against the app's built-in SQLite database (/data.sqlite). SELECT returns rows as JSON; DDL/DML returns change info. The fullstack template's server uses this same file.
Inputs: app (required), sql (required).
read_fileRead fileC
Read a file from an app.
Inputs: app (required), path (required).
send_emailSend emailB
Send a transactional email via SMTP. Requires SMTP_HOST/SMTP_PORT/SMTP_USER/SMTP_PASS/MAIL_FROM in the app's env (any SMTP provider works).
Inputs: to (required), app (required), subject (required), html, +1 more.
server_statusServer statusA
Show the workspace location and everything currently running.
Inputs: no named parameters.
set_envSet env varA
Set a secret/config value in the app's .env. Injected into the app's process on preview and deploy. Values are never echoed back.
Inputs: app (required), key (required), value (required).
start_previewStart previewB
Start a live dev preview of the app and return its URL. Give the URL to the user.
Inputs: app (required).
stop_previewStop previewB
Stop a running preview (and its public tunnel, if shared).
Inputs: app (required).
undeployUndeploy appB
Take down a local deploy (it will no longer restart with the server).
Inputs: app (required).
write_fileWrite fileB
Create or overwrite a file in an app. Parent directories are created automatically.
Inputs: app (required), path (required), content (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 22 tools
Each tool targets a distinct operation: file management, app lifecycle, preview/deploy, env, database, email, push, and export. Even similar actions like start_preview and share_preview are clearly separated (dev preview vs. public tunnel). No overlap or ambiguity.
All tools use snake_case with a verb-first pattern (delete_file, list_apps, write_file, install_dependencies, push_send). Even compound names like push_generate_keys follow the same style. Naming is predictable and consistent.
22 tools is on the higher end but justifiable for a platform covering app scaffolding, files, previews, deployments, env, DB, email, push, and export. The set is comprehensive without being redundant; each tool serves a distinct purpose in the workflow.
The surface covers the full app lifecycle: create, read, update, delete, deploy, preview, log, env, database, and integrations. Minor gaps exist (e.g., no explicit file-append or update, no list of push subscriptions), but these are non-critical and agents can work around them.
Related MCP Connectors
Build and host working websites from ChatGPT or Claude, with templates and a built-in database.
Deploy apps from Claude Code or Cursor: hosting, Postgres, email, files. Vercel+Supabase in one.
Build, version, review, and export websites, web apps, and games from a conversation.
Build and host full-stack apps from a prompt, with agents that reach you on WhatsApp and email.
Related MCP Servers
- AlicenseBqualityCmaintenanceEnables AI assistants to scaffold, edit, live-preview, and deploy full-stack apps with built-in database, email, and push notification capabilities through natural language.19MIT
- FlicenseNot gradedqualityBmaintenanceEnables users working inside Claude or ChatGPT to build software end to end, executing every command, test, and health check in an isolated cloud sandbox so progress is blocked unless each step is proven by real output, and finishing with a live public preview URL. It also lets sessions checkpoint and restore risky fixes, with access unlocked by a Stripe Checkout purchase.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to build and deploy an app from a GitHub repository to a managed live server and then operate it — logs, captured errors, health checks, managed Postgres, secrets, custom domains, email authentication, and Stripe checkout links. It also exposes safe, read/write-labelled tools so agents can rebuild, start/stop, and inspect projects without ever editing source code.MIT
- AlicenseNot gradedqualityDmaintenanceEnables deploying and managing projects across AWS, Google Cloud, Azure, DigitalOcean, Hetzner, and Vercel directly from Claude Code, with tools for instance lifecycle, domains, environment variables, backend services, databases, webhooks, and GitHub integration.88 npm3MIT