Flisk logo

Flisk

Run, inspect, and control local multi-service apps from AI coding agents through MCP.

Install Flisk

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "flisk": {
      "command": "npx",
      "args": [
        "-y",
        "@flisk-sh/flisk"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @flisk-sh/flisk

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked .

Overview

flisk MCP server gives Claude Code, Cursor, and Codex agent access to a local multi-service development runtime. It lets agents start applications, check service health, inspect logs, and use runtime controls while Flisk manages services defined by Compose files or plain commands. Reach for it when an AI coding workflow needs visibility into, and control over, the application running on a developer’s machine. Flisk is local-only in its described workflow and does not replace production deployment tooling.

Use cases

  • Start a multi-service development app from an AI coding client
  • Check local service health while debugging
  • Inspect application logs through an agent
  • Control a running local development environment
  • Operate an imported Compose project from an AI workflow

Key features

  • MCP access to local runtime controls
  • Service health checks
  • Log inspection
  • Compose import and service definitions
  • Docker, Tilt, and local-process workflows
  • Generated gateway and service configuration

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · @flisk-sh/flisk (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars47Stargazers on the source repository.
npm downloads35kPackage downloads in the last 30 days.
Last commitTodayMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Flisk works

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:

Terminal
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.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Flisk

flisk is an MCP server that connects AI coding agents to Flisk’s local multi-service development runtime. Its main tools let agents start and control applications, check service health, and inspect logs. It is designed for local workflows involving services defined through Compose files or Flisk service configuration.

Install Flisk with `npm install -g @flisk-sh/flisk`, then start its MCP interface with `flisk mcp`. Node.js 22.12 or newer is required. Docker, Tilt, and Bun are additionally needed for the container-based workflow, while smaller applications can run as local processes.

Yes, flisk is described as working with Cursor through its MCP server. Configure Cursor to launch the local `flisk mcp` command, then use the connection to expose local application health, logs, and runtime controls to the agent.

Yes, run `flisk import .` in the project directory to create Flisk service definitions from an existing Compose application. You can then run `flisk up` and allow the MCP-connected agent to work with the local runtime.

No, Flisk is for local development and does not handle production deployment. Use separate deployment tools for hosting and operating the application outside the local environment.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewFlisk AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/flisk?style=directory)](https://allmcps.com/mcp/flisk)
HTML Embed
<a href="https://allmcps.com/mcp/flisk"><img src="https://allmcps.com/api/badge/flisk?style=directory" alt="Flisk on AllMCPs" /></a>