How to integrate Nozbe Teams MCP with Google ADK

GET STARTED FOR FREE
Framework Integration Gradient
Nozbe Teams Logo
Google ADK Logo
divider

Introduction

This guide walks you through connecting Nozbe Teams to Google ADK using the Composio tool router. By the end, you'll have a working Nozbe Teams agent that can create a new project called 'q3 planning', assign all overdue tasks to sarah, list incomplete tasks in marketing project through natural language commands.

This guide will help you understand how to give your Google ADK agent real control over a Nozbe Teams account through Composio's Nozbe Teams MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

TL;DR

Here's what you'll learn:
  • Get a Nozbe Teams account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Nozbe Teams
  • Build an agent that connects to Nozbe Teams through MCP
  • Interact with Nozbe Teams using natural language

What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.

Key features include:

  • Gemini Integration: Native support for Google's Gemini models
  • MCP Toolset: Built-in support for Model Context Protocol tools
  • Streamable HTTP: Connect to external services through streamable HTTP
  • CLI and Web UI: Run agents via command line or web interface

What is the Nozbe Teams MCP server, and what's possible with it?

The Nozbe Teams MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Nozbe Teams account. It provides structured and secure access so your agent can perform Nozbe Teams operations on your behalf.

Supported Tools & Triggers

Tools
Create AttachmentTool to add attachment metadata to a comment.
Create CommentTool to add a comment to a task in Nozbe Teams.
Create Project SectionTool to create a new project section in Nozbe Teams.
Create ReminderTool to add a reminder to a task in Nozbe Teams.
Create Tag AssignmentTool to add a tag assignment to a task.
Create TaskTool to create a new task in Nozbe Teams.
Create Team MemberTool to add a team member in Nozbe Teams.
Create UserTool to create a new placeholder user in Nozbe Teams.
Delete CommentTool to permanently delete a comment by its ID.
Delete ProjectTool to delete a project in Nozbe Teams by its ID.
Delete ReminderTool to delete a reminder by its unique ID.
Delete Tag AssignmentTool to delete a tag assignment by its ID.
Delete TaskTool to delete a task in Nozbe Teams by its ID.
Get AttachmentTool to get attachment metadata by its ID.
Get Comment by IDTool to retrieve a comment by its ID from Nozbe Teams.
Get Project by IDTool to retrieve a project by its ID from Nozbe Teams.
Get Project AccessTool to retrieve project access details by ID.
Get Project SectionTool to retrieve a project section by ID from Nozbe Teams.
Get ReminderTool to get a reminder by ID from Nozbe Teams.
Get TagTool to get a tag by ID from Nozbe Teams.
Get Tag AssignmentTool to retrieve a tag assignment by its ID.
Get Task by IDTool to retrieve a task by its ID from Nozbe Teams.
Get Task EventTool to get a task event by ID.
Get Team by IDTool to retrieve a team by its ID from Nozbe Teams.
Get Team Member by IDTool to retrieve a team member by ID from Nozbe Teams.
Get User by IDTool to retrieve a user by their ID from Nozbe Teams.
List Comment AttachmentsTool to get all attachments related to a specific comment in Nozbe Teams.
List CommentsTool to get accessible comments with optional filtering by task_id and pagination support.
List Group AssignmentsTool to get accessible group assignments from Nozbe Teams.
List Project AccessesTool to get accessible project accesses in Nozbe Teams.
List Project GroupsTool to get accessible project groups from Nozbe Teams.
List ProjectsTool to retrieve accessible projects with optional filtering.
List Project SectionsTool to retrieve accessible project sections with optional filtering.
List RemindersTool to get accessible reminders from Nozbe Teams.
List Tag AssignmentsTool to get accessible tag assignments with optional filtering by tag_id or task_id.
List TagsTool to get accessible tags from Nozbe Teams.
List Task EventsTool to get accessible task events from Nozbe Teams.
List TasksTool to retrieve accessible tasks from Nozbe Teams.
List UsersTool to retrieve accessible users from Nozbe Teams.
Poll for new tasksTool to poll for new tasks created since the last call.
Poll Updated TasksTool to poll for tasks that have been updated since the last call.
Update CommentTool to update an existing comment in Nozbe Teams.
Update ProjectTool to update a project in Nozbe Teams.
Update Project AccessTool to update project access permissions in Nozbe Teams.
Update TaskTool to update a task in Nozbe Teams.
Update TeamTool to update a team in Nozbe Teams.
Update Team MemberTool to update a team member in Nozbe Teams.
Update UserTool to update a user in Nozbe Teams.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • A Google API key for Gemini models
  • A Composio account and API key
  • Python 3.9 or later installed
  • Basic familiarity with Python

Getting API Keys for Google and Composio

Google API Key
  • Go to Google AI Studio and create an API key.
  • Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
  • Log in to the Composio dashboard.
  • Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
  • Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.

Install dependencies

bash
pip install google-adk composio python-dotenv

Inside your virtual environment, install the required packages.

What's happening:

  • google-adk is Google's Agents Development Kit
  • composio connects your agent to Nozbe Teams via MCP
  • python-dotenv loads environment variables

Set up ADK project

bash
adk create my_agent

Set up a new Google ADK project.

What's happening:

  • This creates an agent folder with a root agent file and .env file

Set environment variables

bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email

Save all your credentials in the .env file.

What's happening:

  • GOOGLE_API_KEY authenticates with Google's Gemini models
  • COMPOSIO_API_KEY authenticates with Composio
  • COMPOSIO_USER_ID identifies the user for session management

Import modules and validate environment

python
import os
import warnings

from composio import Composio
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")
What's happening:
  • os reads environment variables
  • Composio is the main Composio SDK client
  • GoogleProvider declares that you are using Google ADK as the agent runtime
  • Agent is the Google ADK LLM agent class
  • McpToolset lets the ADK agent call MCP tools over HTTP

Create Composio client and Tool Router session

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["nozbe_teams"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url,
print(f"Composio MCP URL: {COMPOSIO_MCP_URL}")
What's happening:
  • Authenticates to Composio with your API key
  • Declares Google ADK as the provider
  • Spins up a short-lived MCP endpoint for your user and selected toolkit
  • Stores the MCP HTTP URL for the ADK MCP integration

Set up the McpToolset and create the Agent

python
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Nozbe Teams operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
What's happening:
  • Connects the ADK agent to the Composio MCP endpoint through McpToolset
  • Uses Gemini as the model powering the agent
  • Lists exact tool names in instruction to reduce misnamed tool calls

Run the agent

bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web

Execute the agent from the project root. The web command opens a web portal where you can chat with the agent.

What's happening:

  • adk run runs the agent in CLI mode
  • adk web . opens a web UI for interactive testing

Complete Code

Here's the complete code to get you started with Nozbe Teams and Google ADK:

python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()
warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["nozbe_teams"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url


composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Nozbe Teams operations."
    ),  
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")

Conclusion

You've successfully integrated Nozbe Teams with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Nozbe Teams using natural language commands.

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Nozbe Teams tools
  • Environment variables keep your credentials secure and separate from code
  • Clear agent instructions reduce tool calling errors
  • The ADK web UI provides an interactive interface for testing and development

You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

How to build Nozbe Teams MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Nozbe Teams MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Nozbe Teams MCP with Claude Agent SDK

LangChain

LangChain

Use Nozbe Teams MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Nozbe Teams MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Nozbe Teams MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Nozbe Teams MCP with LlamaIndex

CrewAI

CrewAI

Use Nozbe Teams MCP with CrewAI

Claude Code

Claude Code

Use Nozbe Teams MCP with Claude Code

Codex

Codex

Use Nozbe Teams MCP with Codex

FAQ

What are the differences in Tool Router MCP and Nozbe Teams MCP?

With a standalone Nozbe Teams MCP server, the agents and LLMs can only access a fixed set of Nozbe Teams tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Nozbe Teams and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Google ADK?

Yes, you can. Google ADK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Nozbe Teams tools.

Can I manage the permissions and scopes for Nozbe Teams while using Tool Router?

Yes, absolutely. You can configure which Nozbe Teams scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Nozbe Teams data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free