vitela-bridge

The agent bridge for Vitela, the editor for ExactTeX.

It is a small program that runs on your machine. Your coding agent talks to it over the Model Context Protocol (MCP); it talks to the Vitela tab open in your browser. Every tool the agent calls runs inside that tab — the project, the compiler and the TeX engine are all there — and the answer comes back. Nothing leaves your machine.

One rule makes it safe to hand an agent the keys: the agent never edits text. A change it proposes lands in your document as an ExactTeX revision, signed agent, that you accept or reject in Vitela's review margin like any other suggestion.

The full guide, with screenshots: https://vitela.artificialfallibility.com/agent.

Install

Node 20 or newer. No install step: npx fetches and runs it.

Claude Code

claude mcp add vitela-bridge -- npx -y github:camilochs/vitela-bridge

Codex

codex mcp add vitela-bridge -- npx -y github:camilochs/vitela-bridge

Cursor, Windsurf, Zed, Claude Desktop and other MCP clients — add to the client's MCP configuration:

{
  "mcpServers": {
    "vitela-bridge": {
      "command": "npx",
      "args": ["-y", "github:camilochs/vitela-bridge"]
    }
  }
}

Related MCP server: cursor_worker

Pair

1. Start your agent. The bridge starts with it and prints a six-digit code; ask the agent for it (the bridge_status tool returns it).

2. Open Vitela, press Agent in the header, type the code. The card says Connected.

3. Work. The agent reads the project, runs the check, compiles, verifies the bibliography, and proposes changes you accept or reject in the margin.

The code changes every time the bridge starts. A reload of the tab keeps the pairing.

Tools

Configuration

The tab connects to the bridge on the machine that serves the page for a plain-http dev server, and on 127.0.0.1 for localhost and for the published site.

License

MIT.

If the bridge is useful to you, a star on this repository helps others find it — and tells us it is worth the care.