Introducing MCP Connectors in Beta on GroqCloud
Zero-setup tool use for Google Workspace: faster, easier, and more secure than ever.
Today we’re excited to announce MCP Connectors in Beta on GroqCloud. MCP Connectors are Groq-maintained wrappers for external services (starting with Google Workspace: Gmail, Drive and Calendar). This release builds on top of GroqCloud’s existing remote MCP support, enabling your AI agents to interact with Google Workspace tools via the Responses API, without having to manage your own MCP server.
Built for developers who want powerful AI agents without operational overhead, MCP Connectors deliver drop-in compatibility, zero infrastructure to manage, and Groq’s speed on our secure inference infrastructure.
Why MCP Connectors Matter
The MCP (Model Context Protocol) approach unlocks agentic AI workflows: models interacting with external tools, databases, and services to extend beyond pure text generation. Some external services provide their own MCP server to connect to; many others (such as Google Workspace apps) do not. To use MCP with these services, you have to build, deploy, and manage your own MCP server.
Enter MCP Connectors: a set of pre-built, Groq-hosted MCP servers that interface with various services to provide you all the benefits of MCP without the additional work of building or maintaining servers yourself.
With MCP Connectors on GroqCloud, you get:
- Drop-in Compatibility: If you’re already using OpenAI’s Responses API with a Google Workspace MCP connector, you just switch to GroqCloud and keep the same workflow.
- Zero Deployment Burden: No need to spin up or maintain an MCP server.
- Lower Latency, Lower Cost: Groq’s low-latency inference makes tool-enabled agents feel instantaneous at a cost structure that fuels growth.
- Security: OAuth tokens remain in your control. You handle authentication however you prefer, and those tokens are passed through to Groq's connectors at request time. We never store tokens or retain your Google credentials. Only share credentials with MCP servers you fully trust.
- Tool Use Control: Use allow-lists and approvals to govern which agents can call which tools, keeping governance tight.
What’s Included at Launch
We're starting with Google Workspace: the tools developers use most. At launch, you can connect to Gmail, Google Drive, and Google Calendar through GroqCloud's Responses API on all models that support tool use.
The following table outlines the capabilities and typical use cases for each new connector:
| Connector | Capabilities | Typical Use Cases |
|---|---|---|
Gmail | Search, read, and summarize threads; fetch recent email IDs. | Inbox triage, follow-up drafting, support ticket enrichment. |
Google Calendar | Search events, fetch detailed agendas. | Scheduling copilots, meeting prep, automated recap generators. |
Google Drive | Full-text search, document fetch with smart truncation, recent files listings. | Knowledge retrieval, document QA, internal wiki assistants. |
Once you provide the right OAuth credentials, models on GroqCloud can discover and invoke these Google tools exactly as they would on OpenAI.
Getting Started
- Switch your API endpoint to GroqCloud
- Choose a tool-use supported model
- Include your Google OAuth token in the authorization header
- Call Google Workspace tools via the Responses API
No code changes required if you're already using OpenAI-compatible tool calling.
We’re excited to see the next wave of agentic experiences built with GroqCloud and Google Workspace. Learn more about MCP Connectors on GroqCloud. Interested in additional MCP Connector support on GroqCloud? Reach out to our support team and let us know.