How to integrate Kommo MCP with LangChain

This guide walks you through connecting Kommo to LangChain 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 LangChain 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.

Kommo logoKommo
Oauth2

Kommo is a CRM platform for managing your leads, contacts, and sales pipelines. It helps businesses organize customer interactions, automate workflows, and boost team productivity.

53 Tools

Introduction

This guide walks you through connecting Kommo to LangChain 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 LangChain 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

TL;DR

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

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

Step by step10 STEPS
1

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
2

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

Install dependencies

npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters 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/core is the core agent framework
  • dotenv/config loads environment variables
4

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
5

Import dependencies

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

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

Initialize Composio client

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
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 Kommo tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding
7

Create a Tool Router session

const session = await composio.create(
    userId as string,
    {
        toolkits: ['kommo']
    }
);

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

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "kommo-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

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

Set up interactive chat interface

let conversationHistory: any[] = [];

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

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

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

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
What's happening:
  • We initialize an empty conversationHistory list to maintain context across interactions
  • A readline interface is used to continuously accept 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 invoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully
10

Run the application

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
What's happening:
  • We call the main() function to start the application

Complete Code

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

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['kommo']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "kommo-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Kommo related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    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;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});

Conclusion

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

Supported Tools

Every Kommo action and event your agent gets out of the box.

Add AI Source File

Tool to add a knowledge source file to Kommo AI.

Create Kommo Companies

Action to add one or more companies into the Kommo account.

Create Kommo Contact

Action to create one or more contacts in Kommo CRM.

Create Kommo Lead

Action to create a lead in Kommo CRM.

Create Kommo Task

Action to create a task in Kommo CRM.

Delete Kommo Files

Tool to delete files (move to trash) in Kommo.

Get Kommo Account

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

Get Kommo Company

Tool to get a company by its ID from Kommo CRM.

Get Kommo Contact

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

Get Kommo Custom Field

Tool to retrieve a custom field by its ID from Kommo CRM.

Get Kommo Event

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

Get Kommo Field Group

Tool to retrieve a custom field group by its ID from Kommo CRM.

Get File Links

Tool to get entities associated with a file in Kommo.

Get Incoming Leads Summary

Tool to retrieve summary statistics for incoming (unsorted) leads in Kommo CRM.

Get Kommo Lead

Tool to get a lead by its ID from Kommo CRM.

Get Kommo Loss Reason

Tool to retrieve a specific loss reason by its ID from Kommo CRM.

Get Kommo Pipeline

Tool to get a pipeline by its ID from Kommo CRM.

Get Kommo Pipeline Status

Tool to get a specific pipeline stage by its ID from Kommo CRM.

Get Kommo Task

Tool to retrieve a task by its ID from Kommo CRM.

Get Kommo User

Tool to retrieve user data by its ID from Kommo CRM.

Get Kommo Widget Info

Tool to get detailed information about a widget by its code.

Import Products to AI

Tool to launch import of products from CRM to AI knowledge base.

List Kommo Catalogs

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

List Kommo Companies

Action to list Kommo companies with various filter options.

List Kommo Contacts

Action to list contacts in Kommo CRM.

List Kommo Conversations

Tool to get a list of conversations from Kommo CRM.

List Kommo Custom Fields

Action to list custom fields in Kommo CRM.

List Entity Files

Tool to retrieve a list of files attached to an entity in Kommo CRM.

List Kommo Entity Links

Tool to get a list of entities linked to a specific entity in Kommo.

List Kommo Entity Notes

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

List Kommo Entity Tags

Tool to get a list of tags for an entity type (leads, contacts, or companies).

List Kommo Events

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

List Kommo Event Types

Tool to get a list of all available event types in Kommo CRM.

List Kommo Field Groups

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

List Kommo Files

Tool to retrieve a list of files from Kommo Drive.

List Incoming Leads

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

List Kommo Leads

Action to list leads in Kommo CRM.

List Kommo Lead Pipelines

Action to list lead pipelines in Kommo CRM.

List Kommo Loss Reasons

Action to list loss reasons for leads in Kommo CRM.

List Kommo Notes By Entity

Tool to get notes for a specific entity by its ID in Kommo CRM.

List Kommo Pipeline Stages

Action to list stages of a pipeline in Kommo CRM.

List Kommo User Roles

Tool to get a list of user roles in Kommo CRM.

List Kommo Lead Sources

Tool to get a list of lead sources in Kommo CRM.

List Kommo Tasks

Action to list tasks in Kommo CRM.

List Kommo Templates

Tool to get a list of message templates in Kommo CRM.

List Kommo Users

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

List Kommo Webhooks

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

List Kommo Website Buttons

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

List Kommo Widgets

Tool to get a list of installed widgets in Kommo.

Update Kommo Company

Action to update a single company in Kommo CRM.

Update Kommo Contact

Action to update contact information in Kommo CRM by contact ID.

Update Kommo Lead

Action to update an existing lead in Kommo CRM.

Update Kommo Task

Action to update a task in Kommo CRM.

FAQ

Frequently asked questions

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.

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

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.

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.

Start with Kommo.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Kommo tool your agent needs.Free to start.

Start building