Kylas CRM MCP server

Read from the package source without running it. The installed server may list more.

• create_leadwrite action

  Create a lead in Kylas CRM with only the fields the user wants (no static field list).

• get_current_user

  Get the current authenticated user's profile from Kylas (GET /users/me). Call this whenever a date or datetime-related query is involved. Returns timezone (IANA, e.g. Asia/Calcutta), recordActions (call, email, sms, etc.), name, and other profile fields. - For filtering (search_leads, search_idle_leads): use the returned timezone as the timeZone in date/datetime filters; keep the user's date/datet

• get_lead

  Get full details of a lead by ID (GET /leads/{id}). Use when the user asks for complete lead info, lead details, or to view a specific lead. lead_id: The lead ID (e.g. from search_leads or search_leads_by_term results).

• get_lead_field_instructions

  Get all lead fields for the current tenant. CALL THIS FIRST before creating a lead. Returns a cheat sheet with API names (standard fields), Field IDs (custom fields), and Picklist Option IDs. Use this to build field_values for create_lead based on what the user wants—do not use static fields.

• get_pipeline_details

  Get full pipeline details by ID (GET /pipelines/{id}): stages plus unqualifiedReasons and lostReasons. Call this when moving a lead to Closed Lost or Closed Unqualified. Present the relevant reasons list to the user, ask them to pick one, then call update_lead with pipelineStageReason set to that exact string (e.g. "No followup", "Booked with competitor"). pipeline_id: The pipeline ID (from the le

• get_pipeline_stages

  Get stages for a pipeline. Call this only after the user has confirmed which pipeline to use (from lookup_pipelines). Do not call before pipeline confirmation. Returns pipeline name and list of stages for that pipeline only, with id, name, and forecastingType (OPEN, CLOSED_WON, CLOSED_LOST, CLOSED_UNQUALIFIED). Use the stage IDs in search_leads: filters [{"field": "pipeline", "operator": "equal",

• lookup_pipelines

  Look up pipelines by name (for leads). Use when the user asks for leads by stage (e.g. open/closed/won/lost) but does not specify which pipeline. - Call this first; do NOT call get_pipeline_stages until after the user confirms the pipeline. - Present the pipeline(s) (id and name) and ask the user which pipeline they mean. If only one pipeline is found, still ask for confirmation. - Only after the

• lookup_products

  Look up products by name. Use this BEFORE filtering leads by product when the user gives a product name. - If one product is found, use that product's ID in search_leads (e.g. {"field": "products", "operator": "equal", "value": <id>}). - If multiple products are found, ask the user which product they mean (list the options), then use the chosen product's ID in search_leads. query: Search string. U

• lookup_users

  Look up users by name, or list all users in the system. - Use return_all=True (with query "name:" or empty) to fetch all users in one response (all pages combined). - For name search: query in field:value form (e.g. "firstName:last", "name:Last"). If one user is found, use that ID in search_leads; if multiple, ask which one. query: Search string (e.g. "firstName:last", "name:Last"). Use "name:" or

• parse_datetime_to_utc_iso_tool

  Parse a datetime string in the user's timezone and return UTC ISO string for the Kylas API. Call get_current_user first to get the user's timezone. Use the returned string in create_lead field_values for date/datetime fields. Example: user says "create lead with follow-up 11th Feb 2026 at 7:30 AM" → get_current_user → timezone Asia/Calcutta → parse_datetime_to_utc_iso_tool("11 Feb 2026 7:30 AM", "

• search_idle_leads

  Search for idle/stagnant leads: no activity for at least the given number of days. Uses both updatedAt and latestActivityCreatedAt; a lead is returned only when BOTH dates are on or before (today − days), so the effective last activity is before the threshold.

• search_leads

  Search/filter leads. Only fields marked [FILTERABLE] in get_lead_field_instructions can be used. Call get_lead_field_instructions first to get filterable fields and their types.

• search_leads_by_term

  Search leads by a single term across multiple fields (firstName, lastName, companyName, phoneNumbers, emails, etc.). Use this when the user asks for "leads with X", "leads containing Y", or "leads named Z" without specifying which field to filter on. For filtering by a specific field (e.g. "leads where phone number is X"), use search_leads instead.

• update_leadwrite action

  Update a lead in Kylas CRM. Fetches the lead first, merges your field_values into it, then PUTs the full body. Same field_values format as create_lead. Call get_lead_field_instructions first for API names and custom field internal names. For owner: use lookup_users to get the user ID, then pass ownerId: <id> in field_values.

• Code scan2 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 21 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

Kylas CRM: common questions

Is Kylas CRM MCP server safe?

Yes, by our scan: it is graded A (85/100). Read the Kylas CRM safety report

How do I install Kylas CRM?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Kylas CRM need an API key?

Yes. The registry entry asks for KYLAS_API_KEY.

Is Kylas CRM maintained?

The last commit was 36 days ago (2026-09-07). The latest release is v1.0.4.

What can I use instead of Kylas CRM?

Servers from other publishers that do the same job: Salesforce MCP server, Follow Up Boss MCP server and Gambot WhatsApp Business API MCP server. Compare all Kylas CRM alternatives.