tesserae-studio-mcp

Part of the Tesserae Studio repo (packages/tesserae-studio-mcp), so the bridge stays in lockstep with the Studio API it wraps. Published to PyPI as tesserae-studio-mcp.

The MCP bridge for Tesserae Studio. It lets an AI agent (Claude Code, Claude Desktop, or any MCP client) author Tesserae widgets end to end: scaffold a widget, edit its files, lint it, mine a data schema, register it to a running Tesserae, and render it, all through a running Studio server.

This is a thin stdio client. It talks to your Studio server over its local REST API (STUDIO_URL), so the linting, mining, registering, and rendering all run in your own Studio, which in turn drives your Tesserae.

scaffold_widget → write_file → lint_widget → register_widget → faithful_render → mine_data_schema

Prerequisites

A running Tesserae Studio server (it serves the API this bridge calls, and its web UI). See the Studio README for how to run it. Studio in turn connects to a Tesserae for live data and faithful (e-ink) render.

Install

Run this on the machine where your agent runs, which may differ from where Studio runs.

pip install tesserae-studio-mcp

or from source:

pip install "git+https://github.com/dmellok/tesserae-studio#subdirectory=packages/tesserae-studio-mcp"

Either gives you the tesserae-studio-mcp command.

Configure your agent

Point your MCP client at tesserae-studio-mcp. Example (Claude Desktop / Claude Code mcpServers config):

{
  "mcpServers": {
    "tesserae-studio": {
      "command": "tesserae-studio-mcp",
      "env": { "STUDIO_URL": "http://localhost:8770" }
    }
  }
}

Claude Code one-liner:

claude mcp add tesserae-studio -e STUDIO_URL=http://localhost:8770 -- tesserae-studio-mcp

• STUDIO_URL — where your Studio server is reachable (default http://localhost:8770). For a remote / Home Assistant Studio, use its LAN address, e.g. http://192.168.1.50:8770.

The build loop and the widget contract rules are sent to the agent automatically at handshake (FastMCP instructions), so you don't paste a prompt.

At startup the bridge asks your Studio for those rules rather than only using the copy baked into this package, so a corrected rule reaches you on the next agent session without a reinstall. If Studio is unreachable, older than the endpoint, or answers with something this version does not understand, the embedded copy is used instead and everything still works.

The tool list and how results are handled do come from this package, so those need an upgrade. Studio knows which bridge version it ships with: when this one is behind, the agent is told to ask you to run pipx upgrade tesserae-studio-mcp (or your installer's equivalent) and restart it. Studio also shows a bridge pill once one has connected, marked for update when it is out of date.

Run without installing

From a clone:

pip install mcp httpx
STUDIO_URL=http://localhost:8770 python -m tesserae_studio_mcp

License

AGPL-3.0-or-later, matching Tesserae Studio.