# How to integrate Nozbe Teams MCP with LlamaIndex

```json
{
  "title": "How to integrate Nozbe Teams MCP with LlamaIndex",
  "toolkit": "Nozbe Teams",
  "toolkit_slug": "nozbe_teams",
  "framework": "LlamaIndex",
  "framework_slug": "llama-index",
  "url": "https://composio.dev/toolkits/nozbe_teams/framework/llama-index",
  "markdown_url": "https://composio.dev/toolkits/nozbe_teams/framework/llama-index.md",
  "updated_at": "2026-03-29T06:43:36.781Z"
}
```

## Introduction

This guide walks you through connecting Nozbe Teams to LlamaIndex 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 LlamaIndex 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](https://composio.dev/toolkits/nozbe_teams/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/nozbe_teams/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/nozbe_teams/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/nozbe_teams/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/nozbe_teams/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/nozbe_teams/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/nozbe_teams/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/nozbe_teams/framework/cli)
- [Google ADK](https://composio.dev/toolkits/nozbe_teams/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/nozbe_teams/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/nozbe_teams/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/nozbe_teams/framework/mastra-ai)
- [CrewAI](https://composio.dev/toolkits/nozbe_teams/framework/crew-ai)

## TL;DR

Here's what you'll learn:
- Set your OpenAI and Composio API keys
- Install LlamaIndex and Composio packages
- Create a Composio Tool Router session for Nozbe Teams
- Connect LlamaIndex to the Nozbe Teams MCP server
- Build a Nozbe Teams-powered agent using LlamaIndex
- Interact with Nozbe Teams through natural language

## What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.
Key features include:
- ReAct Agent: Reasoning and acting pattern for tool-using agents
- MCP Tools: Native support for Model Context Protocol
- Context Management: Maintain conversation context across interactions
- Async Support: Built for async/await patterns

## 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

| Tool slug | Name | Description |
|---|---|---|
| `NOZBE_TEAMS_CREATE_ATTACHMENT` | Create Attachment | Tool to add attachment metadata to a comment. Use when you need to create attachment metadata for a file associated with a comment. This creates the metadata record; actual file upload may be a separate step depending on the workflow. |
| `NOZBE_TEAMS_CREATE_COMMENT` | Create Comment | Tool to add a comment to a task in Nozbe Teams. Use when you need to add feedback, notes, or updates to a specific task. |
| `NOZBE_TEAMS_CREATE_PROJECT_SECTION` | Create Project Section | Tool to create a new project section in Nozbe Teams. Use when you need to add a section to organize tasks within a project. |
| `NOZBE_TEAMS_CREATE_REMINDER` | Create Reminder | Tool to add a reminder to a task in Nozbe Teams. Use when you need to set up a notification for a specific task at a given time. |
| `NOZBE_TEAMS_CREATE_TAG_ASSIGNMENT` | Create Tag Assignment | Tool to add a tag assignment to a task. Use when you need to tag or label a task for organization or categorization purposes. |
| `NOZBE_TEAMS_CREATE_TASK` | Create Task | Tool to create a new task in Nozbe Teams. Use when you need to add a task to a project or personal task list. Only the task name is required; all other fields are optional. |
| `NOZBE_TEAMS_CREATE_TEAM_MEMBER` | Create Team Member | Tool to add a team member in Nozbe Teams. Use when you need to add an existing user to a team with a specific role and status. The user must already exist in the system before they can be added to a team. |
| `NOZBE_TEAMS_CREATE_USER` | Create User | Tool to create a new placeholder user in Nozbe Teams. Use when you need to add a placeholder user to the system. Note: Only placeholder users can be created via API - attempting to create non-placeholder users will fail with a 400 error. |
| `NOZBE_TEAMS_DELETE_COMMENT` | Delete Comment | Tool to permanently delete a comment by its ID. Use when you need to remove a comment from a task. Returns the deleted comment object with all its properties. |
| `NOZBE_TEAMS_DELETE_PROJECT` | Delete Project | Tool to delete a project in Nozbe Teams by its ID. Use when you need to permanently remove a project from the workspace. |
| `NOZBE_TEAMS_DELETE_REMINDER` | Delete Reminder | Tool to delete a reminder by its unique ID. Use when you need to remove a reminder from Nozbe Teams. |
| `NOZBE_TEAMS_DELETE_TAG_ASSIGNMENT` | Delete Tag Assignment | Tool to delete a tag assignment by its ID. Use when you need to remove a tag from a task or project. |
| `NOZBE_TEAMS_DELETE_TASK` | Delete Task | Tool to delete a task in Nozbe Teams by its ID. Use when you need to permanently remove a task from the workspace. |
| `NOZBE_TEAMS_GET_ATTACHMENT` | Get Attachment | Tool to get attachment metadata by its ID. Use when you need to retrieve details about a specific file attached to a comment. |
| `NOZBE_TEAMS_GET_COMMENT_BY_ID` | Get Comment by ID | Tool to retrieve a comment by its ID from Nozbe Teams. Use when you need to fetch details of a specific comment on a task. |
| `NOZBE_TEAMS_GET_PROJECT_BY_ID` | Get Project by ID | Tool to retrieve a project by its ID from Nozbe Teams. Use when you need to fetch details about a specific project. |
| `NOZBE_TEAMS_GET_PROJECT_ACCESS` | Get Project Access | Tool to retrieve project access details by ID. Use when you need to check a team member's access permissions and manager status for a specific project. |
| `NOZBE_TEAMS_GET_PROJECT_SECTION` | Get Project Section | Tool to retrieve a project section by ID from Nozbe Teams. Use when you need to fetch details of a specific section within a project, including its name, position, and timestamps. |
| `NOZBE_TEAMS_GET_REMINDER` | Get Reminder | Tool to get a reminder by ID from Nozbe Teams. Use when you need to retrieve details about a specific reminder. |
| `NOZBE_TEAMS_GET_TAG` | Get Tag | Tool to get a tag by ID from Nozbe Teams. Use when you need to retrieve details about a specific tag. |
| `NOZBE_TEAMS_GET_TAG_ASSIGNMENT` | Get Tag Assignment | Tool to retrieve a tag assignment by its ID. Use when you need to fetch details about a specific tag-task relationship in Nozbe Teams. |
| `NOZBE_TEAMS_GET_TASK_BY_ID` | Get Task by ID | Tool to retrieve a task by its ID from Nozbe Teams. Use when you need to fetch details about a specific task. |
| `NOZBE_TEAMS_GET_TASK_EVENT` | Get Task Event | Tool to get a task event by ID. Use when you need to retrieve details about a specific task event. |
| `NOZBE_TEAMS_GET_TEAM_BY_ID` | Get Team by ID | Tool to retrieve a team by its ID from Nozbe Teams. Use when you need to fetch details about a specific team. |
| `NOZBE_TEAMS_GET_TEAM_MEMBER_BY_ID` | Get Team Member by ID | Tool to retrieve a team member by ID from Nozbe Teams. Use when you need to fetch details about a specific team member. |
| `NOZBE_TEAMS_GET_USER_BY_ID` | Get User by ID | Tool to retrieve a user by their ID from Nozbe Teams. Use when you need to fetch details about a specific user. |
| `NOZBE_TEAMS_LIST_COMMENT_ATTACHMENTS` | List Comment Attachments | Tool to get all attachments related to a specific comment in Nozbe Teams. Use when you need to retrieve attachment metadata (ID, name, size, MIME type, etc.) for a comment. Returns an array of attachment objects with their properties. |
| `NOZBE_TEAMS_LIST_COMMENTS` | List Comments | Tool to get accessible comments with optional filtering by task_id and pagination support. Use when you need to retrieve comments, optionally filtered by task, with control over pagination and field selection. |
| `NOZBE_TEAMS_LIST_GROUP_ASSIGNMENTS` | List Group Assignments | Tool to get accessible group assignments from Nozbe Teams. Use when you need to retrieve assignments between groups and projects/members, with optional filtering by group_id, object_id, or group_type. |
| `NOZBE_TEAMS_LIST_PROJECT_ACCESSES` | List Project Accesses | Tool to get accessible project accesses in Nozbe Teams. Use when you need to retrieve project access records, optionally filtered by sorting or field selection. Returns a list of project access objects showing which team members have access to which projects and their manager status. |
| `NOZBE_TEAMS_LIST_PROJECT_GROUPS` | List Project Groups | Tool to get accessible project groups from Nozbe Teams. Use when you need to list or search for project groups with optional filtering by name, team, or other criteria. |
| `NOZBE_TEAMS_LIST_PROJECTS` | List Projects | Tool to retrieve accessible projects with optional filtering. Use when you need to list projects, optionally filtered by team_id or is_open status. |
| `NOZBE_TEAMS_LIST_PROJECT_SECTIONS` | List Project Sections | Tool to retrieve accessible project sections with optional filtering. Use when you need to list sections within projects, optionally filtered by project_id. |
| `NOZBE_TEAMS_LIST_REMINDERS` | List Reminders | Tool to get accessible reminders from Nozbe Teams. Use when you need to retrieve reminders, optionally filtered by task ID, all-day status, or other parameters. |
| `NOZBE_TEAMS_LIST_TAG_ASSIGNMENTS` | List Tag Assignments | Tool to get accessible tag assignments with optional filtering by tag_id or task_id. Use when you need to retrieve associations between tags and tasks, optionally filtered by specific tag or task identifiers. |
| `NOZBE_TEAMS_LIST_TAGS` | List Tags | Tool to get accessible tags from Nozbe Teams. Use when you need to retrieve tags, optionally filtered by name, favorite status, or task association. |
| `NOZBE_TEAMS_LIST_TASK_EVENTS` | List Task Events | Tool to get accessible task events from Nozbe Teams. Use when you need to retrieve task activity history or audit trail. Filter by task_id to get events for a specific task. |
| `NOZBE_TEAMS_LIST_TASKS` | List Tasks | Tool to retrieve accessible tasks from Nozbe Teams. Use when you need to query tasks with optional filters like project_id or review_reason. Supports pagination and sorting of results. |
| `NOZBE_TEAMS_LIST_USERS` | List Users | Tool to retrieve accessible users from Nozbe Teams. Use when you need to query users with optional filters like name. Supports pagination and sorting of results. |
| `NOZBE_TEAMS_POLL_FOR_NEW_TASKS` | Poll for new tasks | Tool to poll for new tasks created since the last call. Use when you need to retrieve recently created tasks in Nozbe Teams. Optionally filter by project or responsible user, and specify which fields to return. |
| `NOZBE_TEAMS_POLL_UPDATED_TASKS` | Poll Updated Tasks | Tool to poll for tasks that have been updated since the last call. Use when you need to retrieve recently modified tasks from Nozbe Teams. |
| `NOZBE_TEAMS_UPDATE_COMMENT` | Update Comment | Tool to update an existing comment in Nozbe Teams. Use when you need to modify a comment's text, pin status, deletion status, or extra metadata. |
| `NOZBE_TEAMS_UPDATE_PROJECT` | Update Project | Tool to update a project in Nozbe Teams. Use when you need to modify project properties such as name, status, color, or description. All fields except the project ID are optional - only provide fields you want to update. |
| `NOZBE_TEAMS_UPDATE_PROJECT_ACCESS` | Update Project Access | Tool to update project access permissions in Nozbe Teams. Use when modifying member privileges for a specific project. |
| `NOZBE_TEAMS_UPDATE_TASK` | Update Task | Tool to update a task in Nozbe Teams. Use when you need to modify task properties such as name, project, responsible user, due date, or other attributes. All fields except the task ID are optional - only provide fields you want to update. |
| `NOZBE_TEAMS_UPDATE_TEAM` | Update Team | Tool to update a team in Nozbe Teams. Use when you need to modify team properties such as name, color, or sidebar position. All fields except the team ID are optional - only provide fields you want to update. |
| `NOZBE_TEAMS_UPDATE_TEAM_MEMBER` | Update Team Member | Tool to update a team member in Nozbe Teams. Use when you need to modify team member properties such as role, status, alias, or description. All fields except the team member ID are optional - only provide fields you want to update. |
| `NOZBE_TEAMS_UPDATE_USER` | Update User | Tool to update a user in Nozbe Teams. Use when you need to modify user properties such as name, avatar color, placeholder status, or contact information. All fields except the user ID are optional - only provide fields you want to update. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Nozbe Teams MCP server is an implementation of the Model Context Protocol that connects your AI agent to Nozbe Teams. It provides structured and secure access so your agent can perform Nozbe Teams operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

Before you begin, make sure you have:
- Python 3.8/Node 16 or higher installed
- A Composio account with the API key
- An OpenAI API key
- A Nozbe Teams account and project
- Basic familiarity with async Python/Typescript

### 1. Getting API Keys for OpenAI, Composio, and Nozbe Teams

No description provided.

### 2. Installing dependencies

No description provided.
```python
pip install composio-llamaindex llama-index llama-index-llms-openai llama-index-tools-mcp python-dotenv
```

```typescript
npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv
```

### 3. Set environment variables

Create a .env file in your project root:
These credentials will be used to:
- Authenticate with OpenAI's GPT-5 model
- Connect to Composio's Tool Router
- Identify your Composio user session for Nozbe Teams access
```bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id
```

### 4. Import modules

No description provided.
```python
import asyncio
import os
import dotenv

from composio import Composio
from composio_llamaindex import LlamaIndexProvider
from llama_index.core.agent.workflow import ReActAgent
from llama_index.core.workflow import Context
from llama_index.llms.openai import OpenAI
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec

dotenv.load_dotenv()
```

```typescript
import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();
```

### 5. Load environment variables and initialize Composio

No description provided.
```python
OPENAI_API_KEY = os.getenv("OPENAI_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not OPENAI_API_KEY:
    raise ValueError("OPENAI_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")
```

```typescript
const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!COMPOSIO_API_KEY) throw new Error("COMPOSIO_API_KEY is not set");
if (!COMPOSIO_USER_ID) throw new Error("COMPOSIO_USER_ID is not set");
```

### 6. Create a Tool Router session and build the agent function

What's happening here:
- We create a Composio client using your API key and configure it with the LlamaIndex provider
- We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, nozbe teams)
- The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
- LlamaIndex will connect to this endpoint to dynamically discover and use the available Nozbe Teams tools.
- The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
```python
async def build_agent() -> ReActAgent:
    composio_client = Composio(
        api_key=COMPOSIO_API_KEY,
        provider=LlamaIndexProvider(),
    )

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

    mcp_url = session.mcp.url
    print(f"Composio MCP URL: {mcp_url}")

    mcp_client = BasicMCPClient(mcp_url, headers={"x-api-key": COMPOSIO_API_KEY})
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    llm = OpenAI(model="gpt-5")

    description = "An agent that uses Composio Tool Router MCP tools to perform Nozbe Teams actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Nozbe Teams actions.
    """
    return ReActAgent(tools=tools, llm=llm, description=description, system_prompt=system_prompt, verbose=True)
```

```typescript
async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["nozbe_teams"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Nozbe Teams actions." ,
    llm,
    tools,
  });

  return agent;
}
```

### 7. Create an interactive chat loop

No description provided.
```python
async def chat_loop(agent: ReActAgent) -> None:
    ctx = Context(agent)
    print("Type 'quit', 'exit', or Ctrl+C to stop.")

    while True:
        try:
            user_input = input("\nYou: ").strip()
        except (KeyboardInterrupt, EOFError):
            print("\nBye!")
            break

        if not user_input or user_input.lower() in {"quit", "exit"}:
            print("Bye!")
            break

        try:
            print("Agent: ", end="", flush=True)
            handler = agent.run(user_input, ctx=ctx)

            async for event in handler.stream_events():
                # Stream token-by-token from LLM responses
                if hasattr(event, "delta") and event.delta:
                    print(event.delta, end="", flush=True)
                # Show tool calls as they happen
                elif hasattr(event, "tool_name"):
                    print(f"\n[Using tool: {event.tool_name}]", flush=True)

            # Get final response
            response = await handler
            print()  # Newline after streaming
        except KeyboardInterrupt:
            print("\n[Interrupted]")
            continue
        except Exception as e:
            print(f"\nError: {e}")
```

```typescript
async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}
```

### 8. Define the main entry point

What's happening here:
- We're orchestrating the entire application flow
- The agent gets built with proper error handling
- Then we kick off the interactive chat loop so you can start talking to Nozbe Teams
```python
async def main() -> None:
    agent = await build_agent()
    await chat_loop(agent)

if __name__ == "__main__":
    # Handle Ctrl+C gracefully
    signal.signal(signal.SIGINT, lambda s, f: (print("\nBye!"), exit(0)))
    try:
        asyncio.run(main())
    except KeyboardInterrupt:
        print("\nBye!")
```

```typescript
async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();
```

### 9. Run the agent

When prompted, authenticate and authorise your agent with Nozbe Teams, then start asking questions.
```bash
python llamaindex_agent.py
```

```typescript
npx ts-node llamaindex-agent.ts
```

## Complete Code

```python
import asyncio
import os
import signal
import dotenv

from composio import Composio
from composio_llamaindex import LlamaIndexProvider
from llama_index.core.agent.workflow import ReActAgent
from llama_index.core.workflow import Context
from llama_index.llms.openai import OpenAI
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec

dotenv.load_dotenv()

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

if not OPENAI_API_KEY:
    raise ValueError("OPENAI_API_KEY is not set")
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")

async def build_agent() -> ReActAgent:
    composio_client = Composio(
        api_key=COMPOSIO_API_KEY,
        provider=LlamaIndexProvider(),
    )

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

    mcp_url = session.mcp.url
    print(f"Composio MCP URL: {mcp_url}")

    mcp_client = BasicMCPClient(mcp_url, headers={"x-api-key": COMPOSIO_API_KEY})
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    llm = OpenAI(model="gpt-5")
    description = "An agent that uses Composio Tool Router MCP tools to perform Nozbe Teams actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Nozbe Teams actions.
    """
    return ReActAgent(
        tools=tools,
        llm=llm,
        description=description,
        system_prompt=system_prompt,
        verbose=True,
    );

async def chat_loop(agent: ReActAgent) -> None:
    ctx = Context(agent)
    print("Type 'quit', 'exit', or Ctrl+C to stop.")

    while True:
        try:
            user_input = input("\nYou: ").strip()
        except (KeyboardInterrupt, EOFError):
            print("\nBye!")
            break

        if not user_input or user_input.lower() in {"quit", "exit"}:
            print("Bye!")
            break

        try:
            print("Agent: ", end="", flush=True)
            handler = agent.run(user_input, ctx=ctx)

            async for event in handler.stream_events():
                # Stream token-by-token from LLM responses
                if hasattr(event, "delta") and event.delta:
                    print(event.delta, end="", flush=True)
                # Show tool calls as they happen
                elif hasattr(event, "tool_name"):
                    print(f"\n[Using tool: {event.tool_name}]", flush=True)

            # Get final response
            response = await handler
            print()  # Newline after streaming
        except KeyboardInterrupt:
            print("\n[Interrupted]")
            continue
        except Exception as e:
            print(f"\nError: {e}")

async def main() -> None:
    agent = await build_agent()
    await chat_loop(agent)

if __name__ == "__main__":
    # Handle Ctrl+C gracefully
    signal.signal(signal.SIGINT, lambda s, f: (print("\nBye!"), exit(0)))
    try:
        asyncio.run(main())
    except KeyboardInterrupt:
        print("\nBye!")
```

```typescript
import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["nozbe_teams"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Nozbe Teams actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();
```

## Conclusion

You've successfully connected Nozbe Teams to LlamaIndex through Composio's Tool Router MCP layer.
Key takeaways:
- Tool Router dynamically exposes Nozbe Teams tools through an MCP endpoint
- LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
- The agent becomes more capable without increasing prompt size
- Async Python provides clean, efficient execution of agent workflows
You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.

## How to build Nozbe Teams MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/nozbe_teams/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/nozbe_teams/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/nozbe_teams/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/nozbe_teams/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/nozbe_teams/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/nozbe_teams/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/nozbe_teams/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/nozbe_teams/framework/cli)
- [Google ADK](https://composio.dev/toolkits/nozbe_teams/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/nozbe_teams/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/nozbe_teams/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/nozbe_teams/framework/mastra-ai)
- [CrewAI](https://composio.dev/toolkits/nozbe_teams/framework/crew-ai)

## Related Toolkits

- [Google Sheets](https://composio.dev/toolkits/googlesheets) - 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](https://composio.dev/toolkits/notion) - Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place.
- [Airtable](https://composio.dev/toolkits/airtable) - 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](https://composio.dev/toolkits/asana) - 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.
- [Google Tasks](https://composio.dev/toolkits/googletasks) - Google Tasks is a to-do list and task management tool integrated into Gmail and Google Calendar. It helps you organize, track, and complete tasks across your Google ecosystem.
- [Linear](https://composio.dev/toolkits/linear) - Linear is a modern issue tracking and project planning tool for fast-moving teams. It helps streamline workflows, organize projects, and boost productivity.
- [Jira](https://composio.dev/toolkits/jira) - Jira is Atlassian’s platform for bug tracking, issue tracking, and agile project management. It helps teams organize work, prioritize tasks, and deliver projects efficiently.
- [Clickup](https://composio.dev/toolkits/clickup) - ClickUp is an all-in-one productivity platform for managing tasks, docs, goals, and team collaboration. It streamlines project workflows so teams can work smarter and stay organized in one place.
- [Monday](https://composio.dev/toolkits/monday) - Monday.com is a customizable work management platform for project planning and collaboration. It helps teams organize tasks, automate workflows, and track progress in real time.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.
- [Agiled](https://composio.dev/toolkits/agiled) - Agiled is an all-in-one business management platform for CRM, projects, and finance. It helps you streamline workflows, consolidate client data, and manage business processes in one place.
- [Ascora](https://composio.dev/toolkits/ascora) - Ascora is a cloud-based field service management platform for service businesses. It streamlines scheduling, invoicing, and customer operations in one place.
- [Basecamp](https://composio.dev/toolkits/basecamp) - Basecamp is a project management and team collaboration tool by 37signals. It helps teams organize tasks, share files, and communicate efficiently in one place.
- [Beeminder](https://composio.dev/toolkits/beeminder) - Beeminder is an online goal-tracking platform that uses monetary pledges to keep you motivated. Stay accountable and hit your targets with real financial incentives.
- [Boxhero](https://composio.dev/toolkits/boxhero) - Boxhero is a cloud-based inventory management platform for SMBs, offering real-time updates, barcode scanning, and team collaboration. It helps businesses streamline stock tracking and analytics for smarter inventory decisions.
- [Breathe HR](https://composio.dev/toolkits/breathehr) - Breathe HR is cloud-based HR software for SMEs to manage employee data, absences, and performance. It simplifies HR admin, making it easy to keep employee records accurate and up to date.
- [Breeze](https://composio.dev/toolkits/breeze) - Breeze is a project management platform designed to help teams plan, track, and collaborate on projects. It streamlines workflows and keeps everyone on the same page.
- [Bugherd](https://composio.dev/toolkits/bugherd) - Bugherd is a visual feedback and bug tracking tool for websites. It helps teams and clients report website issues directly on live sites for faster fixes.
- [Canny](https://composio.dev/toolkits/canny) - Canny is a platform for managing customer feedback and feature requests. It helps teams prioritize product decisions based on real user insights.
- [Chmeetings](https://composio.dev/toolkits/chmeetings) - Chmeetings is a church management platform for events, members, donations, and volunteers. It streamlines church operations and improves community engagement.

## Frequently Asked Questions

### 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 LlamaIndex?

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

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)