Skip to main content
Glama
john7ross

BitrixMCP

by john7ross
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to BitrixMCP

No user-submitted related servers found.

    Related Servers

    • mcp-b24

      kostikpenzin
      A
      license
      B
      quality
      A
      maintenance
      A complete MCP server over the Bitrix24 REST API, enabling CRM, tasks, chats, files, calendar, HR, smart processes, mail, telephony, business processes, and events through 30 tools and ~290 actions. Supports incoming webhook or OAuth 2.0 authentication and works over stdio or Streamable HTTP.
      43
      35 npm
      1
      MIT

    • fast-bitrix24-mcp

      darkClaw921
      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
      -

    • bitrix24-mcp-server

      EricVanin
      A
      license
      Not graded
      quality
      B
      maintenance
      A secure, self-hosted MCP server for Bitrix24 CRM that enables reading CRM data and performing confirmation-gated writes through schema discovery and OAuth integration.
      4 npm
      MIT

    • Bitrix24 MCP Server

      OneAtDrt
      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.
      4 npm
      13
      -

    • Bitrix24 MCP Bridge

      KarpovPartnersCom
      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.
      -
    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

    B3.1/5.0

    Scored across 52 tools

    Disambiguation3/5

    Most tools are scoped to a clear Bitrix24 domain, but there are several close pairs (catalog.product.list vs crm.product.list, user.get vs user.search, workflow templates vs document templates), and the universal b24_call overlaps with every typed wrapper. Descriptions mostly resolve the ambiguity, but an agent must read carefully before selecting.

    Naming Consistency3/5

    All names use snake_case with a consistent b24_ prefix, but the underlying pattern is inconsistent: b24_crm_list/delete/fields sit alongside b24_crm_activity_add, b24_task_get, b24_scrum_sprint_list, and noun-style names like b24_telephony_statistics or b24_group_users. It is readable but not a uniform verb_noun convention.

    Tool Count1/5

    At 52 tools, this is far beyond the recommended 3-15 range and above the 50+ extreme threshold. Since b24_call already exposes the entire REST API, many typed wrappers are conveniences that inflate the selection space rather than earn their place.

    Completeness4/5

    The universal b24_call means there are no true dead ends, and b24_list_methods helps discovery. However, the typed layer is uneven: task/calendar updates, CRM add/update, disk upload/list, and several delete operations are absent, so agents must fall back to b24_call for standard lifecycle steps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources