livo

The Livo developer toolkit (TypeScript): a programmatic SDK and the livo CLI in one package, for connecting to and building Livo projects — the web3 product factory you also drive from Claude.

• As a library — a typed client over the Livo MCP: list projects, push code, manage indexers/subgraphs, read deploys. Use it from agents, scripts, or CI.
• As a CLI — the livo command: sign in once (browser), link a project, and get the local inner loop (dev / push / watch).

CLI quickstart

npm i -g @livo-build/livo     # installs the `livo` command
livo login                   # opens your browser to authorize (or: livo login <api-key>)
livo link                    # pick a project → pulls it locally
livo dev                     # writes .env.local (public build vars) + runs your dev server
livo watch                   # auto-push on save → preview URL

(npx @livo-build/livo also runs livo directly.)

SDK quickstart

import { createClient } from "@livo-build/livo";

const livo = createClient({ token: process.env.LIVO_API_KEY! });
const { projects } = await livo.projects.list();
await livo.code.push([{ path: "interface/index.html", content: "<h1>hi</h1>" }], { project_id: projects[0].slug });
const { indexers } = await livo.indexers.list(projects[0].slug);

Layout

src/
  index.ts            library entry — exports (Node + browser safe)
  rpc.ts client.ts pkce.ts oauth.ts types.ts errors.ts
  cli.ts              the `livo` bin (#!/usr/bin/env node)
  cli/                CLI-only modules (fs/http live here, never in index.ts)

The library entry stays free of Node-only imports, so importing @livo-build/livo in a browser/bundler never pulls the CLI code.

Develop

npm install
npm run typecheck
npm run build

Auth: interactive users sign in via OAuth (browser, no secret to paste); API keys are for CI/headless. Tokens are stored in ~/.livo/credentials.json, per-project state in .livo/project.json.

Publish

npm install && npm run build && npm publish   # public via publishConfig