
Lousa
io.github.henriquepePublished by GitHub account henriquepev0.1.1Updated Oct 24, 2026
A whiteboard where AI agents draw their explanations as hand-drawn animated diagrams
Overview
Lousa is a local MCP server and web viewer that lets an AI agent draw explanations as animated, hand-drawn diagrams on a live whiteboard.
- What you can do
- Create boards from a declarative scene of boxes, arrows, cylinders, notes and text, returning a board id and viewer URL, and replace a scene so only changed elements animate again. Read a single board or list boards, and delete boards when done. Read what the user has selected in the viewer so the agent can target exactly those elements. Render everything stroke by stroke in a browser tab as a hand-drawn diagram.
- When to use it
- Useful when you want an agent to explain architecture, flows or concepts visually instead of in long text, and when you want to iterate on a diagram live by pointing at elements in the viewer.
- Requirements
- Runs as a local process via npx, requiring Node.js 18.17 or later; the stdio endpoint auto-starts a local server with a viewer at 127.0.0.1:4666. Self-hosting a shared server uses environment variables such as LOUSA_TOKEN, LOUSA_URL, LOUSA_BUCKET and LOUSA_DATA_DIR.
Installation
In SourceWeft
- Open Lousa in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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_selectionand targets exactly that. - Boards expire by default (12h, sliding) — a whiteboard, not a document graveyard.
ttlHours: 0keeps a board forever.
Quick start
Requires Node.js 18.17+.
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
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 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.
Development
License
AGPL-3.0 © Henrique Pires
Source: README.md at commit c2dd696
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts