mcp-b24
Related Servers
Alternatives to mcp-b24
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceUniversal 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.881MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for interacting with Bitrix24 REST API, enabling CRUD operations on deals, contacts, companies, users, leads, and tasks, plus analytics and risk assessment.2-
- AlicenseBqualityCmaintenanceEnables MCP clients to work with Bitrix24 tasks, projects, CRM entities, and universal lists via the Bitrix24 REST webhook. It provides 46 validated tools for reading and writing business data without caching or storing derivative copies.46MIT
- FlicenseNot gradedqualityDmaintenanceProvides 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 npm13-
- FlicenseNot gradedqualityCmaintenanceA 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.-
- FlicenseNot gradedqualityCmaintenanceProduction-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
Scored across 43 tools
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.
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.
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.
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.