Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
Flisk is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
94/100
trust score
920
downloads a day
local
runs on your machine
18k
downloads in 30d
What it does
Run your whole app on your computer with one command: build, start, check and fix a local stack.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user flisk-mcp '--' npx -y @flisk-sh/flisk mcp
# 2 — ask your agent for something these tools do
# echo, doctor, down and 18 more
Flisk costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publisher
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Flisk as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user flisk-mcp '--' npx -y @flisk-sh/flisk mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
21 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Echo a message back
| Parameter | Type | Required | Notes |
|---|---|---|---|
| message | string | yes | — |
Check whether this machine can run the Flisk stack. Optionally set projectPath to include checks for a specific Flisk project. Returns data.ready and data.host.canUp; run it before up.
No parameter schema on file.
Stop the running stack, optionally selecting its project with projectPath.
No parameter schema on file.
Stacks, resources, their ingress URLs and container ports, the stack-level ports, and Tilt readiness (data.tilt.readiness: ready, pending, failures, enabled; null when no Tilt answers). Optionally select the project with projectPath.
No parameter schema on file.
A bounded snapshot of recent logs from the running stack (default the last 200 lines, at most 10000). Optionally select the project with projectPath. Not a stream.
No parameter schema on file.
List the selected project's services (resources) with their stack, type and port. Set projectPath when the MCP server is not running from the project root.
No parameter schema on file.
Restart a running resource in the stack (or trigger its rebuild). Set projectPath when the MCP server is not running from the project root.
No parameter schema on file.
List AI agent resources (appType: 'agent') in the project with their stack, runtime, durability and port. Set projectPath when the MCP server is not running from the project root.
No parameter schema on file.
List the sessions of a running AI agent resource (id, last activity, status, checkpoint size), or read one session's checkpoint when sessionId is set. Set projectPath when the MCP server is not running from the project root.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| required | yes | — |
List the project's stacks with their resource counts. Set services to include each stack's service names, and verbose for its description. Set projectPath when the MCP server is not running from the project root.
No parameter schema on file.
Project root, whether the generated master files exist (data.configured, data.missingFiles), and resource and stack counts. Set projectPath when the MCP server is not running from the project root.
No parameter schema on file.
The Traefik URL of every frontend and API service, with its base path, port and whether it answers (running, stopped). Set projectPath when the MCP server is not running from the project root.
No parameter schema on file.
Check that the generated files match .flisk/project.json and that every service.json is valid. Returns data.valid, data.errors, data.warnings and data.diffs; a drifted generated file is fixed with config_regenerate. Set projectPath when the MCP server is not running from the project root.
No parameter schema on file.
Explain one project file: whether Flisk generated it or the user owns it, its source, whether it is edited now, whether editing it blocks up, and what to edit instead. Run it before editing a file you did not write. Set projectPath when the MCP server is not running from the project root.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| required | yes | — |
Check that the installed Flisk CLI has its bundled runtime assets (engine, templates). Returns ok, assetRoot and what is missing; a source checkout reports ok: false because the assets exist only in a packaged install. projectPath is optional: a project-local install under its node_modules is…
No parameter schema on file.
Regenerate the master config files in .flisk/.flisk-out/ from .flisk/project.json. A dry run by default, which returns the planned changes as text; set dryRun to false to write them, which discards hand edits in those generated files. Set projectPath when the MCP server is not running from the…
No parameter schema on file.
Scaffold a new service (service.json, Dockerfile, source and a test) with flisk resource <name> --yes, or register an existing directory that already has a service.json. Returns the command's text output. Without stack it uses the only existing stack or main, and fails when several stacks…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| required | yes | — |
Assign resources that have no stack yet to a stack (writes stack into their service.json). A resource already in a stack is refused. Returns the command's text output. Set projectPath when the MCP server is not running from the project root.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| required | yes | — |
Create a Flisk project with flisk project --yes: in projectPath (an existing directory; default the server's directory) write .flisk/project.json and generate its files, or, with template, clone a starter project into a new directory there (then call project_init again with projectPath set to…
No parameter schema on file.
Write EJECTED.md with flisk eject --json: it lists the generated Tilt files and how to run the stack with plain Tilt, and copies, moves or deletes nothing. It changes the project, so it is refused unless confirm is true; dryRun returns the plan (data.generatedFiles, data.created) without…
No parameter schema on file.
Import the services in a directory's root docker-compose.yml as bring-your-own service.json files with flisk import --json, which runs the pinned flisk-import from npm (the first run needs network access). It writes without asking: set dryRun to get the plan only, and force to overwrite an…
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Flisk or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 94 / 100
Release 1.4.37 · scanned 5 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score94
Findings14 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digest8f02cc38c1aa7bf2eed8b0d3a89cbc78badcaba0a41f4a284b40ab73b468424c
Score vectorthreat 100 → client 94
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
can send data / act on an external service
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest8f02cc38c1aa7bf2
Scanned2026-11-05
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.4.37. Pin a release below and the command asks for exactly that one.
1.4.37
5 Nov 2026
latestNo release note was published with this version.
1.4.34
4 Nov 2026
No release note was published with this version.
1.4.33
3 Nov 2026
No release note was published with this version.
1.4.32
1 Nov 2026
No release note was published with this version.
1.4.30
1 Nov 2026
No release note was published with this version.
1.4.29
1 Nov 2026
No release note was published with this version.
1.4.27
1 Nov 2026
No release note was published with this version.
1.4.25
31 Oct 2026
No release note was published with this version.
1.4.24
31 Oct 2026
No release note was published with this version.
1.4.23
31 Oct 2026
No release note was published with this version.
1.4.22
31 Oct 2026
No release note was published with this version.
1.4.17
30 Oct 2026
No release note was published with this version.
1.4.14
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Flisk can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.