WebMCP Embed Script

Drop a single <script> tag into your website so visitors' AI assistants can evaluate your deployed rules directly in the browser, via WebMCP.

Prerequisites: A deployment (Exporting Rules for Deployment) and the ability to edit your site's HTML

When to Use This

Use the WebMCP embed when you want your website itself to offer your rules as tools — e.g. an eligibility checker or a contract clause evaluator that a visitor's browser-side AI agent can call without any backend integration on their part. The script registers your deployment's rules as WebMCP tools scoped to the page.

For server-side or agent integrations, use the MCP server or OpenAPI spec instead.

The Script

Legalese Cloud:

<script
  src="https://api.legalese.cloud/.webmcp/embed.js"
  data-org="{orgSlug}"
  data-scope="*"
  data-tools="auto"
  data-api-key="sk_..."
></script>

Self-hosted jl4-service:

<script
  src="http://{serviceUrl}/.webmcp/embed.js"
  data-scope="*"
  data-tools="auto"
  data-api-key="sk_..."
></script>

The VS Code Integrate dialog pre-fills the correct src for your connection.

Attributes

Attribute	Meaning
`src`	The WebMCP loader served by Legalese Cloud / your jl4-service
`data-org`	Your organization slug on Legalese Cloud (hosted snippet only, see below)
`data-scope`	Which deployments the tools cover (`` = all, `insurance-premium/` = one)
`data-tools`	Comma-separated list of tool categories to register (default: `auto`)
`data-api-key`	A Legalese Cloud API key authorizing rule evaluation

Tool categories (`data-tools`)

data-tools is not a per-rule allow-list — it selects which categories of tools the script registers:

Category	Registers
`rules`	One tool per exported rule (direct evaluation)
`rule-tools`	The discovery tools `search_rules`, `get_rule_schema`, `evaluate_rule`
`file-tools`	`list_files`, `read_file`, `search_identifier`, `search_text` (browse L4 source)
`auto`	`rules` if the scope has at most 10 exported rules, otherwise `rule-tools`
`all`	`rules` + `rule-tools` + `file-tools`

You can combine categories, e.g. data-tools="rules,file-tools".

Note: the self-hosted embed.js reads only data-api-key, data-scope, and data-tools. data-org applies to the hosted Legalese Cloud snippet only — a self-hosted service already knows its own deployments.

Getting an API Key

Replace sk_... with a real key:

Open the Legalese Cloud console.
Create an API key scoped to the deployment (or organization) you are embedding and with l4:rules and l4:evaluate permissions.
Paste your organization slug into data-org and your API key into data-api-key.

Legalese Cloud Permissions

Permission	Enables
`l4:rules`	The embed script registers each exported rule as a WebMCP tool the visitor's on-page agent can see.
`l4:evaluate`	The agent can actually run a rule and get its decision back.

Deliberately omit l4:read here: the browser only needs to discover and call the rules, not download their full source/schema. And because the key ships in client-side HTML, scope it to rule evaluation only, restrict it to this deployment, and rotate it if exposed. Treat it like a publishable key, not a secret.

Verify

Load a page that includes the script and open a WebMCP-aware assistant. Your exported rules appear as available tools; invoking one runs the deployed rule and returns its typed decision.

Notes

data-tools="auto" keeps the tool list in sync with redeploys.
A self-hosted jl4-service serves the loader at http://{serviceUrl}/.webmcp/embed.js.