Bitrix24 MCP server: tasks, CRM and lists
Bitrix24 Tasks, CRM & Lists MCP Server
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
- 1 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The CRM module can create, update and comment on deals and contacts once confirm=true is passed
- MCP_EXTRA_MODULES runs arbitrary third-party code with the server process's permissions
Install
- Works in
- Services
Manual install
docker compose build && docker compose run --rm -T mcpThe recommended stdio run mode; set BITRIX_WEBHOOK_BASE in .env first.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The CRM module can create, update and comment on deals and contacts once confirm=true is passed
- MCP_EXTRA_MODULES runs arbitrary third-party code with the server process's permissions
This is third-party code. Review the repository files before installing.
What it does
The server is built as a core plus three pluggable modules: tasks and projects (26 tools covering connection checks, listing, history, checklists, workgroup kanban boards, sprints and time tracking), CRM (18 tools for deals, contacts, users and activities) and universal lists (2 tools for searching and downloading attachments in a correspondence registry). Modules can be disabled via the MCP_ENABLED_MODULES variable or extended with your own, including third-party npm packages outside the repository. Every write call requires an explicit confirm=true parameter, and there is no unrestricted generic REST tool: each tool validates and limits its own set of fields. By default the server runs over stdio in Docker with one shared webhook and no database; an optional second HTTP transport adds multi-account OAuth login backed by a small PostgreSQL accounts table.
Who it is for. For teams that need broad but controlled coverage of Bitrix24 tasks, CRM and lists in one server, with the option to disable modules they do not need.
Good fit when
- You need both tasks with kanban and sprints, and CRM, from a single server rather than separate ones per entity
- You want every write to explicitly require confirm=true
- You need multi-account remote access through OAuth for several claude.ai users
Not a fit when
- You need an unrestricted generic REST tool: the project deliberately does not provide one
- You have no Docker: a basic npm run is possible, but the README is container-oriented
Example request
Show the open deals in my pipeline and move task 318 to the Done column on the project kanbanMCP
- Transport
- stdio, http
- Authentication
- OAuth
Environment variables
BITRIX_WEBHOOK_BASErequired, secret- The secret inbound webhook URL, e.g. https://portal.example.ru/rest/123/token
MCP_ENABLED_MODULES- A comma-separated list of built-in modules: tasks, crm, lists; all are enabled by default
MCP_EXTRA_MODULES- Third-party npm packages or file paths for custom modules; they run arbitrary code
MCP_TRANSPORT- stdio by default, or http for the mcp-http service
DATABASE_URLsecret- PostgreSQL connection string, needed only for the multi-account HTTP transport
Limitations
The multi-account HTTP transport keeps OAuth clients and tokens in process memory and does not survive a container restart, although the accounts themselves persist in PostgreSQL. An account's role is a descriptive field that does not gate anything by itself. Docker Engine with Compose v2 is needed for the recommended run mode. Integration tests against a real portal are gated by a separate variable and disabled by default. The project is very new with a single author and no stars.
How to disable. Stop docker compose and remove the server from .mcp.json or your MCP client configuration.
FAQ
Does the basic setup need a database?
No, PostgreSQL is only needed for the multi-account HTTP transport; a normal stdio run with one webhook works without any database.
Can I disable part of the tools?
Yes, the MCP_ENABLED_MODULES variable lets you keep only the modules you need, for example just tasks, or disable all built-in ones and load your own via MCP_EXTRA_MODULES.
Discussion
No questions or reviews yet.
Related
All Bitrix24 toolsBitrix24 MCP server with real calls
MCP Server for Bitrix24
A Bitrix24 MCP server with 43 tools and about 870 actions that executes real REST API calls instead of just serving documentation
Bitrix24 MCP Server (qwito)
Bitrix24 MCP Server
A TypeScript MCP server with 45-plus tools for Bitrix24 CRM: contacts, deals, leads, companies, tasks and activity analytics
A compact Bitrix24 MCP server on an inbound webhook: tasks, groups, kanban stages and task comments
Bitrix24 MCP by Bit2Beat
Bitrix24 MCP Server
Bitrix24 MCP server over an inbound webhook: CRM, tasks, disk, calendar, chat, business processes and config migration between portals
Bitrix24 MCP Server (gunnit)
Bitrix24 MCP Server
A TypeScript MCP server for Bitrix24 CRM: contacts, companies, leads, deals, tasks and sales rep performance reports
Bitrix24 MCP server with sales analytics
Bitrix24 MCP Server
Bitrix24 MCP server in TypeScript with a broad set of CRM tools plus a dedicated group for monitoring manager activity and performance
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Bitrix24 MCP server: tasks, CRM and lists (this card) | no | OAuth | 1 | |
| Bitrix24 MCP server with sales analytics | no | not required | 0 | in TypeScript, with manager analytics |
| Bitrix24 MCP server for Open WebUI | no | not required | 0 | 32 tools over HTTP, for Open WebUI |
| Bitrix24 MCP server in Go | no | not required | 0 | single binary |
README in short
The Russian README describes in detail the core-plus-pluggable-modules architecture, a design with no third-party data cache, running in Docker over stdio, an optional HTTP transport with multi-account OAuth backed by PostgreSQL, a full list of environment variables, a breakdown of 46 tools across three modules, and a tests and quality section covering typecheck, lint and integration checks against a real portal.