How to integrate Nozbe Teams MCP with Autogen

Framework Integration Gradient
Nozbe Teams Logo
AutoGen Logo
divider

Introduction

This guide walks you through connecting Nozbe Teams to AutoGen 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 AutoGen 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 and set up your OpenAI and Composio API keys
  • Install the required dependencies for Autogen and Composio
  • Initialize Composio and create a Tool Router session for Nozbe Teams
  • Wire that MCP URL into Autogen using McpWorkbench and StreamableHttpServerParams
  • Configure an Autogen AssistantAgent that can call Nozbe Teams tools
  • Run a live chat loop where you ask the agent to perform Nozbe Teams operations

What is AutoGen?

Autogen is a framework for building multi-agent conversational AI systems from Microsoft. It enables you to create agents that can collaborate, use tools, and maintain complex workflows.

Key features include:

  • Multi-Agent Systems: Build collaborative agent workflows
  • MCP Workbench: Native support for Model Context Protocol tools
  • Streaming HTTP: Connect to external services through streamable HTTP
  • AssistantAgent: Pre-built agent class for tool-using assistants

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

You will need:

  • A Composio API key
  • An OpenAI API key (used by Autogen's OpenAIChatCompletionClient)
  • A Nozbe Teams account you can connect to Composio
  • Some basic familiarity with Autogen and Python async

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 python-dotenv
pip install autogen-agentchat autogen-ext-openai autogen-ext-tools

Install Composio, Autogen extensions, and dotenv.

What's happening:

  • composio connects your agent to Nozbe Teams via MCP
  • autogen-agentchat provides the AssistantAgent class
  • autogen-ext-openai provides the OpenAI model client
  • autogen-ext-tools provides MCP workbench support

Set up environment variables

bash
COMPOSIO_API_KEY=your-composio-api-key
OPENAI_API_KEY=your-openai-api-key
USER_ID=your-user-identifier@example.com

Create a .env file in your project folder.

What's happening:

  • COMPOSIO_API_KEY is required to talk to Composio
  • OPENAI_API_KEY is used by Autogen's OpenAI client
  • USER_ID is how Composio identifies which user's Nozbe Teams connections to use

Import dependencies and create Tool Router session

python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio

from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient
from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams

load_dotenv()

async def main():
    # Initialize Composio and create a Nozbe Teams session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["nozbe_teams"]
    )
    url = session.mcp.url
What's happening:
  • load_dotenv() reads your .env file
  • Composio(api_key=...) initializes the SDK
  • create(...) creates a Tool Router session that exposes Nozbe Teams tools
  • session.mcp.url is the MCP endpoint that Autogen will connect to

Configure MCP parameters for Autogen

python
# Configure MCP server parameters for Streamable HTTP
server_params = StreamableHttpServerParams(
    url=url,
    timeout=30.0,
    sse_read_timeout=300.0,
    terminate_on_close=True,
    headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")}
)

Autogen expects parameters describing how to talk to the MCP server. That is what StreamableHttpServerParams is for.

What's happening:

  • url points to the Tool Router MCP endpoint from Composio
  • timeout is the HTTP timeout for requests
  • sse_read_timeout controls how long to wait when streaming responses
  • terminate_on_close=True cleans up the MCP server process when the workbench is closed

Create the model client and agent

python
# Create model client
model_client = OpenAIChatCompletionClient(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY")
)

# Use McpWorkbench as context manager
async with McpWorkbench(server_params) as workbench:
    # Create Nozbe Teams assistant agent with MCP tools
    agent = AssistantAgent(
        name="nozbe_teams_assistant",
        description="An AI assistant that helps with Nozbe Teams operations.",
        model_client=model_client,
        workbench=workbench,
        model_client_stream=True,
        max_tool_iterations=10
    )

What's happening:

  • OpenAIChatCompletionClient wraps the OpenAI model for Autogen
  • McpWorkbench connects the agent to the MCP tools
  • AssistantAgent is configured with the Nozbe Teams tools from the workbench

Run the interactive chat loop

python
print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
print("Ask any Nozbe Teams related question or task to the agent.\n")

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

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

    if not user_input:
        continue

    print("\nAgent is thinking...\n")

    # Run the agent with streaming
    try:
        response_text = ""
        async for message in agent.run_stream(task=user_input):
            if hasattr(message, "content") and message.content:
                response_text = message.content

        # Print the final response
        if response_text:
            print(f"Agent: {response_text}\n")
        else:
            print("Agent: I encountered an issue processing your request.\n")

    except Exception as e:
        print(f"Agent: Sorry, I encountered an error: {str(e)}\n")
What's happening:
  • The script prompts you in a loop with You:
  • Autogen passes your input to the model, which decides which Nozbe Teams tools to call via MCP
  • agent.run_stream(...) yields streaming messages as the agent thinks and calls tools
  • Typing exit, quit, or bye ends the loop

Complete Code

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

python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio

from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient
from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams

load_dotenv()

async def main():
    # Initialize Composio and create a Nozbe Teams session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["nozbe_teams"]
    )
    url = session.mcp.url

    # Configure MCP server parameters for Streamable HTTP
    server_params = StreamableHttpServerParams(
        url=url,
        timeout=30.0,
        sse_read_timeout=300.0,
        terminate_on_close=True,
        headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")}
    )

    # Create model client
    model_client = OpenAIChatCompletionClient(
        model="gpt-5",
        api_key=os.getenv("OPENAI_API_KEY")
    )

    # Use McpWorkbench as context manager
    async with McpWorkbench(server_params) as workbench:
        # Create Nozbe Teams assistant agent with MCP tools
        agent = AssistantAgent(
            name="nozbe_teams_assistant",
            description="An AI assistant that helps with Nozbe Teams operations.",
            model_client=model_client,
            workbench=workbench,
            model_client_stream=True,
            max_tool_iterations=10
        )

        print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
        print("Ask any Nozbe Teams related question or task to the agent.\n")

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

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

            if not user_input:
                continue

            print("\nAgent is thinking...\n")

            # Run the agent with streaming
            try:
                response_text = ""
                async for message in agent.run_stream(task=user_input):
                    if hasattr(message, 'content') and message.content:
                        response_text = message.content

                # Print the final response
                if response_text:
                    print(f"Agent: {response_text}\n")
                else:
                    print("Agent: I encountered an issue processing your request.\n")

            except Exception as e:
                print(f"Agent: Sorry, I encountered an error: {str(e)}\n")

if __name__ == "__main__":
    asyncio.run(main())

Conclusion

You now have an Autogen assistant wired into Nozbe Teams through Composio's Tool Router and MCP. From here you can:
  • Add more toolkits to the toolkits list, for example notion or hubspot
  • Refine the agent description to point it at specific workflows
  • Wrap this script behind a UI, Slack bot, or internal tool
Once the pattern is clear for Nozbe Teams, you can reuse the same structure for other MCP-enabled apps with minimal code changes.

How to build Nozbe Teams MCP Agent with another framework

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

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