# How to integrate Kommo MCP with Mastra AI ```json { "title": "How to integrate Kommo MCP with Mastra AI", "toolkit": "Kommo", "toolkit_slug": "kommo", "framework": "Mastra AI", "framework_slug": "mastra-ai", "url": "https://composio.dev/toolkits/kommo/framework/mastra-ai", "markdown_url": "https://composio.dev/toolkits/kommo/framework/mastra-ai.md", "updated_at": "2026-05-12T10:16:59.233Z" } ``` ## 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 - [OpenAI Agents SDK](https://composio.dev/toolkits/kommo/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/kommo/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/kommo/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/kommo/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/kommo/framework/codex) - [OpenClaw](https://composio.dev/toolkits/kommo/framework/openclaw) - [Hermes](https://composio.dev/toolkits/kommo/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/kommo/framework/cli) - [Google ADK](https://composio.dev/toolkits/kommo/framework/google-adk) - [LangChain](https://composio.dev/toolkits/kommo/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/kommo/framework/ai-sdk) - [LlamaIndex](https://composio.dev/toolkits/kommo/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/kommo/framework/crew-ai) ## 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 | Tool slug | Name | Description | |---|---|---| | `KOMMO_ADD_AI_SOURCE_FILE` | Add AI Source File | Tool to add a knowledge source file to Kommo AI. Use when you need to upload a file (like documentation, policies, or knowledge base articles) to be used by the Kommo AI agent or suggested reply feature. | | `KOMMO_CREATE_COMPANY` | Create Kommo Companies | Action to add one or more companies into the Kommo account. | | `KOMMO_CREATE_CONTACT` | Create Kommo Contact | Action to create one or more contacts in Kommo CRM. | | `KOMMO_CREATE_LEAD` | Create Kommo Lead | Action to create a lead in Kommo CRM. | | `KOMMO_CREATE_TASK` | Create Kommo Task | Action to create a task in Kommo CRM. | | `KOMMO_DELETE_FILES` | Delete Kommo Files | Tool to delete files (move to trash) in Kommo. Use when you need to remove files from the Kommo account. | | `KOMMO_GET_ACCOUNT` | Get Kommo Account | Tool to get account information including user data, custom fields, task types, user groups, amojo rights, and integration status. Use when you need to retrieve account-level details from Kommo CRM. | | `KOMMO_GET_COMPANY` | Get Kommo Company | Tool to get a company by its ID from Kommo CRM. Use when you need to retrieve detailed information about a specific company including its name, responsible user, and optionally embedded data like contacts, leads, or catalog elements. | | `KOMMO_GET_CONTACT` | Get Kommo Contact | Tool to get a specific contact by its ID from Kommo CRM. Use when you need to retrieve detailed information about a particular contact. | | `KOMMO_GET_CUSTOM_FIELD` | Get Kommo Custom Field | Tool to retrieve a custom field by its ID from Kommo CRM. Use when you need detailed information about a specific custom field including its type, settings, and enum values. | | `KOMMO_GET_EVENT` | Get Kommo Event | Tool to get a specific event by its ID from Kommo CRM. Use when you need to retrieve detailed information about a particular event, including before/after state changes for entities. | | `KOMMO_GET_FIELD_GROUP` | Get Kommo Field Group | Tool to retrieve a custom field group by its ID from Kommo CRM. Use when you need to get details about a specific field group including its fields and metadata. | | `KOMMO_GET_FILE_LINKS` | Get File Links | Tool to get entities associated with a file in Kommo. Use when you need to find which leads, contacts, companies, or catalog elements are linked to a specific file. | | `KOMMO_GET_INCOMING_LEADS_SUMMARY` | Get Incoming Leads Summary | Tool to retrieve summary statistics for incoming (unsorted) leads in Kommo CRM. Use when you need aggregate metrics like total count, acceptance/decline rates, average processing time, and breakdown by lead source category. | | `KOMMO_GET_LEAD` | Get Kommo Lead | Tool to get a lead by its ID from Kommo CRM. Use when you need to retrieve detailed information about a specific lead including its status, price, responsible user, and optionally embedded data like contacts, catalog elements, or loss reasons. | | `KOMMO_GET_LOSS_REASON` | Get Kommo Loss Reason | Tool to retrieve a specific loss reason by its ID from Kommo CRM. Use when you need detailed information about a particular loss reason, such as its name, sort order, and timestamps. | | `KOMMO_GET_PIPELINE` | Get Kommo Pipeline | Tool to get a pipeline by its ID from Kommo CRM. Use when you need to retrieve details about a specific pipeline including its stages. | | `KOMMO_GET_PIPELINE_STATUS` | Get Kommo Pipeline Status | Tool to get a specific pipeline stage by its ID from Kommo CRM. Use when you need to retrieve detailed information about a particular stage within a pipeline. | | `KOMMO_GET_TASK` | Get Kommo Task | Tool to retrieve a task by its ID from Kommo CRM. Use when you need to fetch details of a specific task. | | `KOMMO_GET_USER` | Get Kommo User | Tool to retrieve user data by its ID from Kommo CRM. Use when you need to fetch details about a specific user including their name, email, role, group, and access rights. | | `KOMMO_GET_WIDGET` | Get Kommo Widget Info | Tool to get detailed information about a widget by its code. Use when you need to retrieve widget metadata, settings, version, or check if a widget is active in the account. | | `KOMMO_IMPORT_PRODUCTS_TO_AI` | Import Products to AI | Tool to launch import of products from CRM to AI knowledge base. Use when you need to initiate the process of importing product data into the AI system for enhanced product recommendations and knowledge. | | `KOMMO_LIST_CATALOGS` | List Kommo Catalogs | Tool to retrieve a list of catalogs (lists) from Kommo CRM. Use when you need to fetch available catalogs in the account. | | `KOMMO_LIST_COMPANIES` | List Kommo Companies | Action to list Kommo companies with various filter options. | | `KOMMO_LIST_CONTACTS` | List Kommo Contacts | Action to list contacts in Kommo CRM. | | `KOMMO_LIST_CONVERSATIONS` | List Kommo Conversations | Tool to get a list of conversations from Kommo CRM. Use when you need to retrieve conversations with pagination support. | | `KOMMO_LIST_CUSTOM_FIELDS` | List Kommo Custom Fields | Action to list custom fields in Kommo CRM. | | `KOMMO_LIST_ENTITY_FILES` | List Entity Files | Tool to retrieve a list of files attached to an entity in Kommo CRM. Use when you need to see all files (documents, images, PDFs, etc.) that have been uploaded to a specific lead, contact, or company. | | `KOMMO_LIST_ENTITY_LINKS` | List Kommo Entity Links | Tool to get a list of entities linked to a specific entity in Kommo. Use when you need to retrieve contacts, companies, or leads linked to another entity. | | `KOMMO_LIST_ENTITY_NOTES` | List Kommo Entity Notes | Tool to get a list of all notes for an entity type (leads, contacts, or companies) in Kommo CRM. Use when you need to retrieve notes across all entities of a specific type, not just for a single entity. | | `KOMMO_LIST_ENTITY_TAGS` | List Kommo Entity Tags | Tool to get a list of tags for an entity type (leads, contacts, or companies). Use when you need to retrieve available tags for a specific entity type in Kommo CRM. | | `KOMMO_LIST_EVENTS` | List Kommo Events | Tool to get a list of events from Kommo CRM with filtering options. Use when you need to retrieve events history, track changes to entities (leads, contacts, companies), or monitor specific event types like status changes, field updates, or assignment changes. | | `KOMMO_LIST_EVENT_TYPES` | List Kommo Event Types | Tool to get a list of all available event types in Kommo CRM. Use when you need to see what event types can be used for filtering events or configuring webhooks. | | `KOMMO_LIST_FIELD_GROUPS` | List Kommo Field Groups | Tool to get a list of custom field groups for an entity type in Kommo CRM. Use when you need to retrieve field group information to organize custom fields. | | `KOMMO_LIST_FILES` | List Kommo Files | Tool to retrieve a list of files from Kommo Drive. Use when you need to search, filter, or browse files stored in the Kommo CRM system. Supports filtering by name, extension, size, date, creator, and other criteria. | | `KOMMO_LIST_INCOMING_LEADS` | List Incoming Leads | Tool to get a list of incoming leads (unsorted) from Kommo with filtering and pagination. Use when you need to retrieve unprocessed leads that haven't been sorted into pipelines yet. Supports filtering by category (sip, mail, forms, chats), UID, and pipeline ID. | | `KOMMO_LIST_LEADS` | List Kommo Leads | Action to list leads in Kommo CRM. | | `KOMMO_LIST_LEADS_PIPELINES` | List Kommo Lead Pipelines | Action to list lead pipelines in Kommo CRM. | | `KOMMO_LIST_LOSS_REASONS` | List Kommo Loss Reasons | Action to list loss reasons for leads in Kommo CRM. Use when you need to retrieve all available loss reasons that can be assigned to lost leads. | | `KOMMO_LIST_NOTES_BY_ENTITY` | List Kommo Notes By Entity | Tool to get notes for a specific entity by its ID in Kommo CRM. Use when you need to retrieve all notes associated with a lead, contact, or company. | | `KOMMO_LIST_PIPELINE_STAGES` | List Kommo Pipeline Stages | Action to list stages of a pipeline in Kommo CRM. | | `KOMMO_LIST_ROLES` | List Kommo User Roles | Tool to get a list of user roles in Kommo CRM. Use when you need to retrieve available user roles and their permissions. | | `KOMMO_LIST_SOURCES` | List Kommo Lead Sources | Tool to get a list of lead sources in Kommo CRM. Use when you need to retrieve all available lead sources that can be assigned to leads. | | `KOMMO_LIST_TASKS` | List Kommo Tasks | Action to list tasks in Kommo CRM. | | `KOMMO_LIST_TEMPLATES` | List Kommo Templates | Tool to get a list of message templates in Kommo CRM. Use when you need to retrieve chat response templates that can be utilized in cards and bots. | | `KOMMO_LIST_USERS` | List Kommo Users | Tool to get a list of users from Kommo CRM with pagination support. Use when you need to retrieve all users in the account or paginate through the users list. | | `KOMMO_LIST_WEBHOOKS` | List Kommo Webhooks | Tool to get a list of registered webhooks for the Kommo account. Use when you need to view all webhook configurations and their settings. | | `KOMMO_LIST_WEBSITE_BUTTONS` | List Kommo Website Buttons | Tool to get a list of website chat button (CRM Plugin) objects from Kommo. Use when you need to retrieve all configured website chat buttons in the account. Supports pagination for large result sets. | | `KOMMO_LIST_WIDGETS` | List Kommo Widgets | Tool to get a list of installed widgets in Kommo. Use when you need to see which widgets are installed and their current status in the account. | | `KOMMO_UPDATE_COMPANY` | Update Kommo Company | Action to update a single company in Kommo CRM. | | `KOMMO_UPDATE_CONTACT` | Update Kommo Contact | Action to update contact information in Kommo CRM by contact ID. | | `KOMMO_UPDATE_LEAD` | Update Kommo Lead | Action to update an existing lead in Kommo CRM. Allows modifying lead properties including name, price, pipeline stage, responsible user, tags, and custom fields. Requires the lead ID to be specified. | | `KOMMO_UPDATE_TASK` | Update Kommo Task | Action to update a task in Kommo CRM. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Kommo MCP server is an implementation of the Model Context Protocol that connects your AI agent to Kommo. It provides structured and secure access so your agent can perform Kommo operations on your behalf through a secure, permission-based interface. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. 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 ### 1. Getting API Keys for OpenAI and Composio OpenAI API Key - Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) 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](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Go to Settings and copy your API key. - This key lets your Mastra agent talk to Composio and reach Kommo through MCP. ### 2. Install dependencies 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 ```bash npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv ``` ### 3. Set up environment variables 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 ```bash COMPOSIO_API_KEY=your_composio_api_key_here COMPOSIO_USER_ID=your_user_id_here OPENAI_API_KEY=your_openai_api_key_here ``` ### 4. Import libraries and validate environment 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 ```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, }); ``` ### 5. Create a Tool Router session for Kommo 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 ```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); ``` ### 6. Configure Mastra MCP client and fetch tools 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 ```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); ``` ### 7. Create the Mastra agent 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 ```typescript const agent = new Agent({ name: "kommo-mastra-agent", instructions: "You are an AI agent with Kommo tools via Composio.", model: "openai/gpt-5", }); ``` ### 8. Set up interactive chat interface 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 ```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); }); ``` ## Complete Code ```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](https://composio.dev/toolkits/kommo/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/kommo/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/kommo/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/kommo/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/kommo/framework/codex) - [OpenClaw](https://composio.dev/toolkits/kommo/framework/openclaw) - [Hermes](https://composio.dev/toolkits/kommo/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/kommo/framework/cli) - [Google ADK](https://composio.dev/toolkits/kommo/framework/google-adk) - [LangChain](https://composio.dev/toolkits/kommo/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/kommo/framework/ai-sdk) - [LlamaIndex](https://composio.dev/toolkits/kommo/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/kommo/framework/crew-ai) ## Related Toolkits - [Hubspot](https://composio.dev/toolkits/hubspot) - 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](https://composio.dev/toolkits/pipedrive) - 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](https://composio.dev/toolkits/salesforce) - 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. - [Apollo](https://composio.dev/toolkits/apollo) - Apollo is a CRM and lead generation platform that helps businesses discover contacts and manage sales pipelines. Use it to streamline customer outreach and track your deals from one place. - [Attio](https://composio.dev/toolkits/attio) - Attio is a customizable CRM and workspace for managing your team's relationships and workflows. It helps teams organize contacts, automate tasks, and collaborate more efficiently. - [Acculynx](https://composio.dev/toolkits/acculynx) - AccuLynx is a cloud-based roofing business management software for contractors. It streamlines project tracking, lead management, and document sharing. - [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time. - [Affinity](https://composio.dev/toolkits/affinity) - Affinity is a relationship intelligence CRM that helps private capital investors find, manage, and close more deals. It streamlines deal flow and surfaces key connections to help you win opportunities. - [Agencyzoom](https://composio.dev/toolkits/agencyzoom) - AgencyZoom is a sales and performance platform built for P&C insurance agencies. It helps agents boost sales, retain clients, and analyze producer results in one place. - [Bettercontact](https://composio.dev/toolkits/bettercontact) - Bettercontact is a smart contact enrichment tool for finding emails and phone numbers. It helps boost lead generation with automated, waterfall search across multiple sources. - [Blackbaud](https://composio.dev/toolkits/blackbaud) - Blackbaud provides cloud-based software for nonprofits, schools, and healthcare institutions. It streamlines fundraising, donor management, and mission-driven operations. - [Brilliant directories](https://composio.dev/toolkits/brilliant_directories) - Brilliant Directories is an all-in-one platform for building and managing online membership communities and business directories. It streamlines listings, member management, and engagement tools into a single, easy interface. - [Capsule crm](https://composio.dev/toolkits/capsule_crm) - Capsule CRM is a user-friendly CRM platform for managing contacts and sales pipelines. It helps businesses organize relationships and streamline their sales process efficiently. - [Centralstationcrm](https://composio.dev/toolkits/centralstationcrm) - CentralStationCRM is an easy-to-use CRM software focused on collaboration and long-term customer relationships. It helps teams manage contacts, deals, and communications all in one place. - [Clientary](https://composio.dev/toolkits/clientary) - Clientary is a platform for managing clients, invoices, projects, proposals, and more. It streamlines client work and saves you serious admin time. - [Close](https://composio.dev/toolkits/close) - Close is a CRM platform built for sales teams, combining calling, email automation, and predictive dialers. It streamlines sales workflows and boosts productivity with all-in-one communication tools. - [Dropcontact](https://composio.dev/toolkits/dropcontact) - Dropcontact is a B2B email finder and data enrichment service for professionals. It delivers verified email addresses and enriches contact info with up-to-date data. - [Dynamics365](https://composio.dev/toolkits/dynamics365) - Dynamics 365 is Microsoft's platform combining CRM, ERP, and productivity apps. It streamlines sales, marketing, service, and operations in one place. - [Espocrm](https://composio.dev/toolkits/espocrm) - EspoCRM is an open-source web application for managing customer relationships. It helps businesses organize contacts, track leads, and streamline their sales process. - [Fireberry](https://composio.dev/toolkits/fireberry) - Fireberry is a CRM platform that streamlines customer and sales management. It helps businesses organize contacts, automate sales, and integrate with other business tools. ## Frequently Asked Questions ### 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. --- [See all toolkits](https://composio.dev/toolkits) ยท [Composio docs](https://docs.composio.dev/llms.txt)