Use the Migration and Integration MCP Tools (Beta)

The migration and integration MCP tools accelerate LWC development by providing guidance on Aura-to-LWC migration, converting Figma designs to LWC specifications, and applying accessibility and Jest test best practices.

  • verify_aura_migration_completeness - Aura-to-LWC migration completeness checklist and validation
  • guide_figma_to_lwc_conversion - Converts Figma designs to LWC specifications
  • run_lwc_accessibility_jest_tests - Accessibility testing utilities and Jest integration for LWC

MCP Tools for LWC Development is a pilot or beta service that is subject to the Beta Services Terms at Agreements - Salesforce.com or a written Unified Pilot Agreement if executed by Customer, and applicable terms in the Product Terms Directory. Use of this pilot or beta service is at the Customer's sole discretion.

The tools are invoked automatically based on your prompts. Here are some possible prompts that invoke the migration and integration MCP tools.

Ask about Aura-to-LWC migration guidelines.

  • Audit these Aura components and produce an LWC migration completeness checklist with gaps and blockers.
  • Validate parity between Aura and LWC versions; list missing features, events, and styling differences.
  • Recommend replacements for Aura-only features (navigation, events, eval) using LWC-safe patterns.

Ask about generating a component based on a Figma design.

  • Convert this Figma design into an LWC spec: components, slots, props, events, states, and SLDS tokens.
  • Extract design tokens such as for spacing, color, radius, and typography from Figma and map them to SLDS variables.
  • Generate an LWC component breakdown and file scaffold plan from this Figma frame.

Fetching data directly from Figma using this tool isn't currently supported. To convert Figma designs to LWC code, we recommend that you use a Figma-based MCP server, such as the Framelink Figma MCP server, along with the guide_figma_to_lwc_conversion tool.

Ask about generating or evaluating accessibility tests for a component.

  • Add Jest accessibility tests for this component’s default, error, and interactive states.
  • Generate test cases for focus order, ARIA roles, and keyboard navigation.
  • Diagnose these failing a11y assertions and propose code/test fixes to pass accessibility checks.

See Also