Bitrix24 Tasks, CRM & Lists MCP Server
Related Servers
Alternatives to Bitrix24 Tasks, CRM & Lists MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceA 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.4351 npm2MIT
- AlicenseBqualityCmaintenanceMCP server that gives AI assistants direct access to Bitrix24 portal through an inbound webhook, enabling management of tasks, kanban boards, reports, chats, files, and knowledge base.48MIT
- 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.-
- 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.882MIT
- 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-
- AlicenseAqualityAmaintenanceEnables interacting with Bitrix24 CRM via webhook API, offering tools for deals, contacts, tasks, users, files, and messaging.1249 npm1MIT
TDQS
Scored across 46 tools
Most tools are clearly separated by resource and action (tasks, deals, contacts, users, projects, calendar, Lists). The main boundary risks are bitrix_create_activity overlapping semantically with bitrix_schedule_meeting and bitrix_create_task, but the descriptions clarify the module context well.
The bitrix_ prefix with snake_case verb_noun naming is consistent throughout, e.g. bitrix_list_tasks, bitrix_get_task, bitrix_create_deal. Minor deviations like bitrix_lists_search_letters and bitrix_find_contact are still readable and do not break the overall pattern.
With 46 tools, the server exceeds the 25+ threshold and feels heavy even though it covers three domains. The large surface creates selection overhead and could be better scoped or split into separate servers.
Core create/read/update flows exist for tasks, deals, contacts, and projects, plus useful extras like calendar scheduling and time reports. However, there are no delete or archive tools for any entity, activities lack update/delete, and meetings cannot be updated or cancelled.