Refactory
Related Servers
Alternatives to Refactory
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables agents to statically analyze Python source via AST traversal, computing McCabe cyclomatic complexity, cognitive nesting depth, and dependency graphs to pinpoint refactoring hotspots. It returns standardized refactoring plans, decomposition guidance, and code-metric telemetry with zero external dependencies.7-
- AlicenseAqualityCmaintenanceExtracts deterministic architecture maps from codebases for AI agents, enabling queries about blast radius, routes, security findings, and production readiness without sending code anywhere.6MIT

loctree-mcpofficial
FlicenseNot gradedqualityAmaintenanceStructural code intelligence for AI agents. Scan once, query everything — dead exports, circular imports, dependency graphs, and more. CLI + MCP server.6 npm9-- AlicenseNot gradedqualityCmaintenanceA graph-powered code intelligence engine that indexes codebases into a structural knowledge graph to provide AI agents with deep context on function calls, types, and execution flows. It offers local, zero-dependency tools for hybrid search, impact analysis, and dead code detection across Python, JavaScript, and TypeScript projects.675 PyPI814MIT
- FlicenseNot gradedqualityBmaintenanceEnables developers and coding agents to refactor Python codebases by re-aliasing imports and migrating dependencies, safely rewriting module paths and callsites through deterministic AST analysis instead of error-prone regex. It also surfaces dependency graphs and refactoring plans that minimize LLM token usage.7-
- FlicenseNot gradedqualityBmaintenanceEnables coding agents and developers to parse Python source into ASTs and compute complexity metrics that pinpoint refactoring hotspots, dead code, and breaking API diffs. It returns decomposition plans and dependency-graph telemetry over MCP, keeping token usage low with zero external dependencies.7-
TDQS
Scored across 11 tools
Each tool has a distinct and clearly defined purpose within the decomposition pipeline—analyze, characterize, decompose, depmap, extract, fix imports, metrics, plan, report, verify, verify exports. There is no overlap or ambiguity between them; an agent can easily select the correct tool for each step.
All tools follow the consistent pattern 'refactory_verb_noun' (e.g., refactory_analyze, refactory_fix_imports, refactory_verify_exports). The naming is uniform, predictable, and uses only snake_case, making it easy for an agent to infer functionality from the name.
With 11 tools, the server is well-scoped for its domain of code decomposition. Each tool serves a necessary step in the pipeline, and the count is neither too low (missing functionality) nor too high (unwieldy). The tool set earns its place.
The tools cover the entire decomposition lifecycle: analysis, characterization, dependency mapping, planning, extraction, import fixing, verification, metrics, reporting, and export verification. There are no obvious gaps; the surface is complete for the stated purpose of refactoring a monolithic file.