isWebMCP

Salesforce · Experience Cloud and Lightning Web Components · Proposed scenario

Evaluate a public content-discovery component

An illustrative pilot for an Experience Cloud reference-solutions team: review a public content-discovery page and its proposed search contract. Start with source coverage and platform compatibility, not claims about Agentforce or live CRM automation.

Documented by the company

What the official sources establish

Our proposed workflow—not a deployed integration

  • A proposed owner is an Experience Cloud developer-experience team maintaining a public CMS reference application. Select one anonymous, synthetic content-discovery page; first assess whether meaningful controls are present in its fetched HTML.
  • Save source evidence and review a sanitized proposed search contract. If appropriate, adapt our search-tool recipe to the owner-controlled content lookup. A plain JavaScript recipe is not an installable Lightning component and must pass the owner security and lifecycle review.
  • After an owner-reviewed component change is published, recheck the same public URL and comparison context. Keep existing component and permission tests. An agent would still need an authorized, compatible browser connection to test the actual task.

What isWebMCP can provide now

  • Hosted public-source inspection, imported contract lint, accessible-controls and search-tool recipes, and complete compatible before/after source comparisons through the CLI or remote MCP server.

What needs development or agreement

  • A Salesforce-specific component adapter, Lightning Web Security compatibility testing, authenticated tenant access, and runtime outcome verification remain unbuilt. We provide no managed package, Agentforce integration, CRM connector, or authorization assessment.

Proposed pilot · Not performed

A bounded way to test the hypothesis

Proposed two-week pilot: one public synthetic CMS reference page, one component engineer, and a security reviewer. Exclude CRM records, lead creation, case updates, and authenticated content.

Deliverables to produce

  • A source-coverage decision, a reviewed contract proposal, a compatibility checklist, and paired source reports for any owner-approved page fix. Unsupported behavior is recorded, not scored as a completed task.

Measures to collect—not results

  • Proposed acceptance: the owner confirms meaningful source coverage, triages every prioritized finding, and obtains a complete compatible comparison after a supported change.
  • The security reviewer must accept the proposed adapter boundary before any runtime experiment. Proceed only if a second release reuses the evidence and the owner identifies utility beyond existing component checks.

Stop or decline if…

  • Stop if the useful page is an opaque client-rendered shell, requires login, needs security isolation disabled, or exposes non-public CMS or CRM data.

Risks, constraints and unanswered questions

  • Source visibility and browser API access are unresolved until an owner-approved pilot. Linting a declared tool does not prove discovery, correct permissions, successful lookup, or compatibility with any Salesforce agent product.

Source and date ledger

Research reviewed 2026-09-05. Dates describe the source, not a company trial. An unavailable publication date is left unknown.