SkillFoxx

Type a name, a task or a service

bitrix24-mcp by RCS: a commercial server with audit logging

bitrix24-mcp

A commercial Bitrix24 MCP server with 55 tools for CRM, tasks, calls and open lines, with audit logging and a free tier of 100 calls a day

MCP server

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

  • Can modify and delete CRM records: destructive operations require client confirmation, but access is granted by a license key, not just webhook scopes
  • Reads call recordings and open-line conversations with clients, which are sensitive communications
All reasons and checks
Russian stack

rcs-kz/bitrix24-mcpAuthor:RCS

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/rcs-kz-bitrix24-mcp

Detects 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-mcp -- npx -y @rcs-kz/bitrix24-mcp@1.0.1

Or add to the file .mcp.json, in the project

{
  "mcpServers": {
    "bitrix24-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@rcs-kz/bitrix24-mcp@1.0.1"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

BITRIX24_WEBHOOK_URLsecret, optional
Inbound webhook URL of your Bitrix24 portal (https://<portal>.bitrix24.kz/rest/<user_id>/<token>/). Stored in the OS keychain on first run; this env var is a fallback for CI / containerised / headless deployments.
RCS_LICENSE_KEYsecret, optional
Commercial license key issued after the 14-day trial. Stored in the OS keychain on first run; env var fallback only needed for CI / headless deployments.

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-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@rcs-kz/bitrix24-mcp@1.0.1"
      ]
    }
  }
}

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

BITRIX24_WEBHOOK_URLsecret, optional
Inbound webhook URL of your Bitrix24 portal (https://<portal>.bitrix24.kz/rest/<user_id>/<token>/). Stored in the OS keychain on first run; this env var is a fallback for CI / containerised / headless deployments.
RCS_LICENSE_KEYsecret, optional
Commercial license key issued after the 14-day trial. Stored in the OS keychain on first run; env var fallback only needed for CI / headless deployments.

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-mcp","type":"stdio","command":"npx","args":["-y","@rcs-kz/bitrix24-mcp@1.0.1"]}'

Or add to the file .vscode/mcp.json, in the project

{
  "servers": {
    "bitrix24-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@rcs-kz/bitrix24-mcp@1.0.1"
      ]
    }
  }
}

If the file already exists, add the server inside the servers key.

Keys and settings

BITRIX24_WEBHOOK_URLsecret, optional
Inbound webhook URL of your Bitrix24 portal (https://<portal>.bitrix24.kz/rest/<user_id>/<token>/). Stored in the OS keychain on first run; this env var is a fallback for CI / containerised / headless deployments.
RCS_LICENSE_KEYsecret, optional
Commercial license key issued after the 14-day trial. Stored in the OS keychain on first run; env var fallback only needed for CI / headless deployments.

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-mcp -- npx -y @rcs-kz/bitrix24-mcp@1.0.1

Or add to the file ~/.codex/config.toml, for all projects

[mcp_servers.bitrix24-mcp]
command = "npx"
args = ["-y", "@rcs-kz/bitrix24-mcp@1.0.1"]

If the file already exists, append the block to the end.

Keys and settings

BITRIX24_WEBHOOK_URLsecret, optional
Inbound webhook URL of your Bitrix24 portal (https://<portal>.bitrix24.kz/rest/<user_id>/<token>/). Stored in the OS keychain on first run; this env var is a fallback for CI / containerised / headless deployments.
RCS_LICENSE_KEYsecret, optional
Commercial license key issued after the 14-day trial. Stored in the OS keychain on first run; env var fallback only needed for CI / headless deployments.

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-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@rcs-kz/bitrix24-mcp@1.0.1"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

BITRIX24_WEBHOOK_URLsecret, optional
Inbound webhook URL of your Bitrix24 portal (https://<portal>.bitrix24.kz/rest/<user_id>/<token>/). Stored in the OS keychain on first run; this env var is a fallback for CI / containerised / headless deployments.
RCS_LICENSE_KEYsecret, optional
Commercial license key issued after the 14-day trial. Stored in the OS keychain on first run; env var fallback only needed for CI / headless deployments.

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-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@rcs-kz/bitrix24-mcp@1.0.1"
      ]
    }
  }
}

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

BITRIX24_WEBHOOK_URLsecret, optional
Inbound webhook URL of your Bitrix24 portal (https://<portal>.bitrix24.kz/rest/<user_id>/<token>/). Stored in the OS keychain on first run; this env var is a fallback for CI / containerised / headless deployments.
RCS_LICENSE_KEYsecret, optional
Commercial license key issued after the 14-day trial. Stored in the OS keychain on first run; env var fallback only needed for CI / headless deployments.

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-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@rcs-kz/bitrix24-mcp@1.0.1"
      ]
    }
  }
}

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

BITRIX24_WEBHOOK_URLsecret, optional
Inbound webhook URL of your Bitrix24 portal (https://<portal>.bitrix24.kz/rest/<user_id>/<token>/). Stored in the OS keychain on first run; this env var is a fallback for CI / containerised / headless deployments.
RCS_LICENSE_KEYsecret, optional
Commercial license key issued after the 14-day trial. Stored in the OS keychain on first run; env var fallback only needed for CI / headless deployments.

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-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@rcs-kz/bitrix24-mcp@1.0.1"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

BITRIX24_WEBHOOK_URLsecret, optional
Inbound webhook URL of your Bitrix24 portal (https://<portal>.bitrix24.kz/rest/<user_id>/<token>/). Stored in the OS keychain on first run; this env var is a fallback for CI / containerised / headless deployments.
RCS_LICENSE_KEYsecret, optional
Commercial license key issued after the 14-day trial. Stored in the OS keychain on first run; env var fallback only needed for CI / headless deployments.

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-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@rcs-kz/bitrix24-mcp@1.0.1"
      ]
    }
  }
}

If the file already exists, add the server inside the mcp key.

Keys and settings

BITRIX24_WEBHOOK_URLsecret, optional
Inbound webhook URL of your Bitrix24 portal (https://<portal>.bitrix24.kz/rest/<user_id>/<token>/). Stored in the OS keychain on first run; this env var is a fallback for CI / containerised / headless deployments.
RCS_LICENSE_KEYsecret, optional
Commercial license key issued after the 14-day trial. Stored in the OS keychain on first run; env var fallback only needed for CI / headless deployments.

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-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@rcs-kz/bitrix24-mcp@1.0.1"
      ]
    }
  }
}

If the file already exists, add the server inside the context_servers key.

Keys and settings

BITRIX24_WEBHOOK_URLsecret, optional
Inbound webhook URL of your Bitrix24 portal (https://<portal>.bitrix24.kz/rest/<user_id>/<token>/). Stored in the OS keychain on first run; this env var is a fallback for CI / containerised / headless deployments.
RCS_LICENSE_KEYsecret, optional
Commercial license key issued after the 14-day trial. Stored in the OS keychain on first run; env var fallback only needed for CI / headless deployments.

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-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@rcs-kz/bitrix24-mcp@1.0.1"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

BITRIX24_WEBHOOK_URLsecret, optional
Inbound webhook URL of your Bitrix24 portal (https://<portal>.bitrix24.kz/rest/<user_id>/<token>/). Stored in the OS keychain on first run; this env var is a fallback for CI / containerised / headless deployments.
RCS_LICENSE_KEYsecret, optional
Commercial license key issued after the 14-day trial. Stored in the OS keychain on first run; env var fallback only needed for CI / headless deployments.

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

You will need: Node.js

Checked against the repository on Sep 25, 2026, commit f78a362.

Text for your agent

Download the .mcpb bundle from rcs.kz/bitrix24-mcp and install it in Claude Desktop with one click, then enter the portal's inbound webhook URL and a license key in the install form; use the freemium endpoint from the docs for a free Solo activation.

Other ways from the author
npm install @rcs-kz/bitrix24-mcp

A manual npm install for advanced users; it currently ships an older build without telephony and open-line tools.

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

What it does

The server gives Claude Desktop 55 typed tools for Bitrix24 Cloud CRM, tasks, users, instant messaging and calendar, authorizing through an inbound webhook or a Bitrix24.Market OAuth app. Beyond standard CRM entities, it separately covers sales-floor oversight: calls with duration and a recording link, WhatsApp, Telegram and site-widget open-line conversations with time-to-first-response, and rep notes on a deal's timeline, which requires the imopenlines and telephony scopes. Tokens and the webhook URL are stored in the OS keychain rather than a config file, destructive tools are flagged destructive in the manifest and prompt for client confirmation, and every call writes a line to a local audit log. The server's source code is closed and ships as a signed bundle; the repository is a public storefront with documentation, install guides, a threat model and a vulnerability disclosure policy.

Who it is for. For Bitrix24 Cloud companies that need not just CRM access from Claude but oversight of rep calls and conversations, and are willing to pay for support and updates that track Bitrix24 REST API changes.

Good fit when

  • You need not just CRM access but reporting on calls, open lines and rep notes
  • Audit logging, rate limits and OS-keychain token storage matter more than a config file
  • You are fine with closed source in exchange for support and an SLA

Not a fit when

  • You need open source for auditing or customizing yourself
  • Your portal is on-premise rather than Bitrix24 Cloud: the server only supports cloud
  • You need more than 100 free calls a day or more than one portal without paying

Example request

Summarize deals over 50 million KZT that slipped their close date this quarter and create a follow-up task for each

Limitations

The source code is proprietary and ships as a signed V8-bytecode bundle; the repository holds only documentation. The free Solo tier gives 100 calls a day on one portal for personal use; commercial use and more portals require the paid Pro tier. Only Bitrix24 Cloud is supported, on-premise is on the roadmap with no date. The license key is checked remotely at license.rcs.kz once a day, with a 14-day grace period if that service is unreachable. The npm package currently ships an older build without telephony and open-line tools; the current version needs to be installed as the .mcpb bundle.

How to disable. Remove the bitrix24-mcp server from Claude Desktop and, if you subscribed to Pro, cancel it in Lemon Squeezy.

MCP

Transport
stdio
Authentication
API key

Security check

  • Can modify and delete CRM records: destructive operations require client confirmation, but access is granted by a license key, not just webhook scopes
  • Reads call recordings and open-line conversations with clients, which are sensitive communications

README in short

The Russian and English README describes the 55 tools in detail, a security model with OS-keychain token storage, no telemetry, declared network access limited to the portal domain and license.rcs.kz, install via the .mcpb bundle, the Solo and Pro tiers paid through Lemon Squeezy, a support SLA, and a link to a threat model with an attack report. The repository's CC BY-ND 4.0 license covers the documentation; the software itself is governed by a separate commercial agreement.

FAQ

Can the server be used for free?

Yes, the Solo tier gives 100 calls a day on one portal for personal use, forever, with no payment.

Why is the source code closed?

This is the vendor's stated position: the product is commercial, and revenue funds support and updates that track Bitrix24 REST API changes; bundle integrity is verified with a SHA-256 signature.

Official

Salesforce's official DX MCP server: work with orgs, metadata, data, users and Apex tests from your agent

MCP serverHigh risk483
Official

Yandex's official skill set: catalog, prices, stock, orders, storefront and a weekly checkup for a Yandex Kit store, through Claude Code or Codex

PluginHigh riskRussian stackNo VPN needed28
Editors’ pick

Full 65-operation YouGile API coverage with configurable permissions, write confirmation and a shared company rate limit

MCP serverHigh riskRussian stackNo VPN needed

Bitrix24 portal MCP server

MCP-сервер портала Битрикс24

Official

Bitrix24's official per-portal MCP: an external agent uses OAuth or a token to read and change tasks, deals, meetings and mail

MCP serverHigh riskRussian stackNo VPN needed
Foxx AIbitrix24-mcp by RCS: a commercial server with audit logging

I am Foxx AI and I have already vetted this tool. Ask about install, setup or anything else, and I will keep it simple.