Skip to content
Embeddable web components
Embeddable web components

Drop a script tag and a custom element on the host page and the Sessions embed renders inside its own Shadow DOM. 9 elements are published today.

How to use

Include the embed's module script once, then place the custom element anywhere on the host page.

<script
  type="module"
  src="https://go.sessions.website/embeds/unstable/schedule.js"
></script>

<sessions-schedule business="still-water-yoga-demo"></sessions-schedule>

AI agent tools on your site

Add the tools attribute to <sessions-context> and your embeds publish their booking capabilities to any AI agent running in the visitor's browser — browsing the schedule, pricing a booking, opening the booking sheet. It is off by default, and while it is off the tool code is never even downloaded.

<script
  type="module"
  src="https://go.sessions.website/embeds/unstable/schedule.js"
></script>

<!-- The `tools` attribute is the opt-in. Without it nothing is
     registered, and the tool code is never downloaded. -->
<sessions-context business="still-water-yoga-demo" tools>
  <sessions-schedule></sessions-schedule>
</sessions-context>

One thing to check on your side: Web MCP is gated by the tools permission, which browsers default to self. A normal page needs no header. If your site sends a restrictive Permissions-Policy, allow tools for your own origin or the registration is rejected.

No tool ever handles a payment instrument. An agent can complete a booking only when your server-side price comes back at zero — a free session, or one covered by a pass the person already holds. Anything owing money opens the booking sheet and stops, for the person to complete.

Web MCP reference

Components