Google Expands Gemini Third-Party App Integrations as Pressure Mounts Over Model Context Protocol Support

Google is expanding the capabilities of its Gemini AI assistant by adding direct integration for a fresh wave of third-party applications and services. For months, users and industry observers have noted that Google has moved relatively slowly when it comes to embedding outside software directly into its flagship conversational AI. While the tech giant previously introduced support for the Model Context Protocol, that advanced feature has largely remained restricted to developer tools, command-line interfaces, and enterprise environments, leaving everyday users waiting for native, consumer-facing connections.

To help bridge this gap, Google has steadily rolled out direct, app-level integrations within Gemini over the last several months. Building upon a previous wave of additions that brought tools like Granola, Otter.ai, Ticketmaster, and Wix into the fold, the latest update widens the ecosystem further. Starting today, users can link Gemini directly with a variety of productivity and workflow platforms, including Airtable, Linear, Wispr AI, and Adobe, among others.

This ongoing expansion is designed to make Gemini a more versatile daily driver for professionals and casual users alike, allowing the AI to pull in relevant information and interact directly with the software people already use to manage their work. For instance, individuals who rely on specialized tools like Wispr Flow’s Notetaker to capture, record, and transcribe meetings can now leverage the new Wispr AI integration. By connecting the two, a user can prompt Gemini to fetch the notes from their most recent meeting and automatically extract relevant action items to populate their personal to-do list.

Similarly, the new integration with Airtable unlocks powerful database management capabilities right inside the chat interface. Users can instruct Gemini to query their Airtable bases to surface pending tasks, upcoming project deadlines, and other critical data without ever having to manually open the application, switch browser tabs, or dig through complex spreadsheets.

For those looking to take advantage of these new connections, accessing them is straightforward. The newly supported applications can be located and enabled within the Connected Apps section found inside Gemini’s settings menu. Alternatively, users can bypass the menus entirely during an active conversation by summoning a specific app directly in the chat window simply by typing the @ symbol followed by the service name. This streamlined approach aims to weave Gemini more deeply into existing daily workflows, transforming the assistant from a standalone chat window into a centralized hub for cross-platform productivity.

Google Needs to Open Gemini’s MCP Support

While the addition of these new third-party applications represents a welcome step forward for the Gemini ecosystem, the app-by-app integration strategy remains inherently slow and difficult to scale. Relying on engineers to custom-build and release individual integrations for every popular software service on the market means that users will inevitably face gaps where their preferred tools are left unsupported.

This bottleneck is particularly glaring because Gemini already possesses underlying support for the Model Context Protocol. Despite this technical capability, custom MCP apps continue to be restricted primarily to eligible personal accounts located within the United States. Widely opening up MCP support to the broader public would fundamentally change the dynamic, instantly granting users the freedom to connect a vast array of custom apps and services all at once, rather than waiting for official, trickle-down integrations from Google.

Competing AI ecosystems have already embraced broader protocol access. Both Anthropic’s Claude and OpenAI’s ChatGPT utilize the Model Context Protocol to seamlessly integrate with hundreds of third-party apps, services, and developer environments out of the box. Because of this open approach, those platforms can adapt to niche software stacks and specialized professional needs much faster than Gemini can through individual corporate partnerships.

Google’s current measured approach ultimately limits Gemini’s long-term utility for power users, particularly if the assistant fails to support an obscure or specialized app that an individual relies on for their daily livelihood. Expanding broader access to MCP support would immediately solve this dilemma, giving millions of users a standardized way to bridge the gap between Gemini and their preferred digital tools. Interestingly, the framework for broader connectivity already exists within Google’s broader ecosystem, as Gemini Spark currently supports custom MCP endpoints, proving that the underlying infrastructure is capable of handling a wide variety of third-party software connections when permitted to do so.