How to integrate Breeze MCP with LangChain

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Breeze logo
LangChain logo
divider

Introduction

This guide walks you through connecting Breeze to LangChain using the Composio tool router. By the end, you'll have a working Breeze agent that can create a new workspace for the design team, add john and sara to project alpha, archive completed project called website redesign through natural language commands.

This guide will help you understand how to give your LangChain agent real control over a Breeze account through Composio's Breeze MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Breeze with

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your Breeze project to Composio
  • Create a Tool Router MCP session for Breeze
  • Initialize an MCP client and retrieve Breeze tools
  • Build a LangChain agent that can interact with Breeze
  • 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 Breeze MCP server, and what's possible with it?

The Breeze MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Breeze account. It provides structured and secure access to your projects, tasks, and team collaboration features, so your agent can create projects, manage cards, add team members, organize workflows, and handle workspace administration on your behalf.

  • Project creation and management: Instantly create new projects, archive completed ones, or delete projects you no longer need—keeping your workspace organized at all times.
  • Task and card automation: Have your agent create, update, or delete cards (tasks) in any project, assign due dates, and manage assignees for seamless task tracking.
  • Team and member collaboration: Easily add people to projects or remove them, ensuring the right teammates are always involved without manual overhead.
  • Workflow structuring with lists: Let your agent create new stages (lists) within projects to tailor workflows and keep every team organized by process.
  • Workspace setup and cleanup: Automate creation or deletion of workspaces to reflect your team’s evolving structure and simplify workspace administration.

Supported Tools & Triggers

Tools
Add Project PeopleAdd people to a Breeze project by inviting them via email.
Archive ProjectTool to archive a specific project.
Create CardTool to create a new card in a project.
CREATE_LISTTool to create a new list (stage) in a Breeze project.
Create ProjectCreates a new project in Breeze project management system.
Create WorkspaceTool to create a new workspace.
Delete CardTool to delete a specific card (task) by its ID.
Delete ProjectTool to delete a specific project by ID.
Delete Person from ProjectTool to delete a person from a project by user ID.
Delete WorkspaceTool to delete a specific workspace by ID.
Get CardTool to retrieve detailed info for a specific card (task) in a project.
GET_CARDSTool to get all cards (tasks) for a specific project.
Get ProjectTool to get a specific project by ID.
Get Project PeopleTool to get all users in a project.
Get ProjectsRetrieves a list of all active (non-archived) projects in Breeze.
Get WorkspaceTool to get a specific workspace by ID.
Get WorkspacesTool to get all workspaces.
Move CardTool to move a card to a different stage or position.

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:

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

pip install composio-langchain langchain-mcp-adapters langchain python-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 is the core agent framework
  • python-dotenv 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

from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with Breeze functionality through MCP

Initialize Composio client

async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))

    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
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 Breeze tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding

Create a Tool Router session

# Create Tool Router session for Breeze
session = composio.create(
    user_id=os.getenv("COMPOSIO_USER_ID"),
    toolkits=['breeze']
)

url = session.mcp.url
What's happening:
  • We're creating a Tool Router session that gives your agent access to Breeze 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 Breeze tools as needed

Configure the agent with the MCP URL

client = MultiServerMCPClient({
    "breeze-agent": {
        "transport": "streamable_http",
        "url": session.mcp.url,
        "headers": {
            "x-api-key": os.getenv("COMPOSIO_API_KEY")
        }
    }
})

tools = await client.get_tools()

agent = create_agent("gpt-5", tools)
What's happening:
  • We're creating a MultiServerMCPClient that connects to our Breeze MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • get_tools() retrieves all available Breeze tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model

Set up interactive chat interface

conversation_history = []

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

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

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

    if not user_input:
        continue

    conversation_history.append({"role": "user", "content": user_input})
    print("\nAgent is thinking...\n")

    response = await agent.ainvoke({"messages": conversation_history})
    conversation_history = response['messages']
    final_response = response['messages'][-1].content
    print(f"Agent: {final_response}\n")
What's happening:
  • We initialize an empty conversation_history list to maintain context across interactions
  • A while loop continuously accepts 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 ainvoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully

Run the application

if __name__ == "__main__":
    asyncio.run(main())
What's happening:
  • We call the main() function using asyncio.run() to start the application

Complete Code

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

from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()

async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    
    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
    
    session = composio.create(
        user_id=os.getenv("COMPOSIO_USER_ID"),
        toolkits=['breeze']
    )

    url = session.mcp.url
    
    client = MultiServerMCPClient({
        "breeze-agent": {
            "transport": "streamable_http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    })
    
    tools = await client.get_tools()
  
    agent = create_agent("gpt-5", tools)
    
    conversation_history = []
    
    print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
    print("Ask any Breeze related question or task to the agent.\n")
    
    while True:
        user_input = input("You: ").strip()
        
        if user_input.lower() in ['exit', 'quit', 'bye']:
            print("\nGoodbye!")
            break
        
        if not user_input:
            continue
        
        conversation_history.append({"role": "user", "content": user_input})
        print("\nAgent is thinking...\n")
        
        response = await agent.ainvoke({"messages": conversation_history})
        conversation_history = response['messages']
        final_response = response['messages'][-1].content
        print(f"Agent: {final_response}\n")

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

Conclusion

You've successfully built a LangChain agent that can interact with Breeze 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.

How to build Breeze MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Breeze MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Breeze MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Breeze MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Breeze MCP with Claude Cowork

Codex logo

Codex

Use Breeze MCP with Codex

OpenClaw logo

OpenClaw

Use Breeze MCP with OpenClaw

Hermes logo

Hermes

Use Breeze MCP with Hermes

CLI logo

CLI

Use Breeze MCP with CLI

Google ADK logo

Google ADK

Use Breeze MCP with Google ADK

Vercel AI SDK logo

Vercel AI SDK

Use Breeze MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Breeze MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Breeze MCP with LlamaIndex

CrewAI logo

CrewAI

Use Breeze MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Breeze MCP?

With a standalone Breeze MCP server, the agents and LLMs can only access a fixed set of Breeze tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Breeze and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with LangChain?

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 Breeze tools.

Can I manage the permissions and scopes for Breeze while using Tool Router?

Yes, absolutely. You can configure which Breeze 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 Breeze 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.

Get started for freeGet a demo↗