Skip to content

forcedotcom/sf-skills / skills/experience-app-mcp-generate

experience-app-mcp-generate

Verified

Create, extend, deploy, review readiness for, or activate an App MCP, a Salesforce custom hosted MCP server for an Aura Experience Site. Trigger when the user wants to expose an Experience UI or backend action to agents, create local ECA and server metadata, add eligible global invocable Apex or autolaunched Flow tools, add Prompt Builder templates as MCP prompts or tools, preview or perform server activation, deploy the existing MCP stack, or review its readiness. For server setup, always ask whether the user wants HXL widgets for eligible Apex-backed tools through platform-mcp-tool-widget-coordinate. For a standalone request to generate Custom Lightning Types or widgets for an Apex-backed MCP tool, route directly to platform-mcp-tool-widget-coordinate; do not trigger this skill for HXL generation alone. Do not trigger for remote MCP registration or generic Apex and Flow work unrelated to Experience Site agent access.

references/eca-fields.md

View on GitHub
# External Client Application Field Map

Read this reference when reviewing or changing ECA metadata produced by `render_eca.mjs`. Paths below are under `<default-package>/main/default` and use the ECA DeveloperName as `<name>`.

## Generated files

### `externalClientApps/<name>.eca-meta.xml`

Full path: `<default-package>/main/default/externalClientApps/<name>.eca-meta.xml`

| Field | Controls |
|---|---|
| `<label>` | Display label |
| `<description>` | Description |
| `<contactEmail>` | Contact email |

### `extlClntAppGlobalOauthSets/<name>.ecaGlblOauth-meta.xml`

Full path: `<default-package>/main/default/extlClntAppGlobalOauthSets/<name>.ecaGlblOauth-meta.xml`

| Field | Controls |
|---|---|
| `<callbackUrl>` | OAuth callback URLs |
| `<isPkceRequired>` | PKCE requirement |
| `<isRefreshTokenRotationEnabled>` | Refresh-token rotation |
| `<isNamedUserJwtEnabled>` | Named-user JWT |
| `<label>` | Global OAuth settings label |

### `extlClntAppOauthSettings/<name>.ecaOauth-meta.xml`

Full path: `<default-package>/main/default/extlClntAppOauthSettings/<name>.ecaOauth-meta.xml`

| Field | Controls |
|---|---|
| `<commaSeparatedOauthScopes>` | OAuth scopes |
| `<label>` | OAuth settings label |

### `extlClntAppOauthPolicies/<name>.ecaOauthPlcy-meta.xml`

Full path: `<default-package>/main/default/extlClntAppOauthPolicies/<name>.ecaOauthPlcy-meta.xml`

| Field | Controls |
|---|---|
| `<permittedUsersPolicyType>` | Permitted users |
| `<refreshTokenPolicyType>` | Refresh-token policy |
| `<refreshTokenValidityPeriod>` | Refresh-token lifetime value |
| `<refreshTokenValidityUnit>` | Refresh-token lifetime unit |
| `<ipRelaxationPolicyType>` | IP relaxation |
| `<requiredSessionLevel>` | Required session level |
| `<label>` | OAuth policy label |

### `extlClntAppPolicies/<name>_defaultPolicy.ecaPlcy-meta.xml`

Full path: `<default-package>/main/default/extlClntAppPolicies/<name>_defaultPolicy.ecaPlcy-meta.xml`

| Field | Controls |
|---|---|
| `<isEnabled>` | Application availability |
| `<isOauthPluginEnabled>` | OAuth plugin availability |
| `<label>` | Default policy label |

## Permitted users

Default new ECAs to `AdminApprovedPreAuthorized`: the admin grants ECA access through associated profiles or permission sets; those users do not individually consent. This is not limited to administrator users. Remind the admin to arrange preauthorization; this skill does not manage end-user permissions.

If the MCP server is intended for all authenticated site users, suggest `AllSelfAuthorized`: eligible authenticated users authorize the ECA themselves without individual admin preauthorization. Apply it only after an explicit choice. ECA authorization does not replace site, tool, or data access controls.

Pass `--permitted-users-policy <AdminApprovedPreAuthorized|AllSelfAuthorized>` to `render_eca.mjs` for generation and `--check` with the confirmed choice; omission uses the admin-preauthorized baseline. Preserve intentional existing policies. A baseline difference is a review finding, not authorization to change a live ECA.

## Editing invariants

- Store all client-specific OAuth redirect URIs as newline-separated values inside the single `<callbackUrl>` element. Each value must be an absolute redirect URI with an allowed scheme and host. Do not invent a default callback URL, and do not write an empty `<callbackUrl>`.
- Keep the `MCP` and `RefreshToken` OAuth scopes unless the user explicitly changes the supported authorization flow.
- Refresh-token lifetime is controlled by the policy type, period, and unit in the OAuth policy component.
- Keep every `<externalClientApplication>` value aligned with the ECA DeveloperName. A rename requires coordinated file-name and cross-component reference changes, not an isolated field edit.
- The renderer derives labels across the related components. When changing the display label, review the labels in the global OAuth, OAuth settings, and OAuth policy components for consistency.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall