A
licenseB
qualityC
maintenanceEnables AI assistants to scaffold, edit, live-preview, and deploy full-stack apps with built-in database, email, and push notification capabilities through natural language.
19
MIT
Slipway
Related Servers
Alternatives to Slipway
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceDeploy full-stack apps from AI. 75+ tools: GitHub/Docker deploy, databases, environments, security, billing.2-
- AlicenseNot gradedqualityBmaintenanceEnables building and running visual workflows conversationally inside Claude, orchestrating your existing connector tools step-by-step without storing credentials or owning integrations.0MIT
- FlicenseNot gradedqualityCmaintenanceConnects Claude AI to any development project (Django, Next.js, Laravel, etc.) with 15+ universal tools for shell, file, git, logs, Docker, tests, and more.1-
Prowpt MCP Serverofficial
AlicenseCqualityCmaintenanceEnables AI agents to create, edit, and publish web apps on Prowpt.ai through project management, code editing, and AI assistant tools.59MIT- AlicenseBqualityDmaintenanceEnables non-coders to build software by describing ideas in natural language, orchestrating AI agents and CLI workers via chat without needing a terminal.307 npm4Apache 2.0
TDQS
A3.5/5.0
Scored across 22 tools
Disambiguation5/5
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.
Naming Consistency5/5
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.
Tool Count4/5
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.
Completeness4/5
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.
Maintenance
ActivityMaintained
ResponsivenessNo issues