Salesforce Experience CMS vs com.lightsyncpro/lsp
Salesforce Experience CMS is a plugin bundle for AI coding tools published by Salesforce. Marketplaces we read that list it: 1 (Community GitHub marketplaces). com.lightsyncpro/lsp is an MCP server published by lightsyncpro.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace forcedotcom/sf-skills | Listed Version: 0.2.1 Forks (GitHub): 371 Stars (GitHub): 1 093 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.8.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Salesforce Experience CMS | com.lightsyncpro/lsp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 093 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 371 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (lightsyncpro.com/mcp-connect) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 5 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/forcedotcom/sf-skills | github.com/tagteamdesign/lightsync-pro |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 404 (32 h ago) |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Salesforce Experience CMS
Author and source media for Experience Cloud content: apply CMS branding, generate CMS content, search existing Salesforce CMS or Data 360 media, and search and download ethically licensed stock imagery through Salesforce media-management tooling. Use when producing or branding CMS content for a Digital Experience site, locating an existing content asset, or finding a stock image for a page. Also render accessible CMS-managed images, video, audio, and documents in React experiences.
com.lightsyncpro/lsp
Sync Lightroom, Figma, Dropbox & Canva assets to WordPress and Shopify via natural language.
How to run each
Salesforce Experience CMS As a Claude Code plugin
/plugin marketplace add forcedotcom/sf-skills
/plugin install experience-cms@salesforce
com.lightsyncpro/lsp As a remote MCP server
claude mcp add --transport http lsp https://lightsyncpro.com/mcp-connect
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.lightsyncpro/lsp has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Salesforce Experience CMS · What it can do: com.lightsyncpro/lsp · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.