forcedotcom/sf-skills / skills/experience-app-mcp-delivery-generate
experience-app-mcp-delivery-generate
VerifiedPackage and deliver an existing Salesforce hosted MCP server/App MCP for an Experience Site as an MCP configuration file or a Claude plugin repository. Discover the serving URL and External Client Application client ID, generate client configuration, optionally bundle skills in a plugin, and provide local testing and private GitHub handoff instructions. Plugin packaging supports Claude only; reject requests for Codex, ChatGPT, or other plugin platforms. Use for connecting clients and packaging delivery, not for creating or activating the Salesforce MCP server.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 16.5 KB |
| references/eca-consumer-key.md | markdown | 2.1 KB |
| references/mcp-config-delivery.md | markdown | 2.6 KB |
| references/plugin-format-and-publishing.md | markdown | 8.5 KB |
| scripts/developer_name.mjs | script | 464 B |
| scripts/discover_mcp_context.mjsexecutable | script | 6.0 KB |
| scripts/generate_mcp_config.mjsexecutable | script | 1.5 KB |
| scripts/generate_plugin.mjsexecutable | script | 10.8 KB |
| scripts/mcp_config.mjs | script | 3.9 KB |
| scripts/preflight.mjsexecutable | script | 5.0 KB |
| scripts/retrieve_eca_consumer_key.mjsexecutable | script | 5.1 KB |
references/mcp-config-delivery.md
View on GitHub# Standalone MCP configuration delivery
Use when the user wants connection configuration without a plugin. Ask for the target client and an absolute path to a **new JSON file**. Do not change an existing client configuration; generate a file the user can review and import or merge using their client's supported workflow.
The delivery workflow is client-neutral; configuration schemas still depend on the client. The current generator supports the `claude-code` profile (default, `oauth.clientId`) and an explicitly requested custom `requested` profile (`auth.CLIENT_ID`). Do not claim either schema works in every client. For another client, establish its supported schema before generating; report unsupported formats rather than guessing.
A configuration input needs only `destination`, `mcp`, and optionally `authStyle`:
```json
{
"destination": "/absolute/user-selected/new-mcp-config.json",
"authStyle": "claude-code",
"mcp": {
"serverName": "partner-tools",
"environment": "production",
"domain": "your-my-domain",
"siteDeveloperName": "PartnerPortal",
"mcpName": "PartnerTools",
"clientId": "actual-public-eca-consumer-key"
}
}
```
Substitute the selected environment (`production`, `developer`, `sandbox` or `scratch`), its My Domain token and the exact site/server developer names as described in the skill; the generator builds the environment's route, so users need not supply or assemble the URL. Replace the four route components with `url` only when reusing an authoritative setup URL. An explicitly selected integer `mcp.callbackPort` is supported only for `claude-code`; omit it when skipped. Plugin identity, author, icon, repository and skills are unnecessary.
Preview:
```bash
node "<skill-dir>/scripts/generate_mcp_config.mjs" /path/to/delivery-config.json
```
Create the selected file:
```bash
node "<skill-dir>/scripts/generate_mcp_config.mjs" /path/to/delivery-config.json --write
```
Inspect the written JSON: `mcpServers` wraps the selected server key; its entry contains `type: "http"`, the exact HTTPS URL and the selected public client ID in the target profile. Confirm an omitted callback port remains absent. The generator refuses existing destinations and does not write plugin files or a README. Report the file path, selected org/site/server/ECA, profile and validation results. Provide import/merge guidance for the selected client; leave OAuth, routing, tool listing and user permissions pending until verified there. Do not run `claude plugin validate` on a standalone configuration file or provide publication steps unless separately requested.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |