Kylas CRM MCP Server

MCP server for Kylas CRM: create, search, and manage leads. Requires KYLAS_API_KEY. The kylas crm mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 9 defined tools rather than through you.

What it actually does

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.

• 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

Adding it to your client

The server ships on PyPI as kylas-crm-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Its toolset

Everything the assistant can do here goes through one of these:

• 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
• search_idle_leads — Find leads with no activity for N days
• Variable — Required
• KYLAS_API_KEY — Yes
• KYLAS_BASE_URL — No

Configuration

You will need 2 environment variables: KYLAS_API_KEY, KYLAS_BASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Python 3.10+ - Kylas account and API key

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Kylas CRM.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the kylas crm mcp server does with a few real requests.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Kylas CRM's toolset — get_lead_field_instructions, create_lead, search_leads and 6 more — is a fair guide to whether it matches your workflow. It is maintained by akshaykylas94; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Kylas CRM's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.