bit2beat/bitrix24-mcp

A Model Context Protocol (MCP) server that connects **Claude** to your **Bitrix24** portal via an incoming webhook.
Once configured, Claude can read and write CRM records, manage tasks, browse your disk, send notifications, query the product catalog, run business processes, and much more — all from natural conversation.
Built and maintained by **Bit2Beat** — Bitrix24 specialists.
---
Features
| Area | What Claude can do |
|---|---|
| **CRM** | List, get, create, update, and delete deals, contacts, companies, leads, and Smart Process items. Add timeline comments. |
| **Tasks** | List, get, create, update, and complete tasks. |
| **Users & Departments** | List active users and the organizational structure. |
| **Disk** | Browse storages and folders, get file info and download links, upload files. |
| **Calendar** | List and create calendar events. |
| **Chat & Notifications** | Send private messages and personal notifications. |
| **Live Feed** | Post messages to the activity feed. |
| **Groups** | List workgroups and projects. |
| **Business Processes** | List active workflows and start new ones. |
| **Telephony** | Query the call history log. |
| **Product Catalog** | List, get, create, and update products and sections. |
| **Configuration** | Export the full portal config (pipelines, stages, custom fields, automations) to JSON, compare two configs, and apply one config to another portal. |
| **Raw API** | Call any Bitrix24 REST method directly, including batch requests. |
---
Requirements
- Node.js **18 or higher**
- Claude Desktop or Claude Code
- A Bitrix24 incoming webhook URL
---
Installation
1. Clone the repository
2. Install dependencies
3. Create your Bitrix24 webhook
> **Administrator required.** Only a Bitrix24 portal administrator can create incoming webhooks. This is a platform security restriction — webhooks act as system-level credentials and can carry broader permissions than a regular user session.
Step-by-step
1. Log in to your Bitrix24 portal as an **administrator**
2. Go to **Applications** (left sidebar) → **Webhooks**
3. Click **Incoming webhooks** → **Add webhook**
4. Give it a descriptive name (e.g. Claude MCP)
5. Under **Permissions**, enable the scopes you need (see Access Profiles below)
6. Click **Save**
7. Copy the generated URL — it looks like:
This URL is your B24_DEFAULT_WEBHOOK. **Keep it private** — it grants API access to your portal.
Where to find it later
If you need to edit the webhook or add more scopes after the initial setup:
**Applications → Webhooks → Incoming webhooks → (click your webhook name)**
4. Configure Claude Desktop
Open your Claude Desktop configuration file:
| OS | Path |
|---|---|
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
Add the following entry inside "mcpServers":
> **Windows note:** use forward slashes (/) or escaped backslashes (\\) in the path.
5. Restart Claude Desktop
After saving the config file, restart Claude Desktop. You should see the Bitrix24 tools available in the tools panel.
---
Access Profiles
Bitrix24 webhooks use **scopes** to control which modules are accessible. Each scope unlocks a set of API methods — but within a scope, all operations (read and write) are permitted. There is no built-in "read-only" flag at the scope level.
The practical way to limit what Claude can do is to combine the right set of scopes. Below are three ready-made profiles that cover the most common use cases.
---
Profile 1 — Structure Inspector (no business data)
Use this when you want Claude to understand the portal's configuration — pipelines, stages, custom fields, automations — **without access to any actual records** (no deals, no contacts, no tasks).
> Ideal for: consultants auditing a portal setup, or developers mapping the CRM before building an integration.