Automation Weaver vs PROCESIO
Automation Weaver is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). PROCESIO is an MCP server published by Procesio-Externals. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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 |  PROCESIO | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 0.1.6 Forks (GitHub): 4 Stars (GitHub): 4 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 | Automation Weaver | PROCESIO |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 4 |
| Forks (GitHub) (differs) | No figure on GitHub | 4 |
| Last release (differs) | Not published | 2026-11-03 |
| Where it runs (differs) | Remote server (automation-weaver-mcp.vercel.app/api/mcp) | On your machine (https://github.com/Procesio-Externals/procesio-cli/releases/download/v0.1.6/procesio-mcp-0.1.6.mcpb) |
| Transport (differs) | SSE | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/procesio-externals/procesio-cli |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-27 |
| Endpoint at the last check (differs) | Status out of date: last check 39 h ago returned HTTP 402 | no remote endpoint we check |
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
Automation Weaver
No-code workflow visualizer and automation blueprint builder.
PROCESIO
Lets your own AI assistant build, run, validate and audit PROCESIO processes, forms and documents.
How to run each
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
PROCESIO
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Automation Weaver has a remote endpoint we 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
The marketplaces of Automation Weaver publish no settings it asks for, so we do not compare settings.
What it can do: Automation Weaver · What it can do: PROCESIO · 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.