# flisk [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/flisk-sh/flisk  
**GitHub Stars:** 47  
**npm Downloads (last month):** 35048  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/flisk

## Description
The local runtime your AI coding agent can start, check and fix. One command runs your multi-service app from a Compose file or plain commands, and an MCP server gives Claude Code, Cursor and Codex its health, logs and controls. MIT, no account.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "flisk": {
    "command": "npx",
    "args": ["-y","@flisk-sh/flisk"]
  }
}
```

## Documentation

## What flisk does

flisk connects AI coding agents to Flisk’s local development runtime through the Model Context Protocol. Flisk can run the parts of an application—such as APIs, websites, workers, AI agents, and databases—from a Compose file or from local commands. The MCP interface exposes that runtime to an agent so it can work with the application while development is in progress.

The runtime is organized around services. A project can be represented by one `service.json` file per service, or an existing `docker-compose.yml` can be imported with `flisk import`. For generated projects, Flisk can create Dockerfiles, Compose entries, gateway routes, health checks, and Tilt configuration from the service definitions.

## How it works

The MCP server is started through the Flisk command-line interface with `flisk mcp`. An MCP-compatible coding client then communicates with the local process and can use the runtime’s application controls. Flisk starts services in dependency order based on health checks, provides local routes, and supports either containerized development or plain local processes for smaller applications.

A typical workflow is to create or import a project, start it with Flisk, and let the coding agent inspect or operate the running environment. The runtime can include application services, databases, a local gateway, and live reload when Docker and Tilt are used. The project remains on the developer’s machine; Flisk does not deploy it to production.

## Setup and configuration

Install the CLI globally with:

```bash
npm install -g @flisk-sh/flisk
```

Flisk requires Node.js 22.12 or newer. A container-based project also requires Docker, Tilt, and Bun 1.2 or newer. Smaller applications can run as local processes without Docker. On Windows, the full container workflow runs inside Ubuntu on WSL2, with Docker Desktop’s WSL integration enabled.

Create a project with `flisk project --yes`, import an existing Compose application with `flisk import .`, or use the interactive `flisk create` command. Start the resulting project with `flisk up`, then launch the MCP interface with `flisk mcp`. The `flisk doctor` command reports missing development prerequisites, and `flisk down` stops a running demo or application.

## Tools and capabilities

The MCP connection gives supported agents access to the runtime’s health, logs, and controls. In practical terms, an agent can use it to:

- Start and manage the local application runtime.
- Check whether services are healthy.
- Inspect service logs while diagnosing development issues.
- Control the running local environment from the coding client.
- Work with applications composed of multiple services rather than a single process.

Flisk also supports live updates through Tilt for containerized development and generates service wiring such as `DATABASE_URL`, frontend API URLs, gateway routes, and health checks from project configuration.

## Limitations and notes

Flisk is intended for local development. Its documented workflow does not deploy applications to production, so production hosting remains the responsibility of other tools. The complete container workflow has more prerequisites than the local-process mode, and Windows users need to run that workflow inside WSL2. Generated files are managed by Flisk; the CLI can detect drift when generated files are edited manually.

_Full upstream README: https://allmcps.com/mcp/flisk/readme_

