Prepare the website
Use an eligible Bloom-hosted website on a connected domain. Confirm the workspace’s assistant-access readiness.
Let compatible assistants work with supported public website information and explicitly enabled capabilities. Keep the connection scoped to the website and the actions you choose.
Planned capability. These connections are not available yet.
Use an eligible Bloom-hosted website on a connected domain. Confirm the workspace’s assistant-access readiness.
Enable only the supported website capabilities and form destinations your business wants to offer.
Let approved inquiries reach the configured destination, with the required consent and downstream controls intact.
Start with your website and its approved business information. Website hosting and scoped MCP access each have their own setup. Try the website setup →
Choose a use case to see the steps, the outcome, and what you need to get started.
A scoped connection for supported website capabilities.
Eligible site, workspace enablement, compatible client, configured permissions.
See how the pieces connect. Open a group below for the tools, details, and where to find them.
Discover the capabilities you choose to expose.
Prepare an eligible Bloom-hosted website and connected domain before enabling its assistant access.
Website → MCPEnable supported public website tools and intended form destinations. The connection is scoped to those capabilities.
MCP settingsUse the supported connection instructions in a compatible assistant. Availability is checked for the site and workspace.
Assistant access setupSupported lead actions follow the configured form destination and consent requirements.
Website tool → Lead destinationPublic website capability does not expose all CRM records or grant cross-company permissions.
Website scopeMCP does not automatically enable a chat widget or authorize a payment. Concierge and transactional flows have their own setup.
MCP · ConciergeWebsite MCP is an included capability where eligible, not a promise of unrestricted assistant access. Hosted-site requirements differ from an external-site Concierge embed.
See the starting price, then check the allowances and any extra costs. Your accepted offer confirms the final scope.
Compare all Bloom plans ↗The website catalog includes MCP capability. Activation depends on site and workspace readiness and supported tool configuration.
Concierge, optional services, and applicable usage remain separate. Compatibility with a named assistant does not imply a partnership or unrestricted access.Open any item for the details.
Eligible website hosting, connected domain, and workspace enablement are required.
Concierge and consequential transaction capabilities are not automatically activated by the connection.
USD · Catalog and Bloom Build Plans & Services checked October 5, 2026. Your accepted offer governs billing and activation.
It is a standard way for an AI assistant to discover and use supported tools. Bloom scopes those tools to the configured website capabilities.
Do not assume that. The website flow can support approved lead handoff with consent; payment and other consequential actions need their own supported flow and authorization.
Bloom website assistant access requires an eligible Bloom-hosted website and a connected domain. An external site can have a Concierge embed without meeting that MCP requirement.
Walk through your people, processes, and priorities with the Bloom team.