How do I install Lousa?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Lousa need an API key?

No required environment variable is listed on this record.

When was Lousa last checked?

Last checked 2026-11-09. A whiteboard where AI agents draw their explanations as hand-drawn animated diagrams

Lousa MCP server

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y [email protected]

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1claude mcp add io.github.henriquepe-lousa -- npx -y lousa@0.1.1

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.henriquepe-lousa": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ]9    }10  }11}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 0.1.1
Last checked

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

Lousa

A whiteboard where your AI agent draws its explanations.

Your agent drawing a rate limiter explanation, stroke by stroke

Ask your agent "explain this visually" and it sketches an animated, hand-drawn diagram on a live board — instead of another wall of text. Lousa is an MCP server + web viewer: the agent authors a declarative scene (boxes, arrows, cylinders, notes), and the board renders it stroke by stroke, as if someone were drawing it in front of you.

Lousa is Portuguese for the classic school blackboard.

Why it's different

The agent is the artist. No prompt box, no OCR — your coding agent already has the context and draws through typed MCP tools.
Live, incremental drawing. Follow-ups edit the scene; the open tab animates only what changed, like watching the diagram evolve.
Point at things. Click elements in the viewer to select them, then tell your agent "improve what I selected" — it reads your selection through get_selection and targets exactly that.
Boards expire by default (12h, sliding) — a whiteboard, not a document graveyard. ttlHours: 0 keeps a board forever.

Quick start

Requires Node.js 18.17+.

# Claude Code
claude mcp add lousa -- npx -y lousa mcp

# or run the server directly
npx lousa            # viewer at http://127.0.0.1:4666

Any MCP host works — for stdio configuration use command npx, args ["-y", "lousa", "mcp"]. The stdio endpoint auto-starts the local server, so the viewer is always available. Then ask your agent to "draw how our auth flow works" and open the URL it returns.

MCP tools

Tool	What it does
`create_board`	Creates a board from a scene, returns `{id, url}`
`update_board`	Replaces the scene; unchanged elements stay byte-identical so only changes animate
`get_board` / `list_boards`	Read boards
`get_selection`	What the user selected in the viewer (ids + full elements)
`delete_board`	Deletes a board

The scene is a JSON array of elements — box, ellipse, diamond, cylinder, arrow (connects ids), line, text, note — rendered with rough.js. The full schema ships inside the tool definitions; agents need no extra setup.

Self-hosting a shared server

Run lousa on any Node host and point machines at it:

LOUSA_TOKEN=<secret> HOST=0.0.0.0 npx lousa        # server
LOUSA_URL=https://your-host LOUSA_TOKEN=<secret> npx lousa mcp   # each client

LOUSA_TOKEN gates board listing/creation/deletion and /mcp; per-board URLs act as capability links. AWS Lambda + S3 deployment is supported out of the box (lambda.js handler + LOUSA_BUCKET for storage); any HTTPS front (API Gateway, etc.) works.

Env var	Default	Purpose
`PORT` / `HOST`	`4666` / `127.0.0.1`	server bind
`LOUSA_DATA_DIR`	`~/.lousa/boards`	filesystem board storage
`LOUSA_BUCKET`	—	use S3 storage instead of filesystem
`LOUSA_TOKEN`	—	require bearer token (header or `?t=`) on global routes and MCP
`LOUSA_URL`	—	`lousa mcp` proxies to this remote server
`LOUSA_DEFAULT_TTL_HOURS`	`12`	default board expiry

Development

npm install
npm test          # node --test
node cli.js       # local server

Lousa

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Lousa?

Does Lousa need an API key?

What transport does Lousa use?

When was Lousa last checked?

Documentation

Lousa

Why it's different

Quick start

MCP tools

Self-hosting a shared server

Development

License