plexium-tools vs Automation Weaver
plexium-tools is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑20.
plexium-tools is a plugin bundle for AI coding tools published by Clarit AI. No marketplace we read lists it any more. 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-10-29. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace clarit-ai/plexium | Removed on 2026-10-20 Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 5 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | 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 | plexium-toolsno longer listed · | Automation Weaver |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 5 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (automation-weaver-mcp.vercel.app/api/mcp) |
| Transport (differs) | Not stated | SSE |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 7 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/clarit-ai/plexium | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 402 (46 h ago) |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of plexium-tools
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Research-backed orchestration for Claude Code. Structured workflow from idea to production with parallel execution, session memory, 70-point validation, autonomous mode, and…
-
Lyra - a master-level AI prompt optimization specialist.
-
Multi-harness planning, execution, and review through the local Claudexor installation.
-
Explore your org's processes and drive AI transformation
-
Migra workflows de n8n/Make al ecosistema Claude Code. Analiza JSONs, mapea nodos, propone arquitectura e implementa. Usa cuando el usuario pegue un JSON de n8n, mencione migrar…
-
Teach Claude to orchestrate microservices and business processes with Conductor. This skill adds full workflow lifecycle management: define workflows with any task type (HTTP…
What each says it does
plexium-tools
Install, set up, and verify Plexium from inside Claude Code
Automation Weaver
No-code workflow visualizer and automation blueprint builder.
How to run each
plexium-tools
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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 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
Neither one's marketplaces publish the settings it asks for.
What it can do: plexium-tools · What it can do: Automation Weaver · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.