ZeroWidth Workbench vs Automation Weaver
ZeroWidth Workbench is an MCP server published by zerowidth.ai. Marketplaces we read that list it: 1 (Official MCP Registry). Automation Weaver is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-03. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  ZeroWidth Workbench | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 1.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | ZeroWidth Workbench | Automation Weaver |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.zerowidth.ai/mcp/x/workbench) | Remote server (automation-weaver-mcp.vercel.app/api/mcp) |
| Transport (differs) | Streamable HTTP | SSE |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository | Not stated | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 23 h ago | Answered with HTTP 402 (6 days ago) |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
ZeroWidth Workbench
Build, run and publish Workbench flows, tasks, shims and knowledge bases.
Automation Weaver
No-code workflow visualizer and automation blueprint builder.
How to run each
ZeroWidth Workbench As a remote MCP server
claude mcp add --transport http workbench https://api.zerowidth.ai/mcp/x/workbench --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Automation Weaver As a remote MCP server
claude mcp add --transport sse automation-weaver https://automation-weaver-mcp.vercel.app/api/mcp --header "payment-signature: <YOUR_PAYMENT_SIGNATURE>"Requires: payment-signature header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of ZeroWidth Workbench responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: ZeroWidth Workbench · What it can do: Automation Weaver · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.