Kylas CRM

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/kylastech-kylas-crm

About

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools

12 read · 2 write · 0 delete

Secrets

1 (API keys, tokens or passwords)

Install scripts

Not scanned yet

Runs as

Python package

Tools (14)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• create_lead

  Create a lead in Kylas CRM with only the fields the user wants (no static field list). You MUST call get_lead_field_instructions FIRST to get valid API names and Field IDs. Infer from user context which fields to send; include only those in field_values. field_values: Map of field identifier to value. - Standard fields: use API name as key at top level (e.g. firstName, lastName, companyName, emails, phoneNumbers, leadSource, isNew). - Custom fields: MUST be under "customFieldValues" with **internal name** as key (e.g. "customFieldValues": {"cfLeadCheck": "Checked"}). Do not use field ID as k…

• 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/datetime as-is (do not convert to UTC). - For create_lead: when the user provides a datetime in their own words (e.g. "11th Feb 2026 at 7:30 AM"), interpret it in this timezone, convert to UTC using parse_…

• 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 lead's current pipeline or from lookup_pipelines).

• 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", "value": pipeline_id}, {"field": "pipelineStage", "operator": "equal", "value": stage_id}]. If the user said "open leads" or "closed leads" and more than one stage has the same forecastingType, ask wh…

• 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 user confirms, call get_pipeline_stages with that pipeline ID to get stages for that pipeline, then search_leads. query: Search string. Use "name:<pipeline_name>" or just the pipeline name; empty stri…

• 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. Use "name:<product_name>" (e.g. "name:Widget") or just the product name (e.g. "Widget"); the server will send name:value to the API. page: 0-based page (default 0). size: Max 50 (default 50).

• 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 leave default to list all when return_all=True. page: 0-based page (default 0). Ignored when return_all=True. size: Page size, max 50 (default 50). Used per page when return_all=True. return_all: If …

• 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", "Asia/Calcutta") → use result in field_values. local_datetime: Datetime as the user said it (e.g. "11 Feb 2026 7:30 AM", "11th Feb 2026 at 7:30 am"). timezone: IANA timezone from get_current_user (e.g.…

• 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. days: Minimum days with no activity (e.g. 10 for "no activity since 10 days"). time_zone: IANA timezone for threshold (e.g. America/New_York). Default: Asia/Calcutta. page: 0-based page (default 0). size: Page size, max 100 (default 20). sort: Sort e.g. "createdAt,desc" (default).

• 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. filters: List of filter objects. Each must have: - field (str): Field internal/API name (e.g. firstName, country, source, createdAt). - operator (str): One of the allowed operators for that field type (e.g. equal, contains, greater). - value: Value to compare. For PICK_LIST/MULTI_PICKLIST use Option ID (number), except requirementCurrency, companyBusinessType, country, timezone, companyIndustry — use interna…

• 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. search_term: The term to search for (e.g. "akshay", "acme"). page: 0-based page (default 0). size: Page size, max 100 (default 20). sort: Sort e.g. "updatedAt,desc" (default).

• update_lead

  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. lead_id: The lead ID to update (e.g. from search_leads or search_leads_by_term results). field_values: Map of field identifier to value (same as create_lead: firstName, lastName, email, phone with phone_country_code, customFieldValues, picklist Option IDs, date/datetime i…

Signals

Stars

12

Forks

2

Open issues

0

Weekly downloads

29

Last commit

Feb 9, 2026 (8 months ago)

Last release

Feb 9, 2026 (8 months ago)

Last package publish

Feb 9, 2026 (8 months ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name

io.github.kylastech/kylas-crm

Version

1.0.4

Auth

API key

Packages

pypi kylas-crm-mcp-server

License

MIT

Repository

github.com/kylastech/kylas-crm-mcp-server

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql