Metadata Grounding MCP Server (Beta)

Use the Metadata Grounding MCP Server to discover and reuse Salesforce metadata from a connected org such as standard and custom objects and fields, Lightning web components (LWC), users, permission sets, flows, Apex classes, and so on. The server returns metadata the authorized user is permitted to access.

The Metadata Grounding MCP Server 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.

Data 360 provisioned.
API Enabled.
Salesforce Catalog provisioned.
MCP client installed and configured with OAuth authentication. See Set Up Your Org.

Production: https://api.salesforce.com/platform/mcp/v1/platform/metadata-grounding
Sandbox: https://api.salesforce.com/platform/mcp/v1/sandbox/platform/metadata-grounding

The Metadata Grounding MCP Server can help you with these tasks and requests related to finding and reusing Salesforce metadata.

“Find fields related to lease end date or contract expiration.”
“List all picklists that represent priority or urgency.”
“Which objects track reservations or bookings?”
“List components used for opportunity approvals or status progression.”
“Find all users who don’t have a title assigned.”
“Is there already a flow that creates a case?”
“Return all flows created by the Admin User.”
“Can you show me all flows in draft status?”
“Find an Apex class that handles compliance categorization.”

“Explain what the Reservation object represents.”
“What does the Lease End Date field track?”
“What is the org-wide default for Account?”
“Explain what the lightning-record-form component does.”
“What does the force:relatedListSingleContainer component do?”
“Walk me through how the Lead object is shared in this org.”

“Create a new field to track lease expiration date.”
“I need a field for customer status.”
“Add an object for maintenance requests.”
“I need a component to display related records with pagination.”
“Create a UI to update record status via a dropdown.”
“I want a dashboard-style component for operational metrics.”
“Write a trigger on Case that auto-assigns to a Queue Group if origin is Web.”
“Before I create a loyalty points field, check whether one already exists and show me its type and description.”

Flow: “Create a record-triggered flow that automatically updates the Lease Status on Property to ‘Expired’ when the Lease End Date is in the past.”
Lightning Page: “Create a new Lightning page for the Maintenance Request object that shows all request details, related Property, and technician information.”
Lightning Page: “Create a new Lightning page for the Reservation object using reusable summary and related list components.”
LWC: “Generate a Lightning web component that displays open maintenance requests with priority and assigned technician.”
Apex Trigger: “Create a trigger on Maintenance Request that sets the Status to ‘Closed’ when request Completion Date is populated.”

The platform/metadata-grounding server provides these tools. You can view the latest input schema for each tool by going to MCP Servers in Setup. Start with describe_metadata to see which types are available. Use search_metadata to find candidates. Use query_metadata to get full details.

Tool	Description
`describe_metadata`	Discover the metadata types, subtypes, and property schemas available in the connected Salesforce org. Call this tool before the `search_metadata` tool so you know which types and subtypes to filter on. With an empty request, it returns the catalog of supported metadata types. With a metadata type, it returns the JSON schema for that type.
`search_metadata`	Search for metadata records in the connected org using natural language. Use the types and subtypes returned from `describe_metadata` as filters to narrow the results. Returns lightweight descriptors for discovery, not full records. Call `query_metadata` with the returned identifiers to retrieve full records with properties.
`query_metadata`	Retrieve complete metadata records from the connected org, including all type-specific properties. Accepts only identifier values returned by `search_metadata` or `query_metadata`. Use `metadataIdentifiers` for direct lookup, or `parentIdentifiers` to retrieve all children. Refer to `describe_metadata` for property definitions for the returned fields.

The Metadata Grounding MCP Server supports a subset of metadata for an org, but the types of metadata you can query is expanding. Ask the agent to get a list of the current metadata types supported by the server.
Only active picklist values for a picklist field are stored in Salesforce Catalog and available in the Metadata Grounding Server.
The Metadata Grounding Server isn’t available in scratch orgs or in Developer Edition orgs with namespaces turned on. For example, if you’re using a Developer Edition org to create managed packages.
The server is read-only and can’t create, change, or delete anything.
The results come from the Salesforce Catalog index, not from your live org. A recent change in your org can take time to appear, and some types refresh less often than others.