Skip to main content
Glama

Slipway

直接从 Claude 或 ChatGPT 构建并交付真实应用——免费且开源,使用你已经在付费的 AI 订阅。

Slipway 是一个 MCP(Model Context Protocol)服务器,它为你的 AI 助手提供真正交付软件而非仅仅编写软件的工具:搭建应用、编辑文件、运行可在浏览器中打开的实时预览、将数据存储在内置数据库中、发送邮件、发送推送通知,并部署到真实的公共 URL。

没有计量,也没有额度。你已经在付费的模型(Claude Pro/Max、ChatGPT Plus,或任何支持 MCP 的客户端)负责思考;Slipway 只负责执行。一切都在你的机器上运行,部署则进入免费托管层级上的你的账户。

滑道是船只建造并下水启航所用的坡道。

连接后你的助手可以做什么

功能

工具

替代

搭建应用(静态、React+Vite、API、全栈)

create_app、list_apps、delete_app

样板工程初始化

编辑代码

write_file、read_file、list_files、delete_file

从聊天中复制粘贴

带日志的实时预览

start_preview、preview_logs、stop_preview

本地开发环境搭建

数据库(每个应用独立的 SQLite,零配置)

query_database

Supabase 配置

机密 / 配置

set_env、list_env

处理 .env 文件

部署到公共 URL

deploy(local、Vercel、Netlify、Cloudflare Pages)

git + CI + 托管配置

事务性邮件(任意 SMTP)

send_email

Resend 配置

Web 推送通知(VAPID)

push_generate_keys、push_send

OneSignal 配置

npm 包

install_dependencies

终端操作

Related MCP server: @forgespace/ui-mcp

快速开始

需要 Node.js ≥ 22.5(内置 SQLite 需要它)。

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

添加到 claude_desktop_config.json:

{
  "mcpServers": {
    "slipway": {
      "command": "node",
      "args": ["/absolute/path/to/slipway/dist/index.js"]
    }
  }
}

ChatGPT、网页版 claude.ai,或你的手机(远程 HTTP 模式)

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

将客户端的 MCP 连接器指向 https://<your-tunnel>/mcp,并携带请求头 Authorization: Bearer some-long-secret。ChatGPT 在开发者模式下接受远程 MCP 连接器;claude.ai 则将其作为自定义连接器接受。

然后直接这样说:

“帮我做一个带连续天数的习惯追踪器,把数据保存在数据库里,再给我一个可以试用的链接。”

助手会搭建应用、编写代码、启动预览,然后把 URL 交给你。你可以提出修改要求;然后刷新页面。

应用存放位置

应用存储在 ~/.slipway/apps/<name> 中(可用 SLIPWAY_HOME 覆盖)。每个应用都是一个普通目录——这是你的代码,可以随身携带。每个应用的额外内容:

  • data.sqlite — 应用的数据库

  • .env — 机密,预览/部署时注入到应用的进程中(值永远不会通过 AI 回显)

  • .slipway-push.json — Web 推送 VAPID 密钥(私钥永远不会离开你的机器)

部署

  • deploy(app, "local") — 在你的机器上构建并持久地提供该应用。

  • deploy(app, "vercel" | "netlify" | "cloudflare") — 使用该提供商的 CLI(vercel、netlify、wrangler)发布到真实的公共 URL,你只需登录一次即可。免费层级即可用;自定义域名在提供商的仪表盘中配置,且免费绑定。

电子邮件与推送

  • 电子邮件:通过 set_env 设置 SMTP_HOST、SMTP_PORT、SMTP_USER、SMTP_PASS、MAIL_FROM。任何 SMTP 提供商都可用——Gmail 应用专用密码、Fastmail、Mailgun、Brevo,或你自己的服务器。

  • 推送:push_generate_keys 会为你生成一个 VAPID 公钥,用于应用前端的 pushManager.subscribe();push_send 将通知投递到订阅。不涉及第三方推送服务。

安全说明

Slipway 会在其运行的机器上执行代码(npm 脚本、开发服务器)——这正是它的职责。因此:

  • 所有文件操作都被限制在工作区(~/.slipway/apps)内;路径穿越会被拒绝。

  • 未设置 SLIPWAY_TOKEN 的 HTTP 模式会打印一个醒目的警告:任何能访问该端口的人都可以构建并运行代码。在进行隧道转发前,务必设置一个令牌。

  • 环境变量值对 AI 是只写的:list_env 只返回键名,从不返回值。

  • delete_app 需要显式的 confirm: true。

请将已建立隧道的 Slipway 视为对你机器的 SSH 访问,因为它大致就是这样。

路线图

  • 一条命令即可为预览创建公共隧道(share_preview)

  • 除 SQLite 外增加 Postgres 选项

  • 在全栈模板中加入认证脚手架(会话、魔法链接)

  • 托管的多租户模式,让一个 Slipway 服务整个团队

  • 更多模板(Next.js、Expo)

欢迎贡献——参见 CONTRIBUTING.md。

许可证

MIT。Slipway 是一个独立的开源项目,与 Anthropic、OpenAI 或 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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers