Before you set up multisite quoting with AI tools, confirm that your org has the required products, permissions, licenses, and a supported edition. You also need admin credentials, the Salesforce CLI, and an AI coding agent such as Claude Code or Agentforce Vibes to run the configure-eu-cloud-multisite recipe.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions |
Prerequisites
- Set up your org for the Salesforce Hosted MCP Servers.
- Activate the Headless 360 MCP Server.
- Connect your coding agents.
- Access to a Salesforce Energy & Utilities org with all necessary licenses.
- Login URL and admin credentials for the target org.
- Access to an AI agent tool configured to run the setup skill (for example, Claude
Code or Agentforce Vibes running the setup skill that executes the
configure-eu-cloud-multisite Setup Operation Recipe (SOR)
files).
Note For Claude Code, install the Salesforce Development plugin, which provides Salesforce-specific skills and org context through hosted Model Context Protocol (MCP) servers. - Salesforce CLI
Products and features
- Energy & Utilities Sales
- Revenue Management
- Salesforce Pricing
- External Pricing
- Context Service
- Quote and Order settings
- Multisite Quoting feature
Permissions
- View Setup and Configuration
- Modify All Data or Customize Application
- Assign Permission Sets
- Manage Users
- Manage Profiles and Permission Sets
- Customize Application
Suggested Technology and Experience
To run this setup, an admin directs an AI coding agent, such as Claude Code or Agentforce Vibes, that calls headless Salesforce setup APIs. The tested workflow uses Claude Code or Agentforce Vibes as the agent. When a headless metadata call isn't available, the workflow falls back to the Salesforce CLI.
The workflow relies on these components:
| Component | Purpose | Availability | Required |
|---|---|---|---|
| Coding agent (Claude Code or Agentforce Vibes) | Reads org state and executes the setup steps | Yes | Yes |
| Headless Model Context Protocol (MCP) server | Exposes the headless setup/metadata routes the agent calls | Yes | Yes |
Headless metadata skill (SOR steps that call the
/headless/metadata route)
|
Applies setup metadata during the workflow | Yes | Yes |
Multisite Quoting recipe
(configure-eu-cloud-multisite) |
Drives the multisite quoting setup path | Yes | Yes |
Preconfig recipe
(energy-utilities-preconfig) |
The prerequisite recipe runs when the agent is blocked at the provisioning layer | Yes | Conditional (fallback) |
Salesforce CLI (sf) |
Fallback to deploy metadata when a headless route is unavailable | Yes | Conditional (fallback) |
Agentic Tips
- Interaction pattern: Have the agent read the org state first, confirm prerequisites, then change order, publish the screen flow, and finish by verifying the end state and producing a handoff summary. (This matches the order of the task steps.)
- Provisioning-block fallback prompt: In the rare case the agent can't run
the multisite quoting recipe and reports "Blocked at provisioning layer," the
tested setup path provides this prompt: Run
energy-utilities-preconfigrecipe first, it acts as a prerequisite, then reverify if provisioning gap is fixed and move to multisite recipe. - Context to provide: Org details, Energy & Utilities license visibility, and setup access for the relevant nodes. Never paste credentials into a prompt.