lc_apps_listLABSCO SUMMARY
A whole development loop behind one binary, still pre-1.0.
Scaffolding, package management, linting, process supervision and git in a single server is what makes describe-it-then-ship-it plausible without giving the agent a free shell. Two things bound the risk: everything is confined to the apps directory, and paths outside your home directory are rejected. The project's own banner says it is not ready for production, so treat it as a workshop rather than a deployment pipeline.
What it is
A Go binary that gives an assistant a working area under ~/LayeredApps and the tools to build in it: file operations with ripgrep-backed search, project scaffolding for Vite and Next.js, package management through pnpm, PM2 process control, ESLint, and a full set of git commands.
What you get
- Apps and files listed, read, written, edited, moved, copied and deleted inside an application directory —
lc_apps_list,lc_file_list,lc_file_read,lc_file_write,lc_file_edit,lc_file_move,lc_file_copy,lc_file_delete,lc_folder_delete - Text search across an application's files, run through ripgrep —
lc_text_search - New projects scaffolded: React, Vue or Svelte templates, or Next.js with TypeScript, JavaScript, Tailwind or App Router —
vite_app_create,nextjs_app_create - Dependencies installed and added, and dev servers supervised —
pnpm_install,pnpm_add,pnpm_pm2 - ESLint run over named files with optional auto-fix, restricted to relative paths —
lc_js_lint - Git worked normally: status, diff, add, commit, log, branch, restore, stash, push, pull and init —
git_status,git_diff,git_add,git_commit,git_log,git_branch,git_restore,git_stash,git_push,git_pull,git_init - A page fetched through Chrome after its JavaScript has loaded —
lc_chrome_visit - A prompt library the agent can list and read —
lc_prompt_list,lc_prompt_read
Requirements
No account and no key. Install with Homebrew on macOS or Linux, the install script, or a prebuilt binary; Go 1.24+ is only needed to build from source. The client launches the binary with the mcp_server argument. Work happens under ~/LayeredApps unless LAYERED_APPS_DIRECTORY says otherwise, and that path is validated to stay inside your home directory. The project carries a work-in-progress notice and has not reached version 1.0.
Setup effort
One command — curl -fsSL https://raw.githubusercontent.com/layered-flow/layered-code/main/scripts/install.sh | sudo bash
USE CASES
01
Standing up a new front end from a description
Scaffold the project with the template you want, install dependencies, and start the dev server without typing a command.
02
Editing across a project you did not write
Search the codebase with ripgrep, read the files that matched, and apply find-and-replace edits in place.
03
Getting the change committed and pushed
Review the diff, stage it, write the commit message and push, all inside the same conversation.
04
Checking what the page actually renders
Load the running app through Chrome so the assistant sees the page after JavaScript, not the empty shell.
30 tools
Listed in project docs. Your client may show a different list.
lc_file_listlc_text_searchlc_file_readlc_file_writelc_file_editlc_file_movelc_file_deletelc_file_copylc_folder_deletelc_chrome_visitvite_app_createnextjs_app_createpnpm_installpnpm_addpnpm_pm2lc_js_lintlc_prompt_listlc_prompt_readgit_statusgit_diffgit_commitgit_loggit_branchgit_addgit_restoregit_stashgit_pushgit_pullgit_initBEFORE YOU INSTALL
What to know first
Tools you get
30 tools named in the project's documentation.
Requires
layered-code on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
curl -fsSL https://raw.githubusercontent.com/layered-flow/layered-code/main/scripts/install.sh | sudo bashMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"layered-code": {
"command": "/usr/local/bin/layered-code",
"args": [
"mcp_server"
]
}
}
}/usr/local/bin/layered-code is where the install script above puts the binary. If you installed with Homebrew, use layered-code; on Windows, use the full path to layered-code.exe with double backslashes, for example C:\\Users\\YourUsername\\bin\\layered-code.exe.
