Bitrix24 MCP

What bit2beat/bitrix24-mcp MCP server does

The bit2beat/bitrix24-mcp MCP server gives Claude access to selected Bitrix24 portal operations over the Model Context Protocol. Its documented coverage spans CRM entities, tasks, users, departments, disk storage, calendars, chat, notifications, the Live Feed, workgroups, business processes, telephony call history, and the product catalog.

CRM tools can list records with filters and pagination, retrieve individual records, inspect standard and custom fields, create, update, or delete records, and add timeline comments or activities. Task tools support listing, detail retrieval, creation, updates, and completion. File-related tools can browse storages and folders, retrieve file metadata and download links, and upload files.

The README also documents portal configuration operations, including exporting configuration data, comparing configurations, and applying a configuration to another portal. It describes a raw Bitrix24 REST option for direct method and batch requests, although the supplied tool list does not enumerate those operations individually.

How it works

The bit2beat/bitrix24-mcp MCP server calls Bitrix24 through an incoming webhook URL stored in the B24_DEFAULT_WEBHOOK environment variable. The webhook is created by a Bitrix24 portal administrator and includes scopes such as crm, task, disk, calendar, im, bizproc, catalog, and telephony.

Bitrix24 scopes permit both reading and writing within an enabled module; they do not provide a built-in read-only mode. A reduced set of scopes can limit which modules are reachable, but it cannot technically prevent writes inside an enabled scope. The README describes a trust-based read-only approach and a separate instance with only read tools as alternatives. Tools report when a requested operation requires a scope that the webhook does not have.

Setup and configuration

The project requires Node.js 18 or later and is intended for Claude Desktop or Claude Code. Setup involves cloning the repository, running npm install, creating an incoming Bitrix24 webhook, and placing a Node command in the Claude Desktop MCP configuration. The command points to the local index.js file and passes B24_DEFAULT_WEBHOOK in the server environment.

The webhook URL grants API access to the portal and should be kept private. Administrators can later return to Bitrix24's Applications, Webhooks, and Incoming webhooks settings to change its permissions. After editing the Claude Desktop configuration, restart the client so the tools become available.

Tools and capabilities

• Test the webhook and inspect portal and user-permission information.
• Manage CRM records, fields, and timeline entries.
• List, create, update, and complete tasks.
• Inspect users, departments, groups, and projects.
• Browse and upload Bitrix24 disk files.
• List and create calendar events.
• Send chat messages, personal notifications, and Live Feed posts.
• List active workflows and start a business process on a record.
• Query telephony call history and product details.

Limitations and notes

The bit2beat/bitrix24-mcp MCP server depends on the permissions and scopes of the configured Bitrix24 webhook. Creating that webhook requires administrator access. The supplied documentation describes write-capable module scopes, so access should be planned carefully when the agent is used for reporting or analysis. The repository setup also assumes a local Node.js installation and a locally cloned project rather than a hosted endpoint.