Skip to main content
Glama
akshaykylas94

Kylas CRM MCP Server

by akshaykylas94
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Kylas CRM MCP Server

No user-submitted related servers found.

    Related Servers

    • IndiaMART MCP Server

      Techmatic-sys
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables managing IndiaMART buyer leads through natural language, including fetching, searching, analyzing, and updating lead pipeline stages.
      MIT
    • Kylas CRM MCP Server by kylastech

      Kylas CRM MCP Serverofficial

      kylastech
      A
      license
      A
      quality
      C
      maintenance
      Model Context Protocol server for Kylas CRM lead operations, enabling lead creation, search/filter, and lookup of users, products, and pipelines.
      14
      12
      MIT

    • Lead Details MCP

      aadarshlodhi
      F
      license
      Not graded
      quality
      D
      maintenance
      Manages leads and sends emails directly from Claude chat, with tools to add, search, filter, and update leads, plus email capabilities.
      -

    • TeroAI noCRM MCP Connector

      RyansitoTeroAI
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables ChatGPT to interact with noCRM leads for outreach tracking, including listing, retrieving, creating leads and adding comments, without destructive operations.
      -

    • Zoho CRM MCP Server

      junnaisystems
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Zoho CRM data through secure OAuth authentication, supporting comprehensive CRM operations including record management, search, bulk operations, and lead conversion.
      3
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have distinct purposes: create_lead, get_lead_field_instructions, search_leads, and search_idle_leads are clearly differentiated. However, the four lookup tools (lookup_pipelines, lookup_products, lookup_users, get_pipeline_stages) could cause confusion as they all serve similar 'lookup' functions but for different entities, requiring careful reading of descriptions to distinguish them.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern (e.g., create_lead, lookup_pipelines, search_leads) with snake_case throughout. The only minor deviation is get_lead_field_instructions, which uses 'get' instead of 'lookup' or 'search', but it still fits the verb_noun style and is understandable.

    Tool Count5/5

    With 8 tools, the count is well-scoped for a CRM server, covering core operations like lead creation, field instructions, searching, and lookups for pipelines, products, and users. Each tool serves a specific purpose without bloat, aligning with typical CRM workflows.

    Completeness4/5

    The toolset provides strong coverage for lead management, including creation, searching (with filters and idle leads), and necessary lookups. A minor gap is the lack of update or delete operations for leads, which might limit full CRUD lifecycle management, but agents can still handle core tasks effectively with the available tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources