Skip to content

forcedotcom/sf-skills / plugins/builder/salesforce-development/skills/platform-headless-360-integrate

platform-headless-360-integrate

Verified

Read org state and change Setup through the Headless 360 (H360) MCP tools discover, describe, dispatch_readonly, and dispatch. Use when H360 tools are present and the answer is org state no skill or sf command reads: Setup settings, feature or license access, org-specific caps, health checks, release updates. Also H360 setup and errors (401, 403, 404, ROUTE_NOT_FOUND, INVALID_ARGUMENT). DO NOT TRIGGER for records, SOQL, schema, limits in sf org list limits, deploys, or which-plugin questions.

FileKindSize
SKILL.mdskill md18.2 KB
references/errors.mdmarkdown2.4 KB
references/manual-registration.mdmarkdown2.1 KB

references/manual-registration.md

View on GitHub
# Manual H360 registration

Load this only when the user is connecting without the bundled plugin proxy.
Org activation is still required; see the main skill. Walk the user through
configuration changes rather than making them automatically.

1. **For manual registration only**, create an External Client App (ECA) in
   the same org (also a one-time admin task):
   - OAuth scopes: `mcp_api` and `refresh_token`.
   - Turn on **Issue JSON Web Token (JWT)-based access tokens for named users**,
     and require PKCE.
   - Callback URL for Claude Code: `http://localhost:<port>/callback`. Pick a
     fixed port; the same port goes into the next step.
   - A new ECA can take up to 30 minutes to start working.
2. **Register the server** with the URL for the org's environment (only when
   connecting manually):

   | Org | Server URL |
   |---|---|
   | Production | `https://api.salesforce.com/platform/mcp/v1/platform/headless-360` |
   | Sandbox or scratch org | `https://api.salesforce.com/platform/mcp/v1/sandbox/platform/headless-360` |
   | Org that blocks login through login.salesforce.com and test.salesforce.com | `https://api.salesforce.com/platform/mcp/v1/d/{mydomain}/{develop\|scratch}/platform/headless-360` |

   `{mydomain}` is the part before `.my.salesforce.com` in the org's login host.

   ```bash
   claude mcp add --transport http --client-id <ECA consumer key> --callback-port <port> headless-360 <server URL>
   ```

   Add `--client-secret` only if the ECA requires a secret. The CLI prompts for
   it, so the user runs that command in their own terminal. Never ask for the
   secret in chat.
3. **Sign in to a manual registration.** Restart Claude Code, open `/mcp`, and
   authenticate `headless-360` in the browser. Then return to Step 1 of the main skill. The
   bundled Codex server uses the CLI org login and does not use this OAuth flow.

Other MCP clients need the same server URL, client ID, and a callback URL
registered on the ECA. Public reference:
https://developer.salesforce.com/docs/platform/hosted-mcp-servers/references/reference/headless-360-mcp.html
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