Gemini in Workspace now connects to Asana, Salesforce, HubSpot and four more business tools via MCP
Google has added seven MCP-powered integrations to Gemini in Workspace, letting users query Salesforce, HubSpot, QuickBooks and more without leaving Google apps.
Google has rolled out seven third-party integrations for Gemini in Workspace, connecting it directly to Asana, Atlassian Rovo, HubSpot, Intuit Mailchimp, Intuit QuickBooks, Monday.com, and Salesforce. The connections are built on the Model Context Protocol (MCP), the open standard that lets AI models call external APIs and retrieve structured data in a consistent, secure way.
For anyone who has spent time copying pipeline data out of Salesforce into a Google Doc, or flipping between QuickBooks and Sheets to reconcile figures, the practical upshot is simple: you can stop doing that.
What the integrations actually do
Each of the seven connectors covers a distinct slice of business operations:
- Asana and Monday.com: query and manage project tasks and team workflows
- Atlassian Rovo: tap into organisation-wide search and knowledge, surfacing insights from across your Atlassian tools
- HubSpot and Salesforce: bring CRM, client, and sales pipeline data directly into your conversation with Gemini
- Intuit Mailchimp: check campaign performance and audience data without leaving your inbox
- Intuit QuickBooks: pull up expenses, financial summaries, and business data on demand
Together they span a fairly complete operational picture: project delivery, customer relationships, marketing, and finance. That breadth feels deliberate rather than coincidental.
Where it shows up
Once enabled, the connectors are accessible through the Gemini side panel inside Docs, Sheets, and Slides, and through Google Chat. You can ask natural language questions like “What does my open Salesforce pipeline look like right now?” and Gemini will pull in the answer without requiring you to authenticate elsewhere, copy data, or open a new tab.
The interaction respects the permissions your administrator has set, so users only see what they are authorised to see in the source system.
What this means for you
If you are an end user with a Gemini for Google Workspace licence, these connectors are on by default. You do not need to request access or install anything separately. You will find third-party connector options in the Gemini side panel the next time you open Docs, Sheets, or Slides, or when you use Gemini in Google Chat. Bear in mind that some integrations require an active subscription to the third-party service itself, in addition to your Workspace licence.
If you are an IT administrator, the more pressing point is that these connectors are enabled by default across your organisation. If you need to restrict access for specific teams, departments, or users, you will want to review your settings promptly. The admin control path is Apps > Google Workspace > Gemini for Workspace > Third-Party Connectors, where you can manage access at the domain, organisational unit, or group level. Users can also manage their own connections individually through Google Account security settings, under “Your connections to third-party apps and services.” Removing a connection there stops data sharing between Gemini and that integration immediately.
The feature is available on both Rapid Release and Scheduled Release domains from September 2026.
Why MCP matters here
The Model Context Protocol is worth understanding briefly, because it is what makes this approach different from older-style integrations. Rather than building a bespoke connector for every combination of app and AI model, MCP provides a shared standard that any compliant tool can use to expose its data to any compliant AI. Google has been building out its Workspace MCP Server for developers since earlier in 2026, and these seven integrations are the first significant consumer-facing result of that investment.
The practical consequence is that adding the eighth or ninth integration should be considerably less work than adding the first. That matters for the pace at which this list is likely to grow.
The broader picture
Microsoft has been running a comparable play inside Teams, where third-party agents surface directly in the admin centre rather than requiring separate configuration. Both companies are making the same bet: that enterprise users will consolidate around whichever productivity platform becomes the connective layer for everything else, rather than switching between dedicated applications.
That is a reasonable bet. The friction of context-switching is real, and reducing it has measurable effects on how quickly people can do their work. Whether Google or Microsoft wins that particular argument matters less to most organisations than whether the integrations they rely on are available, reliable, and properly governed.
For now, if your organisation uses Salesforce, HubSpot, Asana, Monday.com, Atlassian, Mailchimp, or QuickBooks alongside Google Workspace, there is a concrete efficiency case for testing these connectors. The admin governance question is equally concrete: check your Third-Party Connectors settings before your users do.