llm-migrate
Related Servers
Alternatives to llm-migrate
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI coding agents to inspect project dependency versions, resolve version constraints, and audit Python code for deprecated or incompatible APIs using authoritative evidence and local AST analysis.316 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to inspect a persistent, evidence-backed engineering model and propose typed changes that people review and commit. It provides read tools and a proposal workflow, so agents can assess freshness and suggest updates without silently applying them.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables MCP-capable coding agents to run a human-gated, evidence-backed reverse-engineering pipeline that turns an unfamiliar repository into layered architecture, behavioral contracts, defect findings, validation gates, and a language-agnostic reimplementation spec.136 npm7MIT
- AlicenseAqualityDmaintenanceEnables coding agents to perform safe, project-wide Python refactoring (rename, move, extract, inline, change signature, organize imports, etc.) with a dry-run safety contract and LSP-coordinate addressing.15MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to turn vague requests into context-rich, bounded, verifiable engineering tasks by inspecting project context, generating implementation specs and options, enforcing change boundaries, and verifying results with evidence.1 npmMIT
- 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-
TDQS
Scored across 47 tools
Most tools map to distinct workflow stages and the detailed descriptions make boundaries clear. A few near-twins remain, notably validate_research_artifact vs. validate_research_result and generate_migration_plan vs. generate_session_migration_plan, where an agent could plausibly pick the wrong one.
All tools use imperative lower_snake_case verb_noun names with strong prefixes like get_, record_, validate_, analyze_, generate_, and submit_. Even batch/single pairs like record_change_decision(s) and submit_adaptations follow the same pattern; the minor eval/evaluation abbreviation is not enough to break consistency.
47 tools is far beyond the typical well-scoped 3-15 tool surface and above the 25+ threshold. The count burdens tool selection; several near-duplicate batch/single and workspace/direct validators could be consolidated without losing capability.
The domain is covered end-to-end: scan, research, plan, prompt/file adaptation, change review, blockers, finalization, evaluation, regression analysis, and registry/cost helpers all exist. There are no obvious dead ends; even rare needs such as no-change files, validation disposition, and batch decisions are handled.