Slipway
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_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.) |
| list_appsA | List all apps in the Slipway workspace, with running preview/deploy URLs. |
| delete_appB | Permanently delete an app and its data. Requires confirm=true. |
| list_filesB | List all files in an app (node_modules and .git are skipped). |
| read_fileC | Read a file from an app. |
| write_fileB | Create or overwrite a file in an app. Parent directories are created automatically. |
| delete_fileC | Delete a file or directory inside an app. |
| install_dependenciesC | Run npm install in the app directory. |
| start_previewB | Start a live dev preview of the app and return its URL. Give the URL to the user. |
| share_previewA | Open a public HTTPS URL for the app's preview via a free Cloudflare quick-tunnel — anyone (including phones) can open it. Starts the preview first if needed. Requires the cloudflared CLI. |
| stop_previewB | Stop a running preview (and its public tunnel, if shared). |
| preview_logsC | Recent stdout/stderr from a running preview — use this to debug. |
| query_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. |
| set_envA | 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. |
| list_envB | List the env keys set for an app (keys only, never values). |
| deployA | 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). |
| undeployB | Take down a local deploy (it will no longer restart with the server). |
| send_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). |
| push_generate_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. |
| push_sendB | Send a Web Push notification to a browser subscription (the JSON from PushSubscription.toJSON(), which the app's frontend should send to its backend). |
| export_appA | 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. |
| server_statusA | Show the workspace location and everything currently running. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.