Skip to main content
Glama

Related Servers

Alternatives to mcp-b24

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      A
      maintenance
      Universal MCP server for the Bitrix24 REST API, enabling full read and write access to CRM, tasks, calendar, disk, and more. Supports any MCP client with stdio or Streamable HTTP transport.
      88
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for interacting with Bitrix24 REST API, enabling CRUD operations on deals, contacts, companies, users, leads, and tasks, plus analytics and risk assessment.
      2
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides a REST API and MCP server to interact with Bitrix24 CRM, enabling CRUD operations on entities like deals, leads, contacts, and tasks via natural language.
      5 npm
      13
      -
    • F
      license
      Not graded
      quality
      C
      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

    B3.1/5.0

    Scored across 43 tools

    Disambiguation3/5

    Most tools map to clearly distinct Bitrix24 modules, but several boundaries blur: bx24_users and bx24_hr both cover user creation/updating, bx24_im and bx24_im_chat both expose messaging/counters, and bx24_workflows overlaps with bx24_crm_automation around robots/triggers. The descriptions and method prefixes help, but an agent still needs to read carefully to avoid misselection.

    Naming Consistency5/5

    All 43 tools follow the same `bx24_<module>` snake_case convention with noun-style module names, making the namespace highly predictable. The only mild oddity is `bx24_call` being a generic REST call alongside telephony calls, but the naming pattern itself is uniform.

    Tool Count3/5

    43 tools is large and exceeds the comfortable range for a single MCP surface, but the server's scope is the full Bitrix24 ecosystem and each tool maps to a real module rather than a redundant operation. Still, the count is heavy enough that an agent will need deliberate filtering and selection.

    Completeness4/5

    The set covers CRM entities, tasks, disk, messenger, calendar, telephony, automation, HR, and platform utilities with CRUD/lifecycle operations, and `bx24_call` provides an escape hatch for unspecified REST methods. There are minor gaps such as no dedicated sale/order or standalone CRM status module, but common workflows are not dead-ended.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues