Skip to main content
Glama

Slipway

Build and ship real apps directly from Claude or ChatGPT — free and open source, using the AI subscription you already pay for.

Slipway is an MCP (Model Context Protocol) server that gives your AI assistant the tools to actually ship software, not just write it: scaffold an app, edit its files, run a live preview you can open in your browser, store data in a built-in database, send email, send push notifications, and deploy to a real public URL.

There is no meter and no credits. The model you already pay for (Claude Pro/Max, ChatGPT Plus, or any MCP-capable client) does the thinking; Slipway just executes. Everything runs on your machine, and deploys go to your accounts on free hosting tiers.

A slipway is the ramp a ship is built on and launched from.

What your assistant can do once connected

Capability

Tools

Replaces

Scaffold apps (static, React+Vite, API, fullstack)

create_app, list_apps, delete_app

boilerplate setup

Edit code

write_file, read_file, list_files, delete_file

copy-pasting from chat

Live preview with logs

start_preview, preview_logs, stop_preview

local dev setup

Database (per-app SQLite, zero config)

query_database

Supabase setup

Secrets / config

set_env, list_env

.env wrangling

Deploy to a public URL

deploy (local, Vercel, Netlify, Cloudflare Pages)

git + CI + hosting setup

Transactional email (any SMTP)

send_email

Resend setup

Web push notifications (VAPID)

push_generate_keys, push_send

OneSignal setup

npm packages

install_dependencies

terminal juggling

Related MCP server: @forgespace/ui-mcp

Quick start

Requires Node.js ≥ 22.5 (the built-in SQLite needs it).

git clone https://github.com/SandeepbhuiyaRTNW/slipway.git
cd slipway
npm install
npm run build
npm run smoke   # optional: end-to-end self-test

Claude Code

claude mcp add slipway -- node /absolute/path/to/slipway/dist/index.js

Claude 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 (remote HTTP mode)

SLIPWAY_TOKEN=some-long-secret node dist/index.js --http 8788
# then expose it, e.g.:
cloudflared tunnel --url http://localhost:8788

Point the client's MCP connector at https://<your-tunnel>/mcp with the header Authorization: Bearer some-long-secret. ChatGPT accepts remote MCP connectors in developer mode; claude.ai accepts them as custom connectors.

Then just talk:

"Build me a habit tracker with streaks, keep the data in the database, and give me a link to try it."

The assistant scaffolds the app, writes the code, starts a preview, and hands you the URL. Ask for changes; refresh the page.

Where things live

Apps are stored in ~/.slipway/apps/<name> (override with SLIPWAY_HOME). Each app is a plain directory — it's your code, take it anywhere. Per-app extras:

  • data.sqlite — the app's database

  • .env — secrets, injected into the app's process on preview/deploy (values are never echoed back through the AI)

  • .slipway-push.json — Web Push VAPID keys (private key never leaves your machine)

Deploying

  • deploy(app, "local") — builds and serves the app persistently on your machine.

  • deploy(app, "vercel" | "netlify" | "cloudflare") — publishes to a real public URL using that provider's CLI (vercel, netlify, wrangler), which you log into once. Free tiers work; custom domains are configured in the provider's dashboard and are free to attach.

Email and push

  • Email: set SMTP_HOST, SMTP_PORT, SMTP_USER, SMTP_PASS, MAIL_FROM via set_env. Any SMTP provider works — a Gmail app password, Fastmail, Mailgun, Brevo, or your own server.

  • Push: push_generate_keys gives you a VAPID public key for pushManager.subscribe() in your app's frontend; push_send delivers notifications to a subscription. No third-party push service involved.

Security notes

Slipway executes code (npm scripts, dev servers) on the machine it runs on — that is its job. Accordingly:

  • All file operations are confined to the workspace (~/.slipway/apps); path traversal is rejected.

  • HTTP mode without SLIPWAY_TOKEN prints a loud warning: anyone who can reach the port can build and run code. Always set a token before tunneling.

  • Env values are write-only through the AI: list_env returns key names, never values.

  • delete_app requires an explicit confirm: true.

Treat a tunneled Slipway like SSH access to your machine, because that is roughly what it is.

Roadmap

  • One-command public tunnels for previews (share_preview)

  • Postgres option alongside SQLite

  • Auth scaffolding (sessions, magic links) in the fullstack template

  • A hosted multi-tenant mode so one Slipway can serve a team

  • More templates (Next.js, Expo)

Contributions welcome — see CONTRIBUTING.md.

License

MIT. Slipway is an independent open-source project, not affiliated with Anthropic, OpenAI, or Floot.

Available Tools

19 tools
create_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.)

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).

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 previewC

Stop a running preview.

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

    B3.4/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action. File operations (list, read, write, delete) are clearly separated, preview and env tools are distinct, and notification tools (email vs push) have no overlap. No two tools could be confused.

    Naming Consistency5/5

    All tools use snake_case, and most follow a verb_noun pattern (create_app, list_apps, delete_app, write_file, etc.). A few like 'preview_logs' and 'server_status' are noun phrases but remain consistent in style and readable.

    Tool Count4/5

    At 19 tools, this is slightly above the typical 3–15 well-scoped range. However, the server covers a broad domain—app lifecycle, file management, env, previews, deployment, and notifications—so each tool earns its place, and the count feels reasonable rather than bloated.

    Completeness4/5

    The tool set provides full CRUD for apps and files, env management, preview/deploy workflows, and added features like email and notifications. Minor gaps exist (e.g., no app update/rename, no explicit env deletion), but these can be worked around via file writes or redeployment, so agents will rarely hit dead ends.

    Related MCP Connectors

    Related MCP Servers