Slipway
Related Servers
Alternatives to Slipway
No user-submitted related servers found.
Related 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
- 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.96 npm3MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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
- 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 gradedqualityBmaintenanceEnables MCP-capable assistants to build, preview, and publish full-stack web apps by directing a hosted coding agent, with tools for projects, wallet balance, domains, previews, downloads, and GitHub export.MIT

Roar AI MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to deploy and manage hosted apps from git repos, read logs, add Postgres databases and domains, manage API keys and budgets, and send requests to 200+ AI models. Connects over remote Streamable HTTP with OAuth sign-in, so users need no API keys, installs, or local server.MIT
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.