How to integrate Nozbe Teams MCP with CrewAI

GET STARTED FOR FREE
Framework Integration Gradient
Nozbe Teams Logo
CrewAI Logo
divider

Introduction

This guide walks you through connecting Nozbe Teams to CrewAI 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 CrewAI 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 Composio API key and configure your Nozbe Teams connection
  • Set up CrewAI with an MCP enabled agent
  • Create a Tool Router session or standalone MCP server for Nozbe Teams
  • Build a conversational loop where your agent can execute Nozbe Teams operations

What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.

Key features include:

  • Agent Roles: Define specialized agents with specific goals and backstories
  • Task Management: Create tasks with clear descriptions and expected outputs
  • Crew Orchestration: Combine agents and tasks into collaborative workflows
  • MCP Integration: Connect to external tools through Model Context Protocol

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:
  • Python 3.9 or higher
  • A Composio account and API key
  • A Nozbe Teams connection authorized in Composio
  • An OpenAI API key for the CrewAI LLM
  • Basic familiarity with Python

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.

Install dependencies

bash
pip install composio crewai crewai-tools[mcp] python-dotenv
What's happening:
  • composio connects your agent to Nozbe Teams via MCP
  • crewai provides Agent, Task, Crew, and LLM primitives
  • crewai-tools[mcp] includes MCP helpers
  • python-dotenv loads environment variables from .env

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID scopes the session to your account
  • OPENAI_API_KEY lets CrewAI use your chosen OpenAI model

Import dependencies

python
import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

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

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")
What's happening:
  • CrewAI classes define agents and tasks, and run the workflow
  • MCPServerHTTP connects the agent to an MCP endpoint
  • Composio will give you a short lived Nozbe Teams MCP URL

Create a Composio Tool Router session for Nozbe Teams

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["nozbe_teams"])

url = session.mcp.url
What's happening:
  • You create a Nozbe Teams only session through Composio
  • Composio returns an MCP HTTP URL that exposes Nozbe Teams tools

Initialize the MCP Server

python
server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )
What's Happening:
  • Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
  • MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
  • Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
  • Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
  • Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.

Create a CLI Chatloop and define the Crew

python
print("Chat started! Type 'exit' or 'quit' to end.\n")

conversation_context = ""

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")
What's Happening:
  • Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
  • Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
  • Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
  • Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
  • Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
  • Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.

Complete Code

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

python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

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.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["nozbe_teams"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\n")

    conversation_context = ""

    while True:
        user_input = input("You: ").strip()

        if user_input.lower() in ["exit", "quit", "bye"]:
            print("\nGoodbye!")
            break

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")

Conclusion

You now have a CrewAI agent connected to Nozbe Teams through Composio's Tool Router. The agent can perform Nozbe Teams operations through natural language commands.

Next steps:

  • Add role-specific instructions to customize agent behavior
  • Plug in more toolkits for multi-app workflows
  • Chain tasks for complex multi-step operations

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

Google ADK

Google ADK

Use Nozbe Teams MCP with Google ADK

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

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 CrewAI?

Yes, you can. CrewAI 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