Arezzo MCP Server

Deterministic Google Docs API compiler. Your agent stops silently corrupting documents. Exposed over MCP by the arezzo mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

You cannot safely modify a Google Doc by constructing batchUpdate requests yourself. The API uses UTF-16 code units with cascading index shifts — insert 10 characters at position 50, and every subsequent index in your batch is now wrong. A single miscalculation silently corrupts the document with no error message.

• UTF-16 length calculation (not Python len() — surrogate pairs count differently)
• Reverse-order execution for same-type mutations (delete from end to start)
• Two-phase compilation (content mutations before format mutations)
• Cascading offset tracking across multi-step operations

Adding it to your client

The server ships on PyPI as arezzo, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the arezzo mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by ConvergentMethods; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.