Bitrix24 MCP server with write confirmation
bitrix24-mcp-server
An MCP server for Bitrix24 CRM, tasks, projects, scrum and business processes where every write needs user confirmation, installed via uvx with no cloning
- 0 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Can create, update and delete deals, tasks and CRM records, though confirmation is on by default
- Can start and stop business processes, including deleting a process along with its data
A similar tool with a larger community: Bitrix24 MCP Server, 65 ★ on the repository
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/a-shipilo-bitrix24-mcp-serverDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Can create, update and delete deals, tasks and CRM records, though confirmation is on by default
- Can start and stop business processes, including deleting a process along with its data
This is third-party code. Review the repository files before installing.
What it does
The server gives access to four Bitrix24 areas through an inbound webhook: CRM on the universal crm.item API (leads, deals, contacts, companies) with search, a full card, field discovery, pipelines and comments; tasks with attachment reading, comments and checklists; projects and scrum with kanban boards, sprints and a backlog; business processes with templates, launching, a list of pending approval tasks, and delegation. Every create, update or delete is marked in the README with a confirmation icon: the server shows exactly what will change and waits for explicit approval. In clients that support elicitation this is a dialog; in others, including Claude Desktop, the tool returns a one-time confirmation_id valid for 15 minutes that must be passed to a separate confirm_action call. For unattended scenarios there is a BITRIX24_AUTO_APPROVE variable listing tools that skip confirmation, except CRM operations.
Who it is for. For teams working across Bitrix24 CRM, tasks, projects and business processes at once who want an agent that never changes anything without a person's explicit approval.
Good fit when
- You want to manage deals, tasks, project kanban and scrum sprints from a single MCP server
- You need every Bitrix24 write to require confirmation before it runs
- You need to work with business process tasks: approvals, acknowledgements, delegation
Not a fit when
- You need to create or edit business process templates: Bitrix24 itself does not allow that through a webhook
- You do not need tasks and projects, only CRM: a narrower server would fit better
Example request
Show the current sprint board in the Mobile app scrum and move deal 1542 to wonMCP
- Transport
- stdio
- Authentication
- not required
Environment variables
BITRIX24_WEBHOOK_URLrequired, secret- The Bitrix24 portal inbound webhook URL
BITRIX24_CONFIRM_MODE- Confirmation mode: auto, elicitation or token, default auto
BITRIX24_CONFIRM_TASKS- Confirmation for task and project operations, default true
BITRIX24_AUTO_APPROVE- A comma-separated list of tools that run without confirmation, except crm_*
Limitations
The repository is very new, has a single author, and no stars. Creating or editing business process templates through an inbound webhook is not possible, only through an app, and business process methods require portal admin rights. Choosing Always allow for the confirm_action prompt in Claude Desktop disables the protection against accidental writes, which the README calls out explicitly.
How to disable. Remove the bitrix24 entry from your Claude Desktop or Claude Code mcpServers configuration.
FAQ
How does confirmation work in Claude Desktop, which lacks elicitation support?
The tool returns a confirmation_id, Claude Desktop shows the operation description, and the write only runs after a separate confirm_action call with that id within 15 minutes.
Can confirmation be disabled for CRM?
No, crm_* tools listed in BITRIX24_AUTO_APPROVE are ignored; CRM confirmation cannot be turned off.
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
A read and write MCP server for the Bitrix24 REST API: CRM, tasks, scrum, calendar, disk, messaging and portal events
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
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 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
An MCP server for Bitrix24 CRM contacts and deals via an inbound webhook: search, lists and deal stage changes
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 with write confirmation (this card) | no | not required | 0 | |
| 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 README describes four tool groups in tables with a confirmation mark on every write operation, the confirmation mechanics for clients with and without elicitation, webhook permission setup by Bitrix24 section, the BITRIX24_CONFIRM_MODE, BITRIX24_CONFIRM_TASKS and BITRIX24_AUTO_APPROVE environment variables for unattended scenarios, example Russian-language requests, and development instructions using ruff and pytest. MIT license, with CI configured in the repository.