n8n workflows for a Kommo CRM integration
Kommo MCP Server - n8n Workflows
A set of exported n8n workflows for Kommo CRM: a main orchestrator, individual webhooks per operation, and an example consumer agent
- 2 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The lead, contact and field update workflows write data to Kommo once configured for your instance
- Kommo credentials are stored in the n8n instance itself, not in this repository
Install
Manual install
Download the JSON files you need from the workflows folder of the wluciano/kommo-mcp-n8n repository, import them into your n8n instance via Import Workflow, and configure the Webhook nodes, Kommo credentials and variables for your infrastructure.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The lead, contact and field update workflows write data to Kommo once configured for your instance
- Kommo credentials are stored in the n8n instance itself, not in this repository
This is third-party code. Review the repository files before installing.
What it does
Despite the word MCP in the name, this is not an MCP server but a set of n8n workflow JSON files meant to be imported into your own n8n instance. The main mcp-server.json workflow sets the overall service logic, while individual webhooks like webhook-get-pipelines.json, webhook-update-lead.json or webhook-get-custom-fields.json implement specific Kommo CRM operations: fetching pipelines, updating a lead, a contact or a custom field. A separate agent-example.json shows a sample consumer workflow calling these webhooks. After import, each workflow needs adjusting for your own instance: Webhook nodes, credentials and environment variables.
Who it is for. For those already building automation on n8n who want a ready set of Kommo CRM workflows as a starting point, not an MCP server for an agent.
Good fit when
- You already run n8n and want ready webhooks for Kommo operations instead of building from scratch
- You want an architecture example: a main orchestrator plus individual webhooks per operation
- You are ready to adjust the imported workflows for your own credentials and nodes
Not a fit when
- You are looking for a real MCP server to connect directly to Claude Code, Cursor or another agent: there is none here
- You do not have your own n8n instance to import these files into
Example request
Import webhook-get-pipelines.json into n8n and configure it for my Kommo accountLimitations
The repository and mcp-server.json file name is misleading: there is no real MCP protocol, JSON-RPC or stdio server here, just exported n8n graphs. Documentation is mostly screenshots of the author's specific workflows without a detailed breakdown of nodes and parameters, so adjustment requires reading the JSON structure by hand. It needs your own running n8n instance and separately configured Kommo credentials.
How to disable. Delete the imported workflows from your n8n instance.
FAQ
Is this an MCP server I can connect to Claude Code?
No, despite the name, these are n8n workflows. Connecting to an MCP client needs a separate, real MCP server.
What do I need to make it work?
Your own n8n instance, importing the files from the workflows folder, and configuring Kommo credentials and Webhook nodes for your infrastructure.
Discussion
No questions or reviews yet.
Related
WorkflowsAn MCP server for n8n: the agent manages workflows and their executions through the n8n API in natural language, creating, updating, activating and running them
An MCP server with n8n node and template knowledge: the agent picks nodes, validates configs and, with API access, creates workflows in your n8n
An MCP server for n8n: an assistant creates, runs and deletes workflows through the API, checks executions and tags and requests a security audit
A plugin from the n8n team: 13 skills and a bundled MCP connection teach Claude Code and Codex to build, edit and validate n8n workflows
MCP server that builds n8n workflows as local JSON files: nodes, links, validation and version matching, no running n8n needed.
n8n Workflows: the Zie619 collection
n8n-workflows
An open collection of 4,343 n8n workflows: 365 integrations, 15 categories, search and a web interface, JSON download
README in short
The Spanish README describes the repository as a store of exported n8n JSON files for Kommo CRM, shows screenshots of the main workflow and individual webhooks for getting fields, entity info, pipelines, and updating a contact, field and lead, shows an example agent workflow, and describes usage: importing files from workflows into your own n8n instance, configuring nodes and credentials, testing with HTTP requests, and re-exporting after changes.