Bitrix24 MCP
A Bitrix24 MCP server on an inbound webhook: deals, contacts, tasks, employees, disk and chat in 12 tools
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
- Creates and changes deals, contacts and tasks in a live portal
- Sends messages to employees on behalf of the webhook user
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/bitrix24-mcpDetects 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 --env 'BITRIX24_WEBHOOK_URL=<your BITRIX24_WEBHOOK_URL>' bitrix24 -- npx -y @theyahia/bitrix24-mcpOr add to the file .mcp.json, in the project
{
"mcpServers": {
"bitrix24": {
"command": "npx",
"args": [
"-y",
"@theyahia/bitrix24-mcp"
],
"env": {
"BITRIX24_WEBHOOK_URL": "<your BITRIX24_WEBHOOK_URL>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
BITRIX24_WEBHOOK_URLsecret, required
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",
"@theyahia/bitrix24-mcp"
],
"env": {
"BITRIX24_WEBHOOK_URL": "<your BITRIX24_WEBHOOK_URL>"
}
}
}
}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, required
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","@theyahia/bitrix24-mcp"],"env":{"BITRIX24_WEBHOOK_URL":"<your BITRIX24_WEBHOOK_URL>"}}'Or add to the file .vscode/mcp.json, in the project
{
"servers": {
"bitrix24": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@theyahia/bitrix24-mcp"
],
"env": {
"BITRIX24_WEBHOOK_URL": "<your BITRIX24_WEBHOOK_URL>"
}
}
}
}If the file already exists, add the server inside the servers key.
Keys and settings
BITRIX24_WEBHOOK_URLsecret, required
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 --env 'BITRIX24_WEBHOOK_URL=<your BITRIX24_WEBHOOK_URL>' -- npx -y @theyahia/bitrix24-mcpOr add to the file ~/.codex/config.toml, for all projects
[mcp_servers.bitrix24]
command = "npx"
args = ["-y", "@theyahia/bitrix24-mcp"]
env = { BITRIX24_WEBHOOK_URL = "<your BITRIX24_WEBHOOK_URL>" }If the file already exists, append the block to the end.
Keys and settings
BITRIX24_WEBHOOK_URLsecret, required
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",
"@theyahia/bitrix24-mcp"
],
"env": {
"BITRIX24_WEBHOOK_URL": "<your BITRIX24_WEBHOOK_URL>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
BITRIX24_WEBHOOK_URLsecret, required
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",
"@theyahia/bitrix24-mcp"
],
"env": {
"BITRIX24_WEBHOOK_URL": "<your BITRIX24_WEBHOOK_URL>"
}
}
}
}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, required
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",
"@theyahia/bitrix24-mcp"
],
"env": {
"BITRIX24_WEBHOOK_URL": "<your BITRIX24_WEBHOOK_URL>"
}
}
}
}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, required
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",
"@theyahia/bitrix24-mcp"
],
"env": {
"BITRIX24_WEBHOOK_URL": "<your BITRIX24_WEBHOOK_URL>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
BITRIX24_WEBHOOK_URLsecret, required
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",
"@theyahia/bitrix24-mcp"
],
"environment": {
"BITRIX24_WEBHOOK_URL": "<your BITRIX24_WEBHOOK_URL>"
}
}
}
}If the file already exists, add the server inside the mcp key.
Keys and settings
BITRIX24_WEBHOOK_URLsecret, required
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",
"@theyahia/bitrix24-mcp"
],
"env": {
"BITRIX24_WEBHOOK_URL": "<your BITRIX24_WEBHOOK_URL>"
}
}
}
}If the file already exists, add the server inside the context_servers key.
Keys and settings
BITRIX24_WEBHOOK_URLsecret, required
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",
"@theyahia/bitrix24-mcp"
],
"env": {
"BITRIX24_WEBHOOK_URL": "<your BITRIX24_WEBHOOK_URL>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
BITRIX24_WEBHOOK_URLsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Create a Bitrix24 inbound webhook with crm, task, user, disk, im rights, then add the server with claude mcp add bitrix24 -e BITRIX24_WEBHOOK_URL=<webhook url> -- npx -y @theyahia/bitrix24-mcp.
Other ways from the author
{
"mcpServers": {
"bitrix24": {
"command": "npx",
"args": ["-y", "@theyahia/bitrix24-mcp"],
"env": {
"BITRIX24_WEBHOOK_URL": "https://your-company.bitrix24.ru/rest/1/your-webhook-key/"
}
}
}
}The README's config for Claude Desktop.
This is third-party code. Review the repository files before installing.
What it does
The server connects to Bitrix24 through an inbound webhook and gives an agent 12 tools: listing and reading a deal, creating and updating a deal, listing and creating contacts, listing tasks with filters, creating a task, completing a task, listing employees filtered by activity and department, uploading a file to Disk, and sending a message to an employee or a group. No OAuth app or Bitrix24-side coding is needed. Part of the same author's WWmcp series of MCP servers.
Who it is for. For sales managers and developers who want quick access to Bitrix24 CRM from an agent chat without setting up OAuth.
Good fit when
- You need to quickly create a deal, contact or task from an agent conversation
- You need to see open deals or an employee's tasks without logging into Bitrix24
- You need to send a message to an employee or a group straight from the agent
Not a fit when
- You need leads, companies, pipelines or business processes: there are no tools for them
- You need multi-portal operation with OAuth and token rotation instead of a single webhook
Example request
Show all open deals in Bitrix24 and set a task for employee 5 to prepare a presentation by tomorrowLimitations
Covers only deals, contacts, tasks, employees, disk and messages, with no leads, companies or business processes. The webhook embeds its secret key right in the URL and carries whatever rights were granted when it was created. The author also ships the same code from the theyahia/wwmcp monorepo; there is no duplicate listing in the catalog.
How to disable. Remove the server from your MCP client config, for example claude mcp remove bitrix24 in Claude Code, and revoke the webhook in your portal settings.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| BITRIX24_WEBHOOK_URL required, secret | The full Bitrix24 inbound webhook URL including the auth key |
Security check
- Creates and changes deals, contacts and tasks in a live portal
- Sends messages to employees on behalf of the webhook user
README in short
The Russian README explains setup via an inbound webhook with crm, task, user, disk, im scopes, gives a Claude Desktop config and a Claude Code command, a table of all 12 tools and Russian-language demo prompts. It lists the single required environment variable BITRIX24_WEBHOOK_URL. MIT license, part of the WWmcp series.
FAQ
Do I need OAuth?
No, the server works through an inbound webhook with the right scopes, no OAuth app needed.
How many tools are available?
12: deals, contacts, tasks, employees, Disk files and messages.
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