How to Use the Google Drive MCP in CrewAI

Q: How do I assign specific Google Drive tools to individual CrewAI agents?

You define a toolfilter when registering the MCP Server in your crew configuration. This allows you to give your research agent only listfiles while reserving deletefile for your manager agent.

Q: Can CrewAI agents collaborate to resolve conflicts in Google Drive file versions?

Yes, one agent can use listrevisions to pull the edit history while another agent analyzes the differences. They can then agree on the correct changes and apply them using updatefile.

Q: How do CrewAI agents share Google Drive file context with each other?

Agents pass file IDs and metadata retrieved from getfilemetadata through their shared memory. This allows subsequent agents in the crew to perform actions on the exact same files without re-searching.

Deploy a team of specialized CrewAI agents to search, organize, and share your Google Drive documents.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Google Drive MCP to CrewAI

Create your Vinkius account to connect Google Drive to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Google Drive with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Research Google Drive folders using CrewAI teams

The `list_files` tool serves as the primary search mechanism for your research agent within the CrewAI team. While one agent searches for relevant Google Drive project briefs, a second agent uses `get_file_metadata` to analyze which documents are the most recent. That's why this setup keeps your token usage low because CrewAI agents only pass specific Google Drive file summaries to each other. The crew collaborates autonomously to find exactly what you need in Google Drive without manual keyword searching.

Manage document publishing via this MCP Server

The `copy_file` tool allows a template-manager CrewAI agent to duplicate master files whenever a new project starts. A writer CrewAI agent then takes over, using `update_file` to write fresh content directly into the Google Drive copy. Once the content is ready, a coordinator CrewAI agent uses `export_file` to generate a PDF from the Google Drive doc. This multi-step pipeline runs from start to finish without you ever opening a Google Drive browser tab.

Secure your files with CrewAI security agents

The `list_permissions` tool lets a moderator CrewAI agent audit who has access to newly created Google Drive folders. If the crew detects an external email that should not be there, it flags the Google Drive file for review. By executing `create_permission`, the security CrewAI agent restricts the Google Drive file to internal team members. This setup ensures your CrewAI operations remain compliant with corporate Google Drive sharing policies.

Setup guide

Set up Google Drive MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Google Drive tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Google Drive Analyst",
    goal="Access and analyze Google Drive data via MCP.",
    backstory="Expert analyst with direct Google Drive access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Google Drive transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Google Drive Analyst",
        goal="Access and analyze Google Drive data via MCP.",
        backstory="Expert analyst with direct Google Drive access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Google Drive transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Google Drive. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Google Drive now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Google Drive MCP in CrewAI

You define a tool_filter when registering the MCP Server in your crew configuration. This allows you to give your research agent only list_files while reserving delete_file for your manager agent.

Yes, one agent can use list_revisions to pull the edit history while another agent analyzes the differences. They can then agree on the correct changes and apply them using update_file.

Agents pass file IDs and metadata retrieved from get_file_metadata through their shared memory. This allows subsequent agents in the crew to perform actions on the exact same files without re-searching.

You simply add the Vinkius HTTP endpoint to the mcps list in your Agent definition. The framework handles the transport details, exposing all 12 file management tools directly to your crew.

The MCP Server enforces strict tool boundaries, meaning CrewAI agents can only execute the specific actions defined in the tool schemas. Your Google Drive files, permissions, and directory structures are protected by Vinkius's zero-trust sandboxing.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript