code_refactor
Refactor code by replacing search pattern with replace pattern using regex
LABSCO SUMMARY
context_pattern is the reason to use this rather than a plain find-and-replace.
A bare regex rename hits every occurrence in the repository, including the ones in comments and strings you did not think about. Constraining the match to a surrounding context, or to a file glob, is what makes the rewrite safe. Search first with the matched text included, read what came back, then run the replacement.
What it is
Two tools — find a pattern, replace a pattern — with scoping that keeps a repo-wide regex from doing repo-wide damage.
What you get
- code_search finds a regular expression across the tree and returns file paths with line numbers or line ranges
- code_refactor performs the replacement, with capture groups available in the replacement pattern as $1, $2
- context_pattern on both tools: only match where the surrounding context matches as well — rename legacy_sdk inside import statements without touching it anywhere else
- file_pattern to scope either tool with a glob, such as *.js or src/**/*.ts
- Options to include the matched text and the capture groups in the result, so you can see exactly what was caught before acting on it
- The same two operations as a command-line tool, where a dry run previews the replacements instead of writing them
Requirements
Nothing to authorize. Run it over stdio with npx @myuon/refactor-mcp@latest, or install @myuon/refactor-mcp globally. The same binary doubles as a CLI — put cli after the command to search or refactor from a terminal, where a dry run shows the changes before anything is written. One shell caveat there: escape the dollar sign in capture groups so the shell does not expand them before the tool sees them.
Setup effort
One command — npx @myuon/refactor-mcp@latest
USE CASES
01
Finding every place a pattern appears
Search the tree and get file paths with line numbers back.
02
Renaming a symbol across a codebase
Confirm the matches first, then replace with capture groups carried through.
03
Changing an import without touching everything else
Constrain the replacement to matches inside import statements.
04
Limiting a rewrite to one part of the tree
Scope the file glob so nothing outside that path is rewritten.
05
Checking what a regex actually catches
Search with the matched text and capture groups included and read them before committing to a change.
2 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
code_search
Search for code patterns using regex and return file locations with line numbers
BEFORE YOU INSTALL
What to know first
Tools you get
2 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 2 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx @myuon/refactor-mcp@latestMCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add refactor npx @myuon/refactor-mcp@latest
