Log inSubmit server
Kylas CRM logo

Kylas CRM

Manage Kylas CRM leads through MCP tools for creation, search, lookups, and idle-lead detection.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Kylas CRM

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "kylas-crm-2": {
      "command": "uvx",
      "args": [
        "kylas-crm-mcp-server"
      ],
      "env": {
        "KYLAS_API_KEY": "YOUR_VALUE_HERE",
        "KYLAS_BASE_URL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 14 tools correctly (8d ago).

Overview

The Kylas CRM MCP server connects MCP clients to Kylas CRM for lead creation, search, filtering, and related lookups. It runs as a Python 3.10+ process over stdio and uses a Kylas API key to access the CRM API. Use it when an agent needs to create leads, resolve CRM IDs, inspect lead fields, or find leads without recent activity. Cursor and Claude Desktop are named client examples, and other MCP clients can start the stdio process.

Use cases

  • Create leads from agent-provided information
  • Search and filter Kylas CRM leads
  • Resolve users, products, pipelines, and stages
  • Find leads without activity for a set number of days

Key features

  • Create leads with dynamic fields
  • Search and filter leads
  • Retrieve lead field instructions
  • Resolve users and products to IDs
  • Resolve pipelines and stages
  • Find idle leads

Tools14

What Kylas CRM lets your agent do. Expand a tool for its parameters.

Verified live~2.8k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

9/9 checks healthy over the last 46d

What it can do

From the 14 tools this server returned when we ran it.

Makes network requests · 1Read-only tools · 14
Network at startup2 connections
Files written at startup30

Observed 2026-10-20 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 1d ago via OSV.dev · kylas-crm-mcp-server (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars12Stargazers on the source repository.
Last commit1d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed14Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Kylas CRM works

What Kylas CRM MCP server does

The Kylas CRM MCP server exposes lead-focused operations from Kylas CRM through the Model Context Protocol. It supports creating leads, searching and filtering existing leads, and identifying leads that have had no activity for a specified number of days. The scope is limited to lead operations rather than a general-purpose interface for every Kylas CRM object.

It also provides lookup functions that help an agent work with Kylas identifiers. User names can be resolved to IDs for fields such as owner or creator, product names can be converted to product IDs, and pipeline and stage information can be retrieved for open, closed, or won leads. A schema instruction tool returns standard and custom lead fields along with picklist IDs, which can guide dynamically constructed lead requests.

How it works

The Kylas CRM MCP server uses stdio transport. An MCP client starts the Python module and exchanges messages with it through standard input and output. The server then uses the configured Kylas API connection to perform the requested lead operation.

The repository supports running python -m kylas_crm_mcp, or python main.py during development from the repository root. Its documented client examples are Cursor and Claude Desktop, although the transport is the standard MCP stdio pattern.

Setup and configuration

Python 3.10 or newer is required, along with a Kylas account and API key.

Set KYLAS_API_KEY before starting the server. KYLAS_BASE_URL is optional and defaults to https://api.kylas.io/v1. Configuration can be supplied through environment variables or a .env file. For container use, build the provided Docker image and pass the API key when starting the container with interactive input enabled.

Tools and capabilities

The available operations cover:

  • Retrieving standard and custom lead-field instructions and picklist IDs.
  • Creating leads with fields supplied from the agent’s context.
  • Searching and filtering leads by multiple criteria.
  • Finding leads with no activity for a chosen number of days.
  • Resolving users and products by name to their Kylas IDs.
  • Resolving pipelines and retrieving their stages.

These lookup operations are useful when a create or search request needs identifiers that are not already known to the agent.

Limitations and notes

The implementation is described as lead-only, so the documented capabilities should be evaluated against workflows that center on Kylas leads. A valid Kylas API key is required for normal use. The optional base URL can change the API endpoint, but the documented default points to Kylas’s version-one API path.

Development instructions include installing the development dependencies and running pytest.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Kylas CRM

Kylas CRM is an MCP server that connects MCP clients to the Kylas CRM API and provides lead tools for schema instructions, creation, searching, filtering, user and product lookups, pipeline and stage resolution, and finding idle leads. It communicates over stdio and requires a Kylas API key.

Install it with `pip install -e .` from the repository, or use the listed PyPI package after publication. The server requires Python 3.10 or newer, a Kylas account, and an API key.

Yes, Kylas CRM works with Cursor through its stdio transport. Cursor can start the Python server process and communicate with it through standard input and output.

Set `KYLAS_API_KEY` to run the server. `KYLAS_BASE_URL` is optional; when omitted, the server uses `https://api.kylas.io/v1`. Variables may be provided directly or through a `.env` file.

Related MCP servers

All in Customer Data Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewKylas CRM AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/kylas-crm-2?style=directory)](https://allmcps.com/mcp/kylas-crm-2)
HTML Embed
<a href="https://allmcps.com/mcp/kylas-crm-2"><img src="https://allmcps.com/api/badge/kylas-crm-2?style=directory" alt="Kylas CRM on AllMCPs" /></a>