How to integrate Nozbe Teams MCP with LangChain

This guide walks you through connecting Nozbe Teams to LangChain 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 LangChain 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.

Get started for free Get a demo

Nozbe Teams

Api Key

Nozbe Teams is a cloud-based task management tool for individuals and teams. It helps you organize, track, and manage all your group tasks in one place.

48 Tools

Managed auth

Connect Nozbe Teams without auth hassles

We manage OAuth, API keys, token refresh, and scopes — you just build.

Try for free

Introduction

This guide will help you understand how to give your LangChain 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.

Also integrate Nozbe Teams with

OpenAI Agents SDK Claude Agent SDK Claude Code Claude Cowork Codex OpenClaw Hermes CLI Google ADK Vercel AI SDK Mastra AI LlamaIndex CrewAI

TL;DR

Here's what you'll learn:

Get and set up your OpenAI and Composio API keys
Connect your Nozbe Teams project to Composio
Create a Tool Router MCP session for Nozbe Teams
Initialize an MCP client and retrieve Nozbe Teams tools
Build a LangChain agent that can interact with Nozbe Teams
Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

Agent Framework: Build agents that can use tools and make decisions
MCP Integration: Connect to external services through Model Context Protocol adapters
Memory Management: Maintain conversation history across interactions
Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

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.

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

What is Composio SDK?

Composio's Composio SDK 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 Composio SDK

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

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

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

Step-by-step Guide

Step by step10 STEPS

Prerequisites

Before starting this tutorial, make sure you have:

Python 3.10 or higher installed on your system
A Composio account with an API key
An OpenAI API key
Basic familiarity with Python and async programming

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

npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv

Install the required packages for LangChain with MCP support.

What's happening:

@composio/langchain provides Composio integration for LangChain
@langchain/mcp-adapters enables MCP client connections
@langchain/core is the core agent framework
dotenv/config loads environment variables

Set up environment variables

bash

COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_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 your requests to Composio's API
COMPOSIO_USER_ID identifies the user for session management
OPENAI_API_KEY enables access to OpenAI's language models

Import dependencies

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();

What's happening:

We're importing LangChain's MCP adapter and Composio SDK
The dotenv/config import loads environment variables from your .env file
This setup prepares the foundation for connecting LangChain with Nozbe Teams functionality through MCP

Initialize Composio client

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

What's happening:

We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
Creating a Composio instance that will manage our connection to Nozbe Teams tools
Validating that COMPOSIO_USER_ID is also set before proceeding

Create a Tool Router session

const session = await composio.create(
    userId as string,
    {
        toolkits: ['nozbe_teams']
    }
);

const url = session.mcp.url;

What's happening:

We're creating a Tool Router session that gives your agent access to Nozbe Teams tools
The create method takes the user ID and specifies which toolkits should be available
The returned session.mcp.url is the MCP server URL that your agent will use
This approach allows the agent to dynamically load and use Nozbe Teams tools as needed

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "nozbe_teams-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });

What's happening:

We're creating a MultiServerMCPClient that connects to our Nozbe Teams MCP server via HTTP
The client is configured with a name and the URL from our Tool Router session
getTools() retrieves all available Nozbe Teams tools that the agent can use
We're creating a LangChain agent using the GPT-5 model

Set up interactive chat interface

let conversationHistory: any[] = [];

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

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
});

rl.prompt();

rl.on('line', async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
        console.log("\nGoodbye!");
        rl.close();
        process.exit(0);
    }

    if (!trimmedInput) {
        rl.prompt();
        return;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });

What's happening:

We initialize an empty conversationHistory list to maintain context across interactions
A readline interface is used to continuously accept user input from the command line
When a user types a message, it's added to the conversation history and sent to the agent
The agent processes the request using the invoke() method with the full conversation history
Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully

Run the application

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});

What's happening:

We call the main() function to start the application

Complete Code

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

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['nozbe_teams']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "nozbe_teams-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Nozbe Teams related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    rl.prompt();

    rl.on('line', async (userInput: string) => {
        const trimmedInput = userInput.trim();
        
        if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
            console.log("\nGoodbye!");
            rl.close();
            process.exit(0);
        }
        
        if (!trimmedInput) {
            rl.prompt();
            return;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});

Conclusion

You've successfully built a LangChain agent that can interact with Nozbe Teams through Composio's Tool Router.

Key features of this implementation:

Dynamic tool loading through Composio's Tool Router
Conversation history maintenance for context-aware responses
Async Python provides clean, efficient execution of agent workflows

You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.

TOOLS

Supported Tools

Every Nozbe Teams action and event your agent gets out of the box.

Create Attachment

Tool to add attachment metadata to a comment.

Create Comment

Tool to add a comment to a task in Nozbe Teams.

Create Project Section

Tool to create a new project section in Nozbe Teams.

Create Reminder

Tool to add a reminder to a task in Nozbe Teams.

Create Tag Assignment

Tool to add a tag assignment to a task.

Create Task

Tool to create a new task in Nozbe Teams.

Create Team Member

Tool to add a team member in Nozbe Teams.

Create User

Tool to create a new placeholder user in Nozbe Teams.

Delete Comment

Tool to permanently delete a comment by its ID.

Delete Project

Tool to delete a project in Nozbe Teams by its ID.

Delete Reminder

Tool to delete a reminder by its unique ID.

Delete Tag Assignment

Tool to delete a tag assignment by its ID.

Delete Task

Tool to delete a task in Nozbe Teams by its ID.

Get Attachment

Tool to get attachment metadata by its ID.

Get Comment by ID

Tool to retrieve a comment by its ID from Nozbe Teams.

Get Project by ID

Tool to retrieve a project by its ID from Nozbe Teams.

Get Project Access

Tool to retrieve project access details by ID.

Get Project Section

Tool to retrieve a project section by ID from Nozbe Teams.

Get Reminder

Tool to get a reminder by ID from Nozbe Teams.

Get Tag

Tool to get a tag by ID from Nozbe Teams.

Get Tag Assignment

Tool to retrieve a tag assignment by its ID.

Get Task by ID

Tool to retrieve a task by its ID from Nozbe Teams.

Get Task Event

Tool to get a task event by ID.

Get Team by ID

Tool to retrieve a team by its ID from Nozbe Teams.

Get Team Member by ID

Tool to retrieve a team member by ID from Nozbe Teams.

Get User by ID

Tool to retrieve a user by their ID from Nozbe Teams.

List Comment Attachments

Tool to get all attachments related to a specific comment in Nozbe Teams.

List Comments

Tool to get accessible comments with optional filtering by task_id and pagination support.

List Group Assignments

Tool to get accessible group assignments from Nozbe Teams.

List Project Accesses

Tool to get accessible project accesses in Nozbe Teams.

List Project Groups

Tool to get accessible project groups from Nozbe Teams.

List Projects

Tool to retrieve accessible projects with optional filtering.

List Project Sections

Tool to retrieve accessible project sections with optional filtering.

List Reminders

Tool to get accessible reminders from Nozbe Teams.

List Tag Assignments

Tool to get accessible tag assignments with optional filtering by tag_id or task_id.

List Tags

Tool to get accessible tags from Nozbe Teams.

List Task Events

Tool to get accessible task events from Nozbe Teams.

List Tasks

Tool to retrieve accessible tasks from Nozbe Teams.

List Users

Tool to retrieve accessible users from Nozbe Teams.

Poll for new tasks

Tool to poll for new tasks created since the last call.

Poll Updated Tasks

Tool to poll for tasks that have been updated since the last call.

Update Comment

Tool to update an existing comment in Nozbe Teams.

Update Project

Tool to update a project in Nozbe Teams.

Update Project Access

Tool to update project access permissions in Nozbe Teams.

Update Task

Tool to update a task in Nozbe Teams.

Update Team

Tool to update a team in Nozbe Teams.

Update Team Member

Tool to update a team member in Nozbe Teams.

Update User

Tool to update a user in Nozbe Teams.

FRAMEWORKS

How to build Nozbe Teams MCP Agent with another framework

OpenAI Agents SDK

Use Nozbe Teams MCP with OpenAI Agents SDK

Claude Agent SDK

Use Nozbe Teams MCP with Claude Agent SDK

Claude Code

Use Nozbe Teams MCP with Claude Code

Claude Cowork

Use Nozbe Teams MCP with Claude Cowork

Codex

Use Nozbe Teams MCP with Codex

OpenClaw

Use Nozbe Teams MCP with OpenClaw

Hermes

Use Nozbe Teams MCP with Hermes

CLI

Use Nozbe Teams MCP with CLI

Google ADK

Use Nozbe Teams MCP with Google ADK

Vercel AI SDK

Use Nozbe Teams MCP with Vercel AI SDK

Mastra AI

Use Nozbe Teams MCP with Mastra AI

LlamaIndex

Use Nozbe Teams MCP with LlamaIndex

CrewAI

Use Nozbe Teams MCP with CrewAI

MORE TOOLKITS

Explore Other Toolkits

Toolkit marketplace

Google Sheets

Oauth2

Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly.

Notion

Oauth2Api Key

Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place.

Airtable

Oauth2Api Key

Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations.

Asana

Oauth2

Asana is a collaborative work management platform for teams to organize and track projects. It streamlines teamwork, boosts productivity, and keeps everyone aligned on goals.

FAQ

Frequently asked questions

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.

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

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.

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.

Start with Nozbe Teams.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Nozbe Teams tool your agent needs.Free to start.

Start building

Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREE BOOK A DEMO

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati

Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya

Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave

CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu

Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola

Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche

Co-Founder, Ingram Technologies

How to integrate Nozbe Teams MCP with LangChain

Connect Nozbe Teams without auth hassles

Introduction

Also integrate Nozbe Teams with

TL;DR

What is LangChain?

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

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

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for OpenAI and Composio

Install dependencies

Set up environment variables

Import dependencies

Initialize Composio client

Create a Tool Router session

Configure the agent with the MCP URL

Set up interactive chat interface

Run the application

Complete Code

Conclusion

Supported Tools

How to build Nozbe Teams MCP Agent with another framework

OpenAI Agents SDK

Claude Agent SDK

Claude Code

Claude Cowork

Codex

OpenClaw

Hermes

CLI

Google ADK

Vercel AI SDK

Mastra AI

LlamaIndex

CrewAI

Explore Other Toolkits

Google Sheets

Notion

Airtable

Asana

Frequently asked questions

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

Can I use Tool Router MCP with LangChain?+

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

How safe is my data with Composio Tool Router?+

Start with Nozbe Teams.It takes 30 seconds.

Teams ship real agents on Composio