# Lampo > Frame-exact video review that closes the loop: people note on the exact frame, agents fix, people check and approve. On Lampo Cloud, or open source on your machine or your own server. The source: https://github.com/lampo-vr/lampo. The product is called Lampo, and so is everything people and agents type: the repository (`lampo-vr/lampo`), the `lampo` command (and `lampo-mcp`), the `LAMPO_*` settings, the MCP server's key `lampo`, the `lampo://` resources and the npm package `@lampo-vr/lampo`. Setups from before keep working: `vr` and `vr-mcp` run the same commands, `VR_*` settings are still read, and `vr://` addresses and the key `video-review` still answer. ## Docs - [For agents](https://lampo.video/agents.md): the review loop, the `lampo watch` line format, every `lampo` command, asking the reviewer, MCP, and what not to do. - [Agents and the CLI](https://lampo.video/docs/agents/) - [MCP](https://lampo.video/docs/mcp/) - [Review links](https://lampo.video/docs/sharing/) - [Workflow](https://lampo.video/docs/workflow/) - [Playbooks](https://lampo.video/docs/playbooks/) - [The taste file](https://lampo.video/docs/taste/) - [On your phone](https://lampo.video/docs/mobile/) - [Speech to text](https://lampo.video/docs/speech/) - [Project files](https://lampo.video/docs/files/) - [Footage search](https://lampo.video/docs/footage/) - [Publishing](https://lampo.video/docs/publishing/) - [Configuration](https://lampo.video/docs/configuration/) - [Run it as a server](https://lampo.video/docs/server-mode/) - [Docker](https://lampo.video/docs/docker/) - [Going live](https://lampo.video/docs/go-live/) - [Moving to a server](https://lampo.video/docs/moving/) - [Email](https://lampo.video/docs/email/) - [The first run](https://lampo.video/docs/onboarding/) - [Data format](https://lampo.video/docs/data-format/) - [HTTP API](https://lampo.video/docs/api/) - [Architecture](https://lampo.video/docs/architecture/) ## Setup - Claude Code: `claude mcp add lampo -- /path/to/lampo/bin/lampo-mcp` - Other MCP clients: `lampo mcp config ` prints a ready config (claude, codex, cursor, vscode, antigravity, windsurf, gemini, zed, json). - A hosted server: run `lampo login ` once; every `lampo` command and the MCP server then work against it. ## The loop in short The person connects you once and tells you one sentence: `Use Lampo for ""`. Lampo's MCP server explains the loop in its first read, and every answer says what comes next. 1. The project: `list_folders`, the one the person named (none: a new name becomes the project with V1; several fit: ask once, with options). 2. V1: no version there yet, put it up yourself: `request_upload` from a chat app, `lampo render --to