SkillFoxx

Type a name, a task or a service

mcp-bitrix24

An MCP server for Bitrix24 tasks, workgroups and users via an inbound webhook, built with clean TypeScript architecture

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

  • Creates, closes and reopens tasks in a live Bitrix24 portal
  • The webhook carries whatever rights were set when it was created; issue a separate webhook scoped to just the needed methods
All reasons and checks
Russian stack

stemirkhan/mcp-bitrix24Author:stemirkhan

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/mcp-bitrix24

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 --env 'BITRIX24_WEBHOOK_URL=<your BITRIX24_WEBHOOK_URL>' bitrix24 -- npx -y mcp-bitrix24

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

{
  "mcpServers": {
    "bitrix24": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-bitrix24"
      ],
      "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",
        "mcp-bitrix24"
      ],
      "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","mcp-bitrix24"],"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",
        "mcp-bitrix24"
      ],
      "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 mcp-bitrix24

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

[mcp_servers.bitrix24]
command = "npx"
args = ["-y", "mcp-bitrix24"]
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",
        "mcp-bitrix24"
      ],
      "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",
        "mcp-bitrix24"
      ],
      "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",
        "mcp-bitrix24"
      ],
      "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",
        "mcp-bitrix24"
      ],
      "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",
        "mcp-bitrix24"
      ],
      "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",
        "mcp-bitrix24"
      ],
      "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",
        "mcp-bitrix24"
      ],
      "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.

You will need: Node.js

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

Text for your agent

Run npx -y mcp-bitrix24 with the BITRIX24_WEBHOOK_URL environment variable pointing at your Bitrix24 portal's inbound webhook, and add a bitrix24 server to your agent's mcp_servers config.

Other ways from the author
npx mcp-bitrix24

Requires the BITRIX24_WEBHOOK_URL environment variable with your portal's inbound webhook address.

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

What it does

The server connects to a Bitrix24 portal via an inbound webhook and lets the agent handle tasks: create, update, close, reopen and list them, plus read a task's change history. It also supports workgroups (create and list) and users (list, current user and available fields). For creating tasks with custom fields, a get_task_fields tool validates the fields object's keys against Bitrix24's real fields. The server runs stdio-only, validates tool inputs with zod, and its code is split into mcp, adapters, domain and infrastructure layers.

Who it is for. For Bitrix24 teams who want a narrow, predictable tool set for tasks and workgroups without extra CRM entities.

Good fit when

  • You need to create and close Bitrix24 tasks from a chat with an agent
  • You need the change history of a specific task
  • You only need the tasks and groups module, not deals, leads or contacts

Not a fit when

  • You need to work with deals, leads, contacts or other CRM entities: the server does not cover them
  • You need HTTP transport instead of stdio
  • You have no Bitrix24 inbound webhook with rights for tasks and groups

Example request

Create a Prepare report task for the Marketing workgroup and list that group's open tasks

Limitations

It covers only tasks, workgroups and users; CRM entities are not supported. It runs stdio-only, with no HTTP transport. Task listing pulls 50 records per page from Bitrix24, and limit is applied afterward as a local slice.

How to disable. Remove the mcp_servers.bitrix24 block from your client config and revoke the webhook in Bitrix24 settings.

MCP

Transport
stdio
Authentication
API key
Environment variables
BITRIX24_WEBHOOK_URL
required, secret		Bitrix24 inbound webhook URL with rights for tasks, groups and users

Security check

  • Creates, closes and reopens tasks in a live Bitrix24 portal
  • The webhook carries whatever rights were set when it was created; issue a separate webhook scoped to just the needed methods

README in short

The English README describes the server as an MCP/JSON-RPC over STDIO implementation for Bitrix24 tasks, workgroups and users. It gives a table of all tools with input and output parameters, a Codex config example with the BITRIX24_WEBHOOK_URL variable, and an architecture description across mcp, adapters, domain and infrastructure layers. It notes that validation uses zod and transport is STDIO only.

FAQ

Can I work with deals through this server?

No, the README scopes it to tasks, workgroups and users.

How do I check that a field in fields exists?

Call get_task_fields; create_task validates the fields keys you pass against that list.

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 AImcp-bitrix24

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