Code Migration Planning with Claude Code: MCP Tool Boundary
A production playbook for code migration planning in cross-industry operations using Claude Code: mcp tool boundary, run-scoped inputs, logs, typed results, and artifacts.
Audience: Engineering teams preparing framework or API migrations
The problem
Engineering teams preparing framework or API migrations need code migration planning to run repeatedly against repository snapshots, target docs, and compatibility notes. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Expose only the MCP tools needed for code migration planning, validate tool arguments, keep credentials in the owning service, and log each call outside the sandbox.
Tradeoffs and failure modes
Narrow tool boundaries reduce agent flexibility, but make the integration reviewable and supportable. For code migration planning, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Tool policy
tool: migration-planning_lookup
agent: Claude Code
input_scope: /skill/.argo/inputs
credential_owner: broker
log_arguments: true
network_policy: allowlisted
Run this on Argo