Hubz.

Business / Client, workspace and OAuth consent

Connect MCP clients to authorized Hubz CRM data

Authorize a compatible MCP client through OAuth and review its accessible modules, permission validity and revocation options.

PRODUCT VIEW

See how it works.

Connect a compatible MCP client to the Hubz data you authorize it to use. During setup, add Hubz’s remote MCP address to the client, sign in to Hubz and choose the correct workspace before reviewing requested access. The connection list keeps the client name, creation and last-use information and granted scopes visible. CRM reading, private planning, social drafts and communication are different permissions; a request for new access requires a new consent decision.

Hubz.Workspace / MCP connectionsDK
EXPLORE THE PRODUCT

MCP connections

Sample view
◎
BUSINESS · MCP

MCP connections

1OAuth setupDepends on scope
2Module-specific CRM scopeDepends on scope
3Separation of plans and actionsDepends on scope
4Validity and renewalDepends on scope
5Permission revocationReview
Content → review → permitted action

Custom-connector or remote-MCP support depends on the client’s own service and product conditions.

01Start client setup.
02Review workspace and scope.
03Manage the connection.
Interface illustration using sample data. The layout is simplified to explain the relevant feature.

FROM NEED TO OUTCOME

Where this helps.

Connecting an assistant without explicit data and operation boundaries can create an expectation of excessive authority. Assuming an old connection automatically gains new capabilities also makes the permission decision invisible.

WHAT YOU CAN WORK TOWARDS

Know which client is connected to which workspace and with what scope. Manage permission validity, renewal requirements and revocation as parts of the connection lifecycle.

STEP BY STEP

How to use it.

  1. 01

    Start client setup.

    Add Hubz’s remote MCP address in a compatible client and use supported OAuth authorization.

  2. 02

    Review workspace and scope.

    In the Hubz session, select the correct workspace and explicitly assess CRM modules, plan types and any separate communication requests.

  3. 03

    Manage the connection.

    Check granted permissions, usage and expiry information, and renew or revoke the connection when needed.

INSIDE THE MODULE

What can you do?

FOCUS 01⊙
MCP connections
Scope●Permission○Review○
Start client setup.

OAuth setup

Create a connection with user consent through the supported workflow without manually sharing an API key.

FOCUS 02▤
MCP connections
Scope○Permission●Review○
Review workspace and scope.

Module-specific CRM scope

Define which CRM areas the client can read through a connection-specific permission decision.

FOCUS 03↗
MCP connections
Scope○Permission○Review●
Manage the connection.

Separation of plans and actions

Do not treat private planning, mail reading and external communication as one permission.

FOCUS 04◇
MCP connections
Scope●Permission○Review○
Start client setup.

Validity and renewal

Check visible permission expiry and renewal guidance to manage continued access deliberately.

FOCUS 05⌁
MCP connections
Scope○Permission●Review○
Review workspace and scope.

Permission revocation

Remove the relevant connection to invalidate its existing access and refresh tokens.

IN EVERYDAY WORK

What it looks like in practice.

Business workspace user

Allowing an assistant to prepare work by reading only selected CRM modules.

The correct workspace and modules are explicitly approved, and later access requests are assessed through new consent.

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

KNOW WHAT IS INCLUDED

Plans, permissions and limits.

MCP is available only on Business. Authorize each connection for the appropriate workspace and permissions, and review actions requiring separate approval. An earlier authorization does not remove the requirement for an eligible Business subscription.

  • Custom-connector or remote-MCP support depends on the client’s own service and product conditions.
  • An existing connection does not automatically gain new CRM or planning permissions.
  • Creating the connection does not give unlimited permission to send email, start campaigns or publish social content.
Compare plans

YOUR QUESTIONS

About this feature.

01Can I use MCP with Professional?

MCP requires Business. Mail and social-provider connections follow their own plan and permission rules.

02What happens when a connection is removed?

That connection’s access and refresh tokens become invalid. Provider accounts may have separate permission-revocation procedures.

RELATED WORKFLOW GUIDES

You may also need these features.

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.

MODULES THAT WORK TOGETHER

Explore related modules.

01

Integrations

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

02

MCP and AI connections

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

03

Security and team access

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