Flisk App Builder
OfficialRelated Servers
Alternatives to Flisk App Builder
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceLets a coding agent hand a plain-language app idea to a hosted AI software team that shapes, designs, builds, tests and deploys it, returning a one-time link into the full build workspace. Also lists your apps with their stage, pending approvals and live addresses after a standard OAuth sign-in.MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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 gradedqualityCmaintenanceDeploy full-stack apps from AI. 75+ tools: GitHub/Docker deploy, databases, environments, security, billing.3-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to build and update complete applications, including creating, updating, publishing, previewing, and configuring databases, security, permissions, and server-side integrations.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create and iteratively edit browser games, web apps, and websites from natural-language prompts, track builds, preview results, and request publication.MIT
- AlicenseBqualityDmaintenanceEnables non-coders to build software by describing ideas in natural language, orchestrating AI agents and CLI workers via chat without needing a terminal.3023 npm4Apache 2.0
TDQS
Scored across 24 tools
The set has several look-alike families (status/resource_list/network_list/stack_list/agent_list/project_info, and doctor/runtime_check/config_verify), but the descriptions explicitly cross-reference each other with 'use X for Y' guidance, which resolves most confusion. A few boundaries (doctor vs runtime_check, project_info vs config_verify) still require careful reading.
The dominant convention is noun_verb (project_init, resource_create, config_regenerate, stack_assign, agent_sessions, network_list), applied to 19 of 24 tools. The remaining five are bare lifecycle verbs (up, down, status, logs, doctor), which is a deliberate and readable deviation but not fully uniform.
24 tools is on the heavy side, but the domain is genuinely broad: project scaffolding/import/eject, config generation and verification, stack lifecycle, resource management, agents, and host checks. Nearly every tool maps to a distinct operation, though a few (project_templates, config_explain, runtime_check) are niche.
Creation and inspection are well covered (project_init/import, resource_create, tool_add, up/down/restart/run), but there is no delete or remove operation for resources or stacks, no per-service stop, and agent tooling is read-only (list/sessions) with no lifecycle control. These gaps will force agents to fall back to raw CLI calls.