bitrix24-mcp-server
Related Servers
Alternatives to bitrix24-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables 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.31MIT
- AlicenseAqualityAmaintenanceEnables interacting with Bitrix24 CRM via webhook API, offering tools for deals, contacts, tasks, users, files, and messaging.1244 npm1MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI agents to interact with Bitrix24 CRM for managing contacts, deals, tasks, and leads via a comprehensive set of tools. It supports advanced features like sales team monitoring, performance analytics, and automated CRM searching.-
- FlicenseNot gradedqualityDmaintenanceEnables language models to interact with Bitrix24 CRM, providing tools to manage deals, leads, contacts, tasks, activities, users, files, chat messages, and live chat sessions.4 npm1-
- AlicenseCqualityCmaintenanceEnables Claude to connect to a Bitrix24 portal through an incoming webhook and manage CRM records, tasks, disk files, calendar events, chat messages, business processes, and more via natural language.41MIT
- 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
Every tool has a clear, distinct purpose with detailed descriptions that differentiate overlapping operations (e.g., attach_file vs post_image vs im_post_file). No ambiguity exists among the 43 tools.
All tools follow a consistent 'bitrix24_<resource>_<action>' pattern, using snake_case throughout. The naming is predictable and uniform across all resources.
43 tools is on the high side, but it covers a broad domain (tasks, CRM, telephony, IM) and each tool has a specific role. A few transcription tools are redundant but serve different quality tiers.
Significant gaps exist: CRM entities (deals, contacts, leads) lack create, update, and delete operations. IM chat creation and user management are missing. This will cause agent failures when full lifecycle operations are needed.