Hubz.

Business / Scoped MCP access

Business MCP and AI client connections

Connect compatible clients to permitted CRM context, with separate review and authorization for private plans and communications.

PRODUCT VIEW

See how it works.

Give a compatible AI client the CRM information it needs to prepare useful recommendations. Choose which modules it can access and keep permissions explicit. Hubz MCP connections support data access and private-plan preparation within authorized modules. Actions with external consequences, such as communication or publishing, are assessed through separate permissions and human approval rather than assumed from the existence of a connection.

Hubz.Workspace / MCP and AI connectionsDK
EXPLORE THE PRODUCT

MCP and AI connections

Sample view
◎
BUSINESS · MCP

MCP and AI connections

1Scope selectionDepends on scope
2Compatible client connectionDepends on scope
3Private-plan preparationDepends on scope
4Human reviewDepends on scope
5Connection and permission managementReview
Content → review → permitted action

An MCP connection alone does not grant permission to send email, launch campaigns or publish social content.

01Choose the connection scope
02Review the plan
03Approve actions separately
Interface illustration using sample data. The layout is simplified to explain the relevant feature.

DETAILED FEATURE GUIDES

Explore the features in this module.

MCP connectionsAuthorize a compatible MCP client through OAuth and review its accessible modules, permission validity and revocation options.MCP private plansReview proposals prepared under explicit planning permission with their content, recipient, cost and validity information.MCP communication approvalsReview an assistant-prepared email or limited campaign request in Hubz, with its sender, recipients and full message visible before approval.MCP mailbox read accessShare limited synced plain-text content from an authorized mailbox through a read-access decision separate from sending permission.

FROM NEED TO OUTCOME

Where this helps.

An assistant may need customer information to prepare a plan without needing permission to contact the customer. If those boundaries are unclear, the team can struggle to track which data was used and which action was approved.

WHAT YOU CAN WORK TOWARDS

Keep context access separate from the action decision when using compatible clients. Review the prepared plan with your team before proceeding.

STEP BY STEP

How to use it.

  1. 01

    Choose the connection scope

    Define which client may use which CRM modules. Authorize the connection explicitly within the relevant user and workspace permissions.

  2. 02

    Review the plan

    Inspect the private plan or recommendation prepared from permitted context. A preparation record is not a message sent to a customer or published content.

  3. 03

    Approve actions separately

    For communication actions, review recipient, content and sender scope. Follow the separate authorization and human-approval steps required by the relevant workflow.

INSIDE THE MODULE

What can you do?

FOCUS 01⊙
MCP and AI connections
Scope●Permission○Review○
Choose the connection scope

Scope selection

Explicitly choose the modules and permissions available to a connection. A connection is not unrestricted access to all workspace data.

FOCUS 02▤
MCP and AI connections
Scope○Permission●Review○
Review the plan

Compatible client connection

Connect a suitable MCP-supporting client to authorized Hubz context. The client’s own account and usage conditions apply separately.

FOCUS 03↗
MCP and AI connections
Scope○Permission○Review●
Approve actions separately

Private-plan preparation

Prepare plan and recommendation records within the granted scope. Let the team review content and supporting context before contacting a customer.

FOCUS 04◇
MCP and AI connections
Scope●Permission○Review○
Choose the connection scope

Human review

Assess recipients, senders and content in explicit review steps for relevant actions. Granting authority and approving a particular action remain different decisions.

FOCUS 05⌁
MCP and AI connections
Scope○Permission●Review○
Review the plan

Connection and permission management

Manage connections and their scopes, revoking permissions where needed. Revoke access when a connection is no longer needed.

IN EVERYDAY WORK

What it looks like in practice.

Business sales operations

A compatible assistant prepares a follow-up plan from permitted customer context without sending the customer communication.

Review the recommendation internally and make the external-action decision separately.

Business management team

The team needs clarity about which modules different connections can read and which actions they may perform.

Manage connection scope and action approvals separately to make control visible.

Scenarios are illustrative; they are not customer testimonials or measured performance claims.

KNOW WHAT IS INCLUDED

Plans, permissions and limits.

MCP connections are available only in Business. Use also requires a compatible client, connection authorization and relevant action permissions.

  • An MCP connection alone does not grant permission to send email, launch campaigns or publish social content.
  • External AI-provider accounts, licenses and consumption charges apply separately.
  • MCP requires a current eligible Business subscription as well as the necessary access permissions.
Compare plans

YOUR QUESTIONS

About this feature.

01Is MCP included in Professional?

No. Professional includes standard connections and sales or marketing operations. MCP and related AI-client connections are reserved for Business.

02Does a connection let an assistant send messages automatically?

No. Data access and plan preparation are separate from external communications. Relevant messaging or publishing follows its own permissions, content review and human-approval steps.

03Does Business include AI consumption?

Business includes the MCP access scope. The compatible client’s account, license and any AI-provider consumption charges are separate from that access.

MODULES THAT WORK TOGETHER

Explore related modules.

01

Customer relationships

Keep contact details, company relationships and past conversations in one shared record.

02

Integrations

Set up email, calendar, task-file and approved communication connections with the correct account, permissions and action scope.

03

Security and team access

Arrange team access through workspace membership, existing roles, enabled modules and connection permissions.