bitrix24-custom-mcp: Bitrix24 product catalog and CRM for Claude

bitrix24-custom-mcp

A remote FastMCP server reads the Bitrix24 product catalog and CRM through a webhook, with writes off by default

  • 0 ★ on the repository
  • Last commit
MCP server

Extended access

Why this level

  • A Bitrix24 webhook opens customer, deal and stock data, so rights are issued minimal
  • With writes on, the server creates and changes CRM items, though through a preview and an allowlist
All reasons and checks
Russian stack

ffatimaobaid/bitrix24-custom-mcp

Install

Services

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/bitrix24-custom-mcp

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • A Bitrix24 webhook opens customer, deal and stock data, so rights are issued minimal
  • With writes on, the server creates and changes CRM items, though through a preview and an allowlist

This is third-party code. Review the repository files before installing.

What it does

The Python server gives Claude 24 tools: 9 for the product catalog (sections, products, prices, stock per warehouse) and 12 for reading CRM (leads, deals, contacts, companies, smart processes, funnels, stage history). Requests go to the Bitrix24 REST API through an incoming webhook. Four more write tools appear only with `ENABLE_WRITES=true`: a timeline comment, a to-do, creating and updating an item. Writing needs a separate webhook, and creating or updating first shows a preview and runs with `confirm=true`. `*.delete` methods, bulk edits and funnel changes are blocked by an allowlist.

Who it is for. Sales managers and shop owners on Bitrix24 who want answers about stock, prices and deals right in a chat with Claude.

Good fit when

  • You need stock per warehouse and prices checked against a deal card without opening the portal
  • A manager asks for a funnel summary: number and amount of deals per stage
  • After a call a timeline comment is added to a deal, with confirmation
  • Before creating a contact you want to check duplicates by phone and email

Not a fit when

  • You need deletion, import or moving deals between stages: those methods are blocked
  • A Bitrix24 cloud plan without REST API: webhooks are unavailable there
  • A remote server is overkill and you prefer to run locally

Example request

Show coffee machine stock per warehouse and the deals that have it in line items

MCP

Transport
http
Authentication
API key

Environment variables

BITRIX_WEBHOOK_URL required, secret
Bitrix24 read webhook, the address ends with /
MCP_SECRET_PATH required, secret
Secret part of the /mcp/<secret> path
BITRIX_WRITE_WEBHOOK_URL secret
Separate write webhook, needed when ENABLE_WRITES=true

Limitations

The author did not state a license. You deploy the server yourself: the repository has a Dockerfile and `render.yaml`, and the address is protected only by the `MCP_SECRET_PATH` secret path. Bitrix24 webhooks carry portal rights, so issue them minimal. Deployment docs are short and tests cover only the catalog. Reading works without writing, and the read and write webhooks are kept separate. One author, the last commit in October 2026, no stars.

How to disable. Remove the server from Claude connectors, stop the process or container and revoke both webhooks in the Bitrix24 developer section.

FAQ

How do I enable CRM writes?

Set `ENABLE_WRITES=true` and a separate `BITRIX_WRITE_WEBHOOK_URL`. Without the second one the server stops at startup.

What happens when an item is created?

A preview with field and duplicate checks comes first. The item is created on a repeated call with `confirm=true`.

Can a deal be deleted through the server?

No. All `*.delete` methods are rejected with `PermissionError`.

How do I check that the server is running?

A request to `/health` returns the service status and a flag showing whether writes are on.

Where do webhook secrets end up in logs?

Webhook tokens are redacted in logs, and a write records the tool name, entity type, ID and changed field names without values.

Discussion

No questions or reviews yet.

Russian stack

A Python server giving agents webhook access to a Bitrix24 portal: it reads deals and contacts, and writing is a separate setting

MCP serverExtended access1Repository stars

Bitrix24 MCP by Bit2Beat

Bitrix24 MCP Server

Russian stack

Bitrix24 MCP server over an inbound webhook: CRM, tasks, disk, calendar, chat, business processes and config migration between portals

MCP serverBroad access6Repository stars
Russian stack

A read and write MCP server for the Bitrix24 REST API: CRM, tasks, scrum, calendar, disk, messaging and portal events

MCP serverBroad access1Repository stars

Bitrix24 MCP server: tasks, CRM and lists

Bitrix24 Tasks, CRM & Lists MCP Server

Russian stack

A modular Bitrix24 MCP server with 46 tools for tasks and kanban, CRM deals and contacts, and universal lists, running in Docker with no third-party cache

MCP serverBroad access1Repository stars
Russian stack

An MCP server for Bitrix24 CRM contacts and deals via an inbound webhook: search, lists and deal stage changes

MCP serverBroad access65Repository stars

README in short

Covers the architecture with a secret path, the list of 24 tools with Bitrix24 methods, write safeguards, environment variables and starting with `python server.py`.

README badge

Report a problem