Kommo with CrewAI

How to integrate Kommo MCP with CrewAI

Trusted by

GET STARTED FOR FREE GET A DEMO

30 min · no commitment · see it on your stack

Introduction Also integrate Kommo with TL;DR What is CrewAI What is the Kommo MCP server Supported Tools & Triggers Creating MCP Server - Stand-alone vs Composio SDK Step-by-step Guide Complete Code Conclusion How to build Kommo MCP Agent with another framework Explore Other Toolkits FAQ

Connect Kommo without Auth hassles

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

Try for Free

Introduction

This guide walks you through connecting Kommo to CrewAI using the Composio tool router. By the end, you'll have a working Kommo agent that can add a new lead with contact info, list all companies created this week, create a follow-up task for a lead through natural language commands.

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

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

Also integrate Kommo with

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

TL;DR

Here's what you'll learn:

Get a Composio API key and configure your Kommo connection
Set up CrewAI with an MCP enabled agent
Create a Tool Router session or standalone MCP server for Kommo
Build a conversational loop where your agent can execute Kommo operations

What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.

Key features include:

Agent Roles: Define specialized agents with specific goals and backstories
Task Management: Create tasks with clear descriptions and expected outputs
Crew Orchestration: Combine agents and tasks into collaborative workflows
MCP Integration: Connect to external tools through Model Context Protocol

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

The Kommo MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Kommo CRM account. It provides structured and secure access to your customer data, so your agent can perform actions like creating leads, managing contacts, tracking companies, organizing pipelines, and automating tasks on your behalf.

Lead and pipeline management: Automatically create new leads, list existing leads, and organize them within your sales pipelines, helping you stay on top of every sales opportunity.
Contact and company handling: Effortlessly add or list contacts and companies, making it simple for your agent to keep your CRM up to date and accessible.
Task automation and tracking: Let your agent create tasks for follow-ups, reminders, or next steps, so nothing falls through the cracks in your customer relationships.
Pipeline stage and custom field access: Retrieve and list pipeline stages and custom fields, enabling your agent to analyze and optimize your sales processes with tailored data.
Business process automation: Leverage structured tools to automate repetitive actions like updating records or filtering data, saving you time and reducing manual effort.

Supported Tools & Triggers

Tools

Add AI Source FileTool to add a knowledge source file to Kommo AI.

Create Kommo CompaniesAction to add one or more companies into the Kommo account.

Create Kommo ContactAction to create one or more contacts in Kommo CRM.

Create Kommo LeadAction to create a lead in Kommo CRM.

Create Kommo TaskAction to create a task in Kommo CRM.

Delete Kommo FilesTool to delete files (move to trash) in Kommo.

Get Kommo AccountTool to get account information including user data, custom fields, task types, user groups, amojo rights, and integration status.

Get Kommo CompanyTool to get a company by its ID from Kommo CRM.

Get Kommo ContactTool to get a specific contact by its ID from Kommo CRM.

Get Kommo Custom FieldTool to retrieve a custom field by its ID from Kommo CRM.

Get Kommo EventTool to get a specific event by its ID from Kommo CRM.

Get Kommo Field GroupTool to retrieve a custom field group by its ID from Kommo CRM.

Get File LinksTool to get entities associated with a file in Kommo.

Get Incoming Leads SummaryTool to retrieve summary statistics for incoming (unsorted) leads in Kommo CRM.

Get Kommo LeadTool to get a lead by its ID from Kommo CRM.

Get Kommo Loss ReasonTool to retrieve a specific loss reason by its ID from Kommo CRM.

Get Kommo PipelineTool to get a pipeline by its ID from Kommo CRM.

Get Kommo Pipeline StatusTool to get a specific pipeline stage by its ID from Kommo CRM.

Get Kommo TaskTool to retrieve a task by its ID from Kommo CRM.

Get Kommo UserTool to retrieve user data by its ID from Kommo CRM.

Get Kommo Widget InfoTool to get detailed information about a widget by its code.

Import Products to AITool to launch import of products from CRM to AI knowledge base.

List Kommo CatalogsTool to retrieve a list of catalogs (lists) from Kommo CRM.

List Kommo CompaniesAction to list Kommo companies with various filter options.

List Kommo ContactsAction to list contacts in Kommo CRM.

List Kommo ConversationsTool to get a list of conversations from Kommo CRM.

List Kommo Custom FieldsAction to list custom fields in Kommo CRM.

List Entity FilesTool to retrieve a list of files attached to an entity in Kommo CRM.

List Kommo Entity LinksTool to get a list of entities linked to a specific entity in Kommo.

List Kommo Entity NotesTool to get a list of all notes for an entity type (leads, contacts, or companies) in Kommo CRM.

List Kommo Entity TagsTool to get a list of tags for an entity type (leads, contacts, or companies).

List Kommo EventsTool to get a list of events from Kommo CRM with filtering options.

List Kommo Event TypesTool to get a list of all available event types in Kommo CRM.

List Kommo Field GroupsTool to get a list of custom field groups for an entity type in Kommo CRM.

List Kommo FilesTool to retrieve a list of files from Kommo Drive.

List Incoming LeadsTool to get a list of incoming leads (unsorted) from Kommo with filtering and pagination.

List Kommo LeadsAction to list leads in Kommo CRM.

List Kommo Lead PipelinesAction to list lead pipelines in Kommo CRM.

List Kommo Loss ReasonsAction to list loss reasons for leads in Kommo CRM.

List Kommo Notes By EntityTool to get notes for a specific entity by its ID in Kommo CRM.

List Kommo Pipeline StagesAction to list stages of a pipeline in Kommo CRM.

List Kommo User RolesTool to get a list of user roles in Kommo CRM.

List Kommo Lead SourcesTool to get a list of lead sources in Kommo CRM.

List Kommo TasksAction to list tasks in Kommo CRM.

List Kommo TemplatesTool to get a list of message templates in Kommo CRM.

List Kommo UsersTool to get a list of users from Kommo CRM with pagination support.

List Kommo WebhooksTool to get a list of registered webhooks for the Kommo account.

List Kommo Website ButtonsTool to get a list of website chat button (CRM Plugin) objects from Kommo.

List Kommo WidgetsTool to get a list of installed widgets in Kommo.

Update Kommo CompanyAction to update a single company in Kommo CRM.

Update Kommo ContactAction to update contact information in Kommo CRM by contact ID.

Update Kommo LeadAction to update an existing lead in Kommo CRM.

Update Kommo TaskAction to update a task in Kommo CRM.

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

Prerequisites

Before starting, make sure you have:

Python 3.9 or higher
A Composio account and API key
A Kommo connection authorized in Composio
An OpenAI API key for the CrewAI LLM
Basic familiarity with Python

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

bash

pip install composio crewai crewai-tools[mcp] python-dotenv

What's happening:

composio connects your agent to Kommo via MCP
crewai provides Agent, Task, Crew, and LLM primitives
crewai-tools[mcp] includes MCP helpers
python-dotenv loads environment variables from .env

Set up environment variables

bash

COMPOSIO_API_KEY=your_composio_api_key_here
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 with Composio
USER_ID scopes the session to your account
OPENAI_API_KEY lets CrewAI use your chosen OpenAI model

Import dependencies

python

import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

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

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

What's happening:

CrewAI classes define agents and tasks, and run the workflow
MCPServerHTTP connects the agent to an MCP endpoint
Composio will give you a short lived Kommo MCP URL

Create a Composio Tool Router session for Kommo

python

composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["kommo"])

url = session.mcp.url

What's happening:

You create a Kommo only session through Composio
Composio returns an MCP HTTP URL that exposes Kommo tools

Initialize the MCP Server

python

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )

What's Happening:

Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.

Create a CLI Chatloop and define the Crew

python

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

conversation_context = ""

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

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

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")

What's Happening:

Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.

Complete Code

Here's the complete code to get you started with Kommo and CrewAI:

python

from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

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

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_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.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["kommo"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

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

    conversation_context = ""

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

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

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")

Conclusion

You now have a CrewAI agent connected to Kommo through Composio's Tool Router. The agent can perform Kommo operations through natural language commands.

Next steps:

Add role-specific instructions to customize agent behavior
Plug in more toolkits for multi-app workflows
Chain tasks for complex multi-step operations

How to build Kommo MCP Agent with another framework

OpenAI Agents SDK

Use Kommo MCP with OpenAI Agents SDK

Claude Agent SDK

Use Kommo MCP with Claude Agent SDK

Claude Code

Use Kommo MCP with Claude Code

Claude Cowork

Use Kommo MCP with Claude Cowork

Codex

Use Kommo MCP with Codex

OpenClaw

Use Kommo MCP with OpenClaw

Hermes

Use Kommo MCP with Hermes

CLI

Use Kommo MCP with CLI

Google ADK

Use Kommo MCP with Google ADK

LangChain

Use Kommo MCP with LangChain

Vercel AI SDK

Use Kommo MCP with Vercel AI SDK

Mastra AI

Use Kommo MCP with Mastra AI

LlamaIndex

Use Kommo MCP with LlamaIndex

Explore Other Toolkits

Hubspot

Oauth2Api Key

HubSpot is an all-in-one marketing, sales, and customer service platform. It lets teams nurture leads, automate outreach, and track every customer interaction in one place.

Pipedrive

Oauth2Api Key

Pipedrive is a sales management platform offering pipeline visualization, lead tracking, and workflow automation. It helps sales teams keep deals moving forward efficiently and never miss a follow-up.

Salesforce

Oauth2S2s Oauth2

Salesforce is a leading CRM platform that helps businesses manage sales, service, and marketing. It centralizes customer data, enabling teams to drive growth and build strong relationships.

TOOLKIT MARKETPLACE

FAQ

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

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

Can I use Tool Router MCP with CrewAI?

Yes, you can. CrewAI 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 Kommo tools.

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

Yes, absolutely. You can configure which Kommo 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 Kommo data and credentials are handled as safely as possible.

Used by agents from

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 free Get a demo↗

Harsha GaddipatiCo-founder, Slashy

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

Abhi AryaCo-founder, Opennote

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 has immensely helped in keeping new users on the platform.

Nirman DaveCEO, Zams

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

Ryan YuFounder, Extra Thursday

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

Tomisin JenrolaFounder & CEO, SwarmZero

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

Jerome LeclancheCo-Founder, Ingram Technologies

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.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

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.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

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.

How to integrate Kommo MCP with CrewAI

Table of Contents

Connect Kommo without Auth hassles

Introduction

Also integrate Kommo with

TL;DR

What is CrewAI?

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

Supported Tools & Triggers

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

Create a Composio Tool Router session for Kommo

Initialize the MCP Server

Create a CLI Chatloop and define the Crew

Complete Code

Conclusion

How to build Kommo MCP Agent with another framework

OpenAI Agents SDK

Claude Agent SDK

Claude Code

Claude Cowork

Codex

OpenClaw

Hermes

CLI

Google ADK

LangChain

Vercel AI SDK

Mastra AI

LlamaIndex

Explore Other Toolkits

Hubspot

Pipedrive

Salesforce

FAQ

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

Can I use Tool Router MCP with CrewAI?

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

How safe is my data with Composio Tool Router?

Used by agents from

Never worry about agent reliability