Platform/MCP & assistant access
WEBSITE MCP & ASSISTANT ACCESS

Make your website useful
to an AI assistant, too.

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.

Explore the workflow ↓
Illustrative product views · Northstar Home · Sample dataTry the tabs above ↗

A preview of planned customer API, CLI and agent access.

Planned capability. These connections are not available yet.

FROM START TO NEXT STEP

Open a useful, carefully scoped connection.

01

Prepare the website

Use an eligible Bloom-hosted website on a connected domain. Confirm the workspace’s assistant-access readiness.

02

Choose capabilities

Enable only the supported website capabilities and form destinations your business wants to offer.

03

Review the outcome

Let approved inquiries reach the configured destination, with the required consent and downstream controls intact.

FOLLOW THE WORK, STEP BY STEP

Follow a real workflow.

Choose a use case to see the steps, the outcome, and what you need to get started.

Website to assistant access

Expose only the tools the business intends to offer.

  1. 01Prepare hosted site
  2. 02Connect the domain
  3. 03Choose supported tools
  4. 04Configure the destination
  5. 05Connect the assistant
What you leave with

A scoped connection for supported website capabilities.

What you need to start

Eligible site, workspace enablement, compatible client, configured permissions.

Workflow illustration · The product views above show the interface.
INSIDE MCP & ASSISTANT ACCESS

Your website, ready for a different kind of visitor.

See how the pieces connect. Open a group below for the tools, details, and where to find them.

A trusted starting point

Approved contentYour public business information
Supported toolsOnly what you enable
DomainAn eligible connected website

Let an assistant help

WebsiteAssistant

Discover the capabilities you choose to expose.

Keep the handoff clear

InquirySupported form or request
DestinationConfigured business workflow
Consent & permissionsThe same downstream controls
01Set the context02Prepare the work03Review the next step
Illustrative workflow · sample data. Available tools depend on your plan, role, and setup.
01Make approved website tools discoverableConnect a compatible assistant to a specific capability.3 tools

Eligible website context

Prepare an eligible Bloom-hosted website and connected domain before enabling its assistant access.

Website → MCP

Selected capabilities

Enable supported public website tools and intended form destinations. The connection is scoped to those capabilities.

MCP settings

Client connection

Use the supported connection instructions in a compatible assistant. Availability is checked for the site and workspace.

Assistant access setup
02Keep the handoff explicitA tool connection is not a blanket authorization.3 tools

Inquiry routing

Supported lead actions follow the configured form destination and consent requirements.

Website tool → Lead destination

Separate public and internal access

Public website capability does not expose all CRM records or grant cross-company permissions.

Website scope

Independent activation

MCP does not automatically enable a chat widget or authorize a payment. Concierge and transactional flows have their own setup.

MCP · Concierge
SCOPE & AVAILABILITY

Website MCP is an included capability where eligible, not a promise of unrestricted assistant access. Hosted-site requirements differ from an external-site Concierge embed.

PLANS & SCOPE

A capability of eligible website hosting.

See the starting price, then check the allowances and any extra costs. Your accepted offer confirms the final scope.

Compare all Bloom plans ↗
Start hereFind your fit
With eligible website hosting
Included capability

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.

Scope, allowances & extra costs

Open any item for the details.

Website MCP capabilityIncluded where eligible

Eligible website hosting, connected domain, and workspace enablement are required.

Other products & usageSeparately agreed

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.

THE DETAILS THAT MATTER

Good questions.
Clear answers.

What does MCP mean in plain language?+

It is a standard way for an AI assistant to discover and use supported tools. Bloom scopes those tools to the configured website capabilities.

Does this let an assistant take payments?+

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.

Does it work for every external website?+

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.

LET’S MAP IT TO YOUR BUSINESS

Show us the work.
We’ll help connect it.

Walk through your people, processes, and priorities with the Bloom team.