Use the Lightning Data Service (LDS) MCP Tools (Beta)

The LDS MCP tools help you work better with Salesforce records by providing guidance on the UI API and applying data consistency and referential integrity best practices.

  • explore_lds_uiapi - Explores and documents Lightning Design System UI API capabilities
  • guide_lds_data_consistency - Data consistency patterns and best practices for using LDS-based components and wire adapters
  • guide_lds_development - LDS development guidelines and component integration
  • guide_lds_referential_integrity - Referential integrity patterns for LDS data management
  • orchestrate_lds_data_requirements -

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 LDS MCP tools.

Ask about using UI API for LWC development.

  • List the available UI API wire adapters and when to use each.
  • Generate the UI API field schema and types for Account.Name, Account.Industry, Contact.Email.
  • Compare imperative vs wired UI API calls for fetching and updating records.

Ask about maintaining data consistency using LDS-based wire adapters and other data strategies.

  • Explain how to use getRecordNotifyChange to keep multiple components in sync.
  • Recommend strategies to handle concurrent edits and stale data with LDS.
  • Outline cache invalidation rules when creating, updating, and deleting related records.

Ask about evaluating a component using LDS development guidelines.

  • Recommend when to use base components (lightning-record-form) vs custom LDS wires.
  • Provide a checklist for building a record editor: validation, errors, toasts, and refresh.
  • Suggest performance tips for LDS-heavy pages (field minimization, batching, memoization).

Ask about referential integrity recommendations.

  • Describe how to prevent orphaned contact records when deleting a parent account.
  • Recommend validations before updating lookups to maintain relationship integrity.
  • Handle missing or soft-deleted related records gracefully in UI and data flows.

See Also