How to integrate Nozbe Teams MCP with Mastra AI

GET STARTED FOR FREE
Framework Integration Gradient
Nozbe Teams Logo
Mastra AI Logo
divider

Introduction

This guide walks you through connecting Nozbe Teams to Mastra AI 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 Mastra AI 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:
  • Set up your environment so Mastra, OpenAI, and Composio work together
  • Create a Tool Router session in Composio that exposes Nozbe Teams tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Nozbe Teams tool definitions and attach them as a toolset
  • Build a Mastra agent that can reason, call tools, and return structured results
  • Run an interactive CLI where you can chat with your Nozbe Teams agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

  • MCP Client: Built-in support for Model Context Protocol servers
  • Toolsets: Organize tools into logical groups
  • Step Callbacks: Monitor and debug agent execution
  • OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

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:
  • Node.js 18 or higher
  • A Composio account with an active API key
  • An OpenAI API key
  • Basic familiarity with TypeScript

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key.
  • You need credits or a connected billing setup to use the models.
  • Store the key somewhere safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Go to Settings and copy your API key.
  • This key lets your Mastra agent talk to Composio and reach Nozbe Teams through MCP.

Install dependencies

bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

Install the required packages.

What's happening:

  • @composio/core is the Composio SDK for creating MCP sessions
  • @mastra/core provides the Agent class
  • @mastra/mcp is Mastra's MCP client
  • @ai-sdk/openai is the model wrapper for OpenAI
  • dotenv loads environment variables from .env

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_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 your requests to Composio
  • COMPOSIO_USER_ID tells Composio which user this session belongs to
  • OPENAI_API_KEY lets the Mastra agent call OpenAI models

Import libraries and validate environment

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey as string,
});
What's happening:
  • dotenv/config auto loads your .env so process.env.* is available
  • openai gives you a Mastra compatible model wrapper
  • Agent is the Mastra agent that will call tools and produce answers
  • MCPClient connects Mastra to your Composio MCP server
  • Composio is used to create a Tool Router session

Create a Tool Router session for Nozbe Teams

typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["nozbe_teams"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Nozbe Teams MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "nozbe_teams" for Nozbe Teams access
  • session.mcp.url is the MCP URL that Mastra's MCPClient will connect to

Configure Mastra MCP client and fetch tools

typescript
const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);
What's happening:
  • MCPClient takes an id for this client and a list of MCP servers
  • The headers property includes the x-api-key for authentication
  • getTools fetches the tool definitions exposed by the Nozbe Teams toolkit

Create the Mastra agent

typescript
const agent = new Agent({
    name: "nozbe_teams-mastra-agent",
    instructions: "You are an AI agent with Nozbe Teams tools via Composio.",
    model: "openai/gpt-5",
  });
What's happening:
  • Agent is the core Mastra agent
  • name is just an identifier for logging and debugging
  • instructions guide the agent to use tools instead of only answering in natural language
  • model uses openai("gpt-5") to configure the underlying LLM

Set up interactive chat interface

typescript
let messages: AiMessageType[] = [];

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

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

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;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        nozbe_teams: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
What's happening:
  • messages keeps the full conversation history in Mastra's expected format
  • agent.generate runs the agent with conversation history and Nozbe Teams toolsets
  • maxSteps limits how many tool calls the agent can take in a single run
  • onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

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

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["nozbe_teams"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nozbe_teams: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "nozbe_teams-mastra-agent",
    instructions: "You are an AI agent with Nozbe Teams tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

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

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { nozbe_teams: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with Nozbe Teams through Composio's Tool Router. You can extend this further by:
  • Adding other toolkits like Gmail, Slack, or GitHub
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows

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

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 Mastra AI?

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