In-depth architectural comparison of the Weavatrix Refactor and Weavatrix Refactor Js MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Weavatrix Refactor
Developer Tools · Local stdio
Quality: 36/100 (Fair) | Auth: No auth required
Weavatrix Refactor Js
Developer Tools · Local stdio
Quality: 27/100 (Emerging) | Auth: No auth required
Verdict Summary: Choose Weavatrix Refactor if you need specialized Developer Tools tools running via a local process. Choose Weavatrix Refactor Js if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Weavatrix Refactor when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Weavatrix Refactor is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Weavatrix Refactor Js belongs to Developer Tools using local stdio subprocess. Select Weavatrix Refactor when you need capabilities focused on developer tools and Weavatrix Refactor Js when you require tools for developer tools.