How to integrate Kommo MCP with Mastra AI

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

30 min · no commitment · see it on your stack

Kommo logo
Mastra AI logo
divider

Introduction

This guide walks you through connecting Kommo to Mastra AI 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 Mastra AI 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:
  • Set up your environment so Mastra, OpenAI, and Composio work together
  • Create a Tool Router session in Composio that exposes Kommo tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Kommo tool definitions and attach them as a toolset
  • Build a Mastra agent that can reason, call tools, and return structured results
  • Run an interactive CLI where you can chat with your Kommo agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

  • MCP Client: Built-in support for Model Context Protocol servers
  • Toolsets: Organize tools into logical groups
  • Step Callbacks: Monitor and debug agent execution
  • OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

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:

  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:
  • Node.js 18 or higher
  • A Composio account with an active API key
  • An OpenAI API key
  • Basic familiarity with TypeScript

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key.
  • You need credits or a connected billing setup to use the models.
  • Store the key somewhere safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Go to Settings and copy your API key.
  • This key lets your Mastra agent talk to Composio and reach Kommo through MCP.

Install dependencies

bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

Install the required packages.

What's happening:

  • @composio/core is the Composio SDK for creating MCP sessions
  • @mastra/core provides the Agent class
  • @mastra/mcp is Mastra's MCP client
  • @ai-sdk/openai is the model wrapper for OpenAI
  • dotenv loads environment variables from .env

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_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 your requests to Composio
  • COMPOSIO_USER_ID tells Composio which user this session belongs to
  • OPENAI_API_KEY lets the Mastra agent call OpenAI models

Import libraries and validate environment

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey as string,
});
What's happening:
  • dotenv/config auto loads your .env so process.env.* is available
  • openai gives you a Mastra compatible model wrapper
  • Agent is the Mastra agent that will call tools and produce answers
  • MCPClient connects Mastra to your Composio MCP server
  • Composio is used to create a Tool Router session

Create a Tool Router session for Kommo

typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["kommo"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Kommo MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "kommo" for Kommo access
  • session.mcp.url is the MCP URL that Mastra's MCPClient will connect to

Configure Mastra MCP client and fetch tools

typescript
const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);
What's happening:
  • MCPClient takes an id for this client and a list of MCP servers
  • The headers property includes the x-api-key for authentication
  • getTools fetches the tool definitions exposed by the Kommo toolkit

Create the Mastra agent

typescript
const agent = new Agent({
    name: "kommo-mastra-agent",
    instructions: "You are an AI agent with Kommo tools via Composio.",
    model: "openai/gpt-5",
  });
What's happening:
  • Agent is the core Mastra agent
  • name is just an identifier for logging and debugging
  • instructions guide the agent to use tools instead of only answering in natural language
  • model uses openai("gpt-5") to configure the underlying LLM

Set up interactive chat interface

typescript
let messages: AiMessageType[] = [];

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

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

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

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        kommo: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
What's happening:
  • messages keeps the full conversation history in Mastra's expected format
  • agent.generate runs the agent with conversation history and Kommo toolsets
  • maxSteps limits how many tool calls the agent can take in a single run
  • onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

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

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["kommo"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      kommo: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "kommo-mastra-agent",
    instructions: "You are an AI agent with Kommo tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

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

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { kommo: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with Kommo through Composio's Tool Router. You can extend this further by:
  • Adding other toolkits like Gmail, Slack, or GitHub
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows

How to build Kommo MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Kommo MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Kommo MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Kommo MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Kommo MCP with Claude Cowork

Codex logo

Codex

Use Kommo MCP with Codex

OpenClaw logo

OpenClaw

Use Kommo MCP with OpenClaw

Hermes logo

Hermes

Use Kommo MCP with Hermes

CLI logo

CLI

Use Kommo MCP with CLI

Google ADK logo

Google ADK

Use Kommo MCP with Google ADK

LangChain logo

LangChain

Use Kommo MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Kommo MCP with Vercel AI SDK

LlamaIndex logo

LlamaIndex

Use Kommo MCP with LlamaIndex

CrewAI logo

CrewAI

Use Kommo MCP with CrewAI

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 Mastra AI?

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

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↗