Bitrix24 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
- 3 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Executes real CRM, task, document and business process calls, not just documentation reads
- Destructive actions need no confirmation unless BX24_CONFIRM_DESTRUCTIVE is enabled
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/mcp-server-for-bitrix24Detects 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.
- Executes real CRM, task, document and business process calls, not just documentation reads
- Destructive actions need no confirmation unless BX24_CONFIRM_DESTRUCTIVE is enabled
This is third-party code. Review the repository files before installing.
What it does
The server wraps Bitrix24's REST API versions 1.0 and 3.0 into 43 tools with about 870 actions: CRM, tasks, chats, disk, calendar, HR, smart processes, mail, telephony, business processes, events, open lines, chat bots, a document generator, invoices, currency, web forms, tracking and inventory. The README explicitly contrasts itself with the official Bitrix24 MCP, which only serves documentation: this server executes real calls on the portal. It supports login via an incoming webhook or an OAuth app with automatic token refresh, list auto-pagination with a row cap, request rate limiting matched to the portal's plan, and destructive operations can be gated behind a required confirm flag.
Who it is for. For Bitrix24 teams that need an agent to actually change CRM and task data, not just read API documentation.
Good fit when
- You need real Bitrix24 REST API calls, not a method reference
- You need protection from accidental destructive operations via the BX24_CONFIRM_DESTRUCTIVE flag
- You need auto-pagination for large lists and rate limiting matched to the portal's plan
Not a fit when
- You only need an API method reference with no calls executed: the official Bitrix24 MCP covers that
- You have no incoming webhook or OAuth app and are not ready to set one up
Example request
Create a Bitrix24 task to check an invoice and assign it to the deal's responsible personMCP
- Transport
- stdio
- Authentication
- key is optional
Environment variables
BX24_WEBHOOK_URLsecret- The portal's incoming webhook URL, an alternative to OAuth.
BX24_CLIENT_IDsecret- The OAuth app's client ID, needed together with DOMAIN, SECRET and REFRESH_TOKEN.
BX24_CONFIRM_DESTRUCTIVE- When true, requires an explicit confirm flag before destructive actions.
Limitations
It needs an active Bitrix24 portal, cloud or on-premise, and one of two login methods: an incoming webhook or a full OAuth app with a domain, client_id, client_secret and refresh_token. The default rate limit is 2 requests per second on regular plans and up to 5 on Enterprise, a limit set by Bitrix24 itself rather than the server. Without explicitly enabling BX24_CONFIRM_DESTRUCTIVE, destructive actions run with no required extra confirmation.
How to disable. Remove the server from your MCP client config and revoke the incoming webhook or OAuth app in your Bitrix24 portal settings.
FAQ
How is this different from the official Bitrix24 MCP?
The official server only serves API method documentation, while this one executes real calls on the portal.
Can destructive operations be made safer?
Yes, the BX24_CONFIRM_DESTRUCTIVE=true variable requires an explicit confirm flag before such actions.
How is the kostikpenzin Bitrix24 MCP server different from the official Bitrix24 MCP?
The server makes real Bitrix24 REST API 1.0 and 3.0 calls through 43 tools and about 870 actions: CRM, tasks, chats, disk, calendar, HR, smart processes, mail, telephony and business processes. It does not only serve documentation.
Can I make destructive operations safer in this Bitrix24 MCP?
Give the Bitrix24 webhook minimal rights and no delete rights. Run npx -y mcp-b24, the config is in the install block. It works in Claude Desktop and Cursor. Risk is high because calls go to a live portal.
Discussion
No questions or reviews yet.
Related
All Bitrix24 toolsA 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
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 (qwito)
Bitrix24 MCP Server
A TypeScript MCP server with 45-plus tools for Bitrix24 CRM: contacts, deals, leads, companies, tasks and activity analytics
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 real calls (this card) | no | key is optional | 3 | |
| Bitrix24 MCP Server | no | API key | 65 | webhook |
| Bitrix24 MCP Server (gunnit) | no | API key | 35 | in TypeScript for CRM |
| Bitrix24 REST API documentation MCP | yes | not required | 7 | REST API docs |
README in short
The English README, with a Russian version in i18n, describes the server as a wrapper over Bitrix24's REST API versions 1.0 and 3.0, gives an API compatibility table, an npm or npx install, a full environment variable table for webhook and OAuth, plan-based rate limits, auto-pagination and destructive action confirmation, a link to the mcp-b24 npm package, and sections on tools, usage scenarios and development.