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
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
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
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/mcp-server-for-bitrix24Detects the agents on your machine, checks the risk and pins the version.
Other ways to install
This entry is high risk, so there is no one-click install. Review the code and add the config by hand.
Run in a terminal
claude mcp add --transport stdio bitrix24 -- npx -y mcp-b24Or add to the file .mcp.json, in the project
{
"mcpServers": {
"bitrix24": {
"command": "npx",
"args": [
"-y",
"mcp-b24"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
BX24_WEBHOOK_URLsecret, optional
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.cursor/mcp.json, for all projects
{
"mcpServers": {
"bitrix24": {
"command": "npx",
"args": [
"-y",
"mcp-b24"
]
}
}
}If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.
Keys and settings
BX24_WEBHOOK_URLsecret, optional
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Run in a terminal
code --add-mcp '{"name":"bitrix24","type":"stdio","command":"npx","args":["-y","mcp-b24"]}'Or add to the file .vscode/mcp.json, in the project
{
"servers": {
"bitrix24": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-b24"
]
}
}
}If the file already exists, add the server inside the servers key.
Keys and settings
BX24_WEBHOOK_URLsecret, optional
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Run in a terminal
codex mcp add bitrix24 -- npx -y mcp-b24Or add to the file ~/.codex/config.toml, for all projects
[mcp_servers.bitrix24]
command = "npx"
args = ["-y", "mcp-b24"]If the file already exists, append the block to the end.
Keys and settings
BX24_WEBHOOK_URLsecret, optional
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.gemini/settings.json, for all projects
{
"mcpServers": {
"bitrix24": {
"command": "npx",
"args": [
"-y",
"mcp-b24"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
BX24_WEBHOOK_URLsecret, optional
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.config/devin/mcp_config.json, for all projects
{
"mcpServers": {
"bitrix24": {
"command": "npx",
"args": [
"-y",
"mcp-b24"
]
}
}
}If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.
Keys and settings
BX24_WEBHOOK_URLsecret, optional
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Formerly Windsurf.
Add to the file cline_mcp_settings.json, for all projects
{
"mcpServers": {
"bitrix24": {
"command": "npx",
"args": [
"-y",
"mcp-b24"
]
}
}
}If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.
Keys and settings
BX24_WEBHOOK_URLsecret, optional
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file .roo/mcp.json, in the project
{
"mcpServers": {
"bitrix24": {
"command": "npx",
"args": [
"-y",
"mcp-b24"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
BX24_WEBHOOK_URLsecret, optional
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
A fork of Roo Code, same .roo folders.
Add to the file opencode.json, in the project
{
"mcp": {
"bitrix24": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-b24"
]
}
}
}If the file already exists, add the server inside the mcp key.
Keys and settings
BX24_WEBHOOK_URLsecret, optional
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.config/zed/settings.json, for all projects
{
"context_servers": {
"bitrix24": {
"command": "npx",
"args": [
"-y",
"mcp-b24"
]
}
}
}If the file already exists, add the server inside the context_servers key.
Keys and settings
BX24_WEBHOOK_URLsecret, optional
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file .codeassistant/mcp.json, in the project
{
"mcpServers": {
"bitrix24": {
"command": "npx",
"args": [
"-y",
"mcp-b24"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
BX24_WEBHOOK_URLsecret, optional
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Create an incoming webhook under Developer resources in your Bitrix24 portal, run npx -y mcp-b24 and pass a BX24_WEBHOOK_URL variable in your MCP client config, or set up an OAuth app with BX24_DOMAIN, BX24_CLIENT_ID, BX24_CLIENT_SECRET and BX24_REFRESH_TOKEN.
Other ways from the author
npx -y mcp-b24Launch with no global install, needs Node.js 18 or newer.
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 personLimitations
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.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| BX24_WEBHOOK_URL secret | The portal's incoming webhook URL, an alternative to OAuth. |
| BX24_CLIENT_ID secret | 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. |
Security check
- Executes real CRM, task, document and business process calls, not just documentation reads
- Destructive actions need no confirmation unless BX24_CONFIRM_DESTRUCTIVE is enabled
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.
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.
Related
Salesforce's official DX MCP server: work with orgs, metadata, data, users and Apex tests from your agent
Yandex Kit skills for store management
kit-skills
Yandex's official skill set: catalog, prices, stock, orders, storefront and a weekly checkup for a Yandex Kit store, through Claude Code or Codex
YouGile MCP by Indalo
YouGile MCP
Full 65-operation YouGile API coverage with configurable permissions, write confirmation and a shared company rate limit
Bitrix24 portal MCP server
MCP-сервер портала Битрикс24
Bitrix24's official per-portal MCP: an external agent uses OAuth or a token to read and change tasks, deals, meetings and mail