Kylas CRM MCP Server (Lead Only)
Model Context Protocol server for Kylas CRM lead operations. Use it from Cursor, Claude Desktop, or any MCP client to create leads, search and filter leads, and look up users, products, and pipelines.
Features
- get_lead_field_instructions – Get lead schema (standard + custom fields, picklist IDs)
- create_lead – Create a lead with dynamic fields from user context
- search_leads – Search/filter leads by multiple criteria
- lookup_users – Resolve user names to IDs (for owner, created by, etc.)
- lookup_products – Resolve product names to IDs
- lookup_pipelines / get_pipeline_stages – Resolve pipeline and stage for open/closed/won leads
- search_idle_leads – Find leads with no activity for N days
Requirements
- Python 3.10+
- Kylas account and API key
Installation
pip install -e .
# or from PyPI (after publish): pip install kylas-crm-mcp-server
Configuration
Set environment variables (or use a .env file):
| Variable | Required | Description |
|---|---|---|
KYLAS_API_KEY |
Yes | Your Kylas API key |
KYLAS_BASE_URL |
No | API base URL (default: https://api.kylas.io/v1) |
Running the server
The server uses stdio transport (default for MCP). Run:
python -m kylas_crm_mcp
# or: python main.py (when developing from repo root)
MCP clients (e.g. Cursor) typically start this process and communicate via stdin/stdout.
Docker
docker build -t kylas-crm-mcp .
docker run -e KYLAS_API_KEY=your_key -i kylas-crm-mcp
Development
pip install -e ".[dev]"
pytest
Publishing to the MCP Marketplace
To publish this server to the official MCP Registry (so it appears in Cursor and other MCP clients):
- Publish the package to PyPI (the registry verifies ownership via your README).
- Install mcp-publisher and run
mcp-publisher login github, thenmcp-publisher publish.
See PUBLISHING.md for the full step-by-step guide.
License
See repository for license information.
Metadata
Release files for kylas-crm-mcp-server 1.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| kylas_crm_mcp_server-1.0.4.tar.gz | 23.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kylas_crm_mcp_server-1.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 47.8 kB
Release files / kylas_crm_mcp_server-1.0.4.tar.gz
| Download URL | kylas_crm_mcp_server-1.0.4.tar.gz |
|---|---|
| Size | 23.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0910906503b0448a9a7dbdfe63f25bd37fd79e8dce3a1c03070c1a79bbdc2158
|
|
BLAKE2b-256 checksum How to use checksums |
17b2630f68edb325f5e5b7ebceef1368cc7e6b0d9bef879ce315de930478d454
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Release files / kylas_crm_mcp_server-1.0.4-py3-none-any.whl
| Download URL | kylas_crm_mcp_server-1.0.4-py3-none-any.whl |
|---|---|
| Size | 24.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f21221045664948a9aaad7fa46f49e3c350512b025064466c3c38346ae74245e
|
|
BLAKE2b-256 checksum How to use checksums |
18fd73f44b7f8bf4a7a8758e1192d1daa97cf17b29624dd3b137e16c66299470
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Security for kylas-crm-mcp-server 1.0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.