Developer · Local MCP server

Weavatrix Refactor Js

Transactional refactoring MCP with 11 evidence-backed tools, hash-bound previews, and rollback.

Visit Weavatrix Refactor Js's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.sergii-ziborov/weavatrix-refactor-js
Version
0.1.6
Status
Active
Category
developer
Transport
stdio (local process)
Package
npm
Published
2026-08-10
Updated
2026-08-10
Publisher
sergii-ziborov (GitHub) · 5 servers with pages here
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/sergii-ziborov) · how
Website
weavatrix.com
Repository
github.com/sergii-ziborov/weavatrix-refactor-js
Source
Registry API entry

Packages

RegistryPackageVersionTransportEnvironment variables
npmruntime: npxweavatrix-refactor-js0.1.6stdioWEAVATRIX_ALLOW_SOURCE_EDITS, WEAVATRIX_REFACTOR_HOME, WEAVATRIX_PRECISION

How to connect Weavatrix Refactor Js

Weavatrix Refactor Js runs locally from a Node.js package published to the npm registry: weavatrix-refactor-js version 0.1.6. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y weavatrix-refactor-js@0.1.6. It reads these environment variables: WEAVATRIX_ALLOW_SOURCE_EDITS, WEAVATRIX_REFACTOR_HOME and WEAVATRIX_PRECISION; set them in the client's configuration for this server. Required arguments: repoRoot.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "weavatrix-refactor-js": {
      "command": "npx",
      "args": [
        "-y",
        "weavatrix-refactor-js@0.1.6"
      ],
      "env": {
        "WEAVATRIX_ALLOW_SOURCE_EDITS": "<value>",
        "WEAVATRIX_REFACTOR_HOME": "<value>",
        "WEAVATRIX_PRECISION": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More from sergii-ziborov (GitHub)

All 5 →
ServerRunsEndpoint or package
HostwatchObserve and safely control sites, TLS, containers, traffic, databases and jobs with Hostwatch.Remote · HTTPLive check: sign-in requiredgethostwatch.com
RadioChronLocal-first Wi-Fi incident diagnostics with native BLE scan, history, and risk evidence.Local · stdionpm: radiochron-mcp
Weavatrix GitFast, bounded, read-only Git evidence for local AI coding agents.Local · stdionpm: weavatrix-git
Weavatrix JsAlways-fresh local repo graph: LSP-backed impact, Health, dead code, endpoints, architecture.Local · stdionpm: weavatrix-js

More developer servers

All 5,152 →
ServerRunsEndpoint or package
WeavatrixNative Weavatrix MCP: 67 read-only tools for code, local CI, n8n, Dify, agents, Mermaid, Web3.Local · stdionpm: weavatrix
Weavatrix RefactorTransactional refactoring extension with 11 evidence-backed tools, previews, and rollback.Local · stdionpm: weavatrix-refactor
WeavzGoverned app access for AI agents: 1,000+ apps & 12,000+ tools via Code Mode MCP.Remote · HTTPLive check: sign-in requiredplatform.weavz.io
Web & Developer Data ToolsWebsite tech stacks, domain WHOIS/DNS/SSL, sitemaps, PDF text, GitHub trending and more.Remote · HTTPLive check: sign-in requiredmcp.apify.com
Web Browser (kogiQA)This web browser has been designed to help your agent debug and develop complex web applications.Local · stdionpm: kogiqa-mcp
Web Content ExtractorExtract and process web content into clean, structured formats optimized for LLMs.Local · stdionpm: @agenson-horrowitz/web-content-extractor-mcp