MCP Tools Reference (Beta)
MCP Tools for LWC are part of the lwc-experts and aura-experts toolsets.
MCP Tools for LWC 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.
LWC provides these MCP tools in the lwc-experts toolset to assist with LWC development, testing, optimization, and best practices.
When working with these tools using Agentforce Vibes Extension, you must enable the a4d-general-rules-no-edit.md and a4d-lwc-rules-no-edit.md global rules. The a4d-general-rules-no-edit.md rule is enabled by default. For more information on configuring rules in Agentforce Vibes, see Agentforce Rules in the Agentforce Vibes Extension Developer Guide.
Use these MCP tools to facilitate LWC development.
| Tool Name | Description |
|---|---|
guide_lwc_development | Provides comprehensive LWC development workflow and implementation guidelines |
guide_lwc_best_practices | Offers LWC development best practices and coding standards guidance |
create_lwc_component_from_prd | Creates complete Lightning web components from PRD specifications |
orchestrate_lwc_component_creation | Provides step-by-step component creation guidance |
orchestrate_lwc_component_optimization | Optimizes performance and applies best practices for LWC |
guide_lwc_accessibility | Provides accessibility guidelines and testing instructions |
guide_lwc_rtl_support | Provides Right-to-Left (RTL) internationalization support and RTL development guidance |
guide_lwc_slds2_uplift_linter_fixes | Analyzes LWC code along with the slds-linter output to fix issues based on SLDS 2 guidelines |
orchestrate_lwc_slds2_uplift | Provides migration guidance for upgrading to SLDS 2 |
Use these MCP tools to improve your testing workflow.
| Tool Name | Description |
|---|---|
orchestrate_lwc_component_testing | Provides a comprehensive testing workflow and generates tests |
create_lwc_jest_tests | Generates comprehensive Jest test suites |
review_lwc_jest_tests | Reviews and validates Jest test implementations |
run_lwc_accessibility_jest_tests | Provides accessibility testing utilities and Jest integration for LWC |
Use these MCP tools to review LDS development guidelines and discover LDS wire adapters and UI API type definitions for LWC development.
| Tool Name | Description |
|---|---|
guide_lds_development | Provides LDS development guidelines and component integration |
guide_lds_data_consistency | Provides data consistency patterns and best practices for using LDS-based components and wire adapters |
guide_lds_referential_integrity | Provides referential integrity patterns for LDS data management |
explore_lds_uiapi | Explores and documents Lightning Data Service UI API capabilities |
orchestrate_lds_data_requirements | Analyzes and clarifies LDS data requirements to produce PRD-ready specifications. |
Use this tool to speed up your Figma to LWC conversion.
| Tool Name | Description |
|---|---|
guide_figma_to_lwc_conversion | Converts Figma designs to LWC specifications. Fetching data directly from Figma using this tool isn't currently supported. We recommend that you use the Framelink Figma MCP server along with this tool |
Use this MCP tool to assist with Aura-to-LWC migration, validate migration completeness, and convert design specifications.
| Tool Name | Description |
|---|---|
verify_aura_migration_completeness | Provides a migration completeness checklist and validates results |
Use these MCP tools to analyze LWC code and provide guidance on best practices.
| Tool Name | Description |
|---|---|
guide_lwc_security | Analyzes components based on product security and Lightning Web Security guidelines |
These Aura MCP tools in the aura-experts toolset assist with Aura-to-LWC migration.
When working with these tools using Agentforce Vibes Extension, you must enable the a4d-general-rules-no-edit.md and a4d-lwc-rules-no-edit.md global rules. The a4d-general-rules-no-edit.md rule is enabled by default. For more information on configuring rules in Agentforce Vibes, see Agentforce Rules in the Agentforce Vibes Extension Developer Guide.
| Tool Name | Description |
|---|---|
create_aura_blueprint_draft | Creates a comprehensive Product Requirements Document (PRD) blueprint for Aura component migration |
enhance_aura_blueprint_draft | Enhances an existing draft PRD with expert analysis and unknown resolution |
transition_prd_to_lwc | Provides migration guidance for creating LWC components from Aura specifications |
orchestrate_aura_migration | Orchestrates the complete Aura-to-LWC migration workflow |
See Also