How to integrate Nozbe Teams MCP with Claude Agent SDK

GET STARTED FOR FREE
Framework Integration Gradient
Nozbe Teams Logo
Claude Agent SDK Logo
divider

Introduction

This guide walks you through connecting Nozbe Teams to the Claude Agent SDK 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 Claude Agent SDK 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 Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Nozbe Teams
  • Configure an AI agent that can use Nozbe Teams as a tool
  • Run a live chat session where you can ask the agent to perform Nozbe Teams operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Nozbe Teams account
  • Some knowledge of Python

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • 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

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • composio-anthropic provides Composio integration for Anthropic
  • claude-agent-sdk is the core agent framework
  • python-dotenv loads environment variables

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The load_dotenv() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Nozbe Teams functionality

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Nozbe Teams
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["nozbe_teams"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Nozbe Teams
  • The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Nozbe Teams tools via Composio.",
    max_turns=10
)
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permission_mode="bypassPermissions" allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Nozbe Teams
  • max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

    # Main chat loop
    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit"}:
            print("Goodbye!")
            break

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()
What's happening:
  • The Claude SDK client is created using the async context manager pattern
  • The agent processes each query and streams the response back in real-time
  • The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
What's happening:
  • This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
  • The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

Here's the complete code to get you started with Nozbe Teams and Claude Agent SDK:

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Nozbe Teams
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["nozbe_teams"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Nozbe Teams tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

        # Main chat loop
        while True:
            user_input = input("You: ").strip()
            if user_input.lower() in {"exit", "quit"}:
                print("Goodbye!")
                break

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

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

Conclusion

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

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Nozbe Teams MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Nozbe Teams MCP with OpenAI Agents SDK

Google ADK

Google ADK

Use Nozbe Teams MCP with Google ADK

LangChain

LangChain

Use Nozbe Teams MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Nozbe Teams MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Nozbe Teams MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Nozbe Teams MCP with LlamaIndex

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 Claude Agent SDK?

Yes, you can. Claude Agent SDK 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