Skip to main content
Glama
deriglazoff

Bitrix24 MCP Server

by deriglazoff

Related Servers

Alternatives to Bitrix24 MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to manage Bitrix24 CRM entities, tasks, project kanban boards, and Scrum sprints through an incoming webhook, requiring explicit user confirmation for all write operations.
      31
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Exposes Bitrix24 REST API to AI assistants, enabling management of tasks, CRM entities, call recordings (with local transcription), users, workgroups, and Knowledge Base articles.
      43
      7 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables language models to interact with Bitrix24 CRM, providing tools to manage deals, leads, contacts, tasks, activities, users, files, chat messages, and live chat sessions.
      7 npm
      1
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      A bridge between Claude (MCP) and Bitrix24 CRM/Tasks, enabling natural language interaction with leads, deals, contacts, companies, and tasks via a custom MCP server using incoming webhooks.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Production-grade MCP server for Bitrix24 Cloud with 45 tools, safe by default. Connects Claude Desktop to your Bitrix24 tenant for AI-driven CRM, tasks, messaging, and calendar operations.
      -

    TDQS

    C2.9/5.0

    Scored across 41 tools

    Disambiguation3/5

    Most tools are domain-specific and distinct, but there are several overlapping pairs: b24_crm_fields vs b24_read_custom_fields, b24_read_product_catalog vs b24_products_sections, and b24_disk_file_get vs b24_disk_file_content all have close boundaries that could cause misselection. The generic b24_call and b24_batch are clearly positioned as fallbacks, which helps, but the metadata/read tools remain ambiguous.

    Naming Consistency3/5

    The dominant pattern is b24_<domain>_<action> (e.g. b24_crm_list, b24_tasks_create), which is readable. However, the b24_read_* group reverses the order, several tools use noun-only names like b24_disk_storages and b24_products_sections, and utilities like b24_call/b24_batch/b24_test_connection do not follow the domain convention.

    Tool Count2/5

    41 tools is well above the comfortable range for an MCP server and feels heavy even for a broad platform like Bitrix24. Many modules have only one or two operations, and the presence of generic b24_call/b24_batch further reduces the need for such a large surface.

    Completeness3/5

    CRM, tasks, and products have fairly complete CRUD/lifecycle coverage, and the generic b24_call/b24_batch prevents total dead ends. However, calendar, disk, IM, feed, bizproc, and telephony are only partially covered—there is no calendar update/delete, task delete, disk folder create, or feed read, making the broader domain feel incomplete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues