SkillFoxx

Type a name, a task or a service

Bitrix24 MCP bridge for Claude via a webhook

Bitrix24 MCP Bridge

A homemade bridge between a Claude custom connector and Bitrix24 CRM/tasks, built because Bitrix24's native marketplace OAuth connector was broken

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

  • It can create and update CRM records and tasks under the webhook owner's rights
  • The access secret is embedded in the URL: anyone with the link has CRM access
All reasons and checks
Russian stack

karpovpartnerscom/bitrix24-mcp-bridge-claudeAuthor:KarpovPartnersCom

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/bitrix24-mcp-bridge

Detects the agents on your machine, checks the risk and pins the version.

Other ways to install

Assembled automatically, review before installing.

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 http 'Bitrix24 MCP Bridge' 'https://mcp-bitrix.karpovpartners-it.ru/mcp/<your MCP_PATH_SECRET>'

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

{
  "mcpServers": {
    "Bitrix24 MCP Bridge": {
      "type": "http",
      "url": "https://mcp-bitrix.karpovpartners-it.ru/mcp/<your MCP_PATH_SECRET>"
    }
  }
}

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

Keys and settings

MCP_PATH_SECRETsecret, required
секрет в пути URL для доступа к MCP-коннектору
BITRIX_WEBHOOK_URLsecret, required
URL входящего вебхука Bitrix24 с правами CRM+Задачи

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 Bridge": {
      "url": "https://mcp-bitrix.karpovpartners-it.ru/mcp/<your MCP_PATH_SECRET>"
    }
  }
}

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

MCP_PATH_SECRETsecret, required
секрет в пути URL для доступа к MCP-коннектору
BITRIX_WEBHOOK_URLsecret, required
URL входящего вебхука Bitrix24 с правами CRM+Задачи

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 Bridge","type":"http","url":"https://mcp-bitrix.karpovpartners-it.ru/mcp/<your MCP_PATH_SECRET>"}'

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

{
  "servers": {
    "Bitrix24 MCP Bridge": {
      "type": "http",
      "url": "https://mcp-bitrix.karpovpartners-it.ru/mcp/<your MCP_PATH_SECRET>"
    }
  }
}

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

Keys and settings

MCP_PATH_SECRETsecret, required
секрет в пути URL для доступа к MCP-коннектору
BITRIX_WEBHOOK_URLsecret, required
URL входящего вебхука Bitrix24 с правами CRM+Задачи

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 Bridge' --url 'https://mcp-bitrix.karpovpartners-it.ru/mcp/<your MCP_PATH_SECRET>'

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

[mcp_servers."Bitrix24 MCP Bridge"]
url = "https://mcp-bitrix.karpovpartners-it.ru/mcp/<your MCP_PATH_SECRET>"

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

Keys and settings

MCP_PATH_SECRETsecret, required
секрет в пути URL для доступа к MCP-коннектору
BITRIX_WEBHOOK_URLsecret, required
URL входящего вебхука Bitrix24 с правами CRM+Задачи

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

gemini mcp add -s user -t http 'Bitrix24 MCP Bridge' 'https://mcp-bitrix.karpovpartners-it.ru/mcp/<your MCP_PATH_SECRET>'

Or add to the file ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "Bitrix24 MCP Bridge": {
      "httpUrl": "https://mcp-bitrix.karpovpartners-it.ru/mcp/<your MCP_PATH_SECRET>"
    }
  }
}

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

Keys and settings

MCP_PATH_SECRETsecret, required
секрет в пути URL для доступа к MCP-коннектору
BITRIX_WEBHOOK_URLsecret, required
URL входящего вебхука Bitrix24 с правами CRM+Задачи

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 Bridge": {
      "serverUrl": "https://mcp-bitrix.karpovpartners-it.ru/mcp/<your MCP_PATH_SECRET>"
    }
  }
}

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

MCP_PATH_SECRETsecret, required
секрет в пути URL для доступа к MCP-коннектору
BITRIX_WEBHOOK_URLsecret, required
URL входящего вебхука Bitrix24 с правами CRM+Задачи

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 Bridge": {
      "type": "streamableHttp",
      "url": "https://mcp-bitrix.karpovpartners-it.ru/mcp/<your MCP_PATH_SECRET>"
    }
  }
}

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

MCP_PATH_SECRETsecret, required
секрет в пути URL для доступа к MCP-коннектору
BITRIX_WEBHOOK_URLsecret, required
URL входящего вебхука Bitrix24 с правами CRM+Задачи

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 Bridge": {
      "type": "streamable-http",
      "url": "https://mcp-bitrix.karpovpartners-it.ru/mcp/<your MCP_PATH_SECRET>"
    }
  }
}

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

Keys and settings

MCP_PATH_SECRETsecret, required
секрет в пути URL для доступа к MCP-коннектору
BITRIX_WEBHOOK_URLsecret, required
URL входящего вебхука Bitrix24 с правами CRM+Задачи

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 Bridge": {
      "type": "remote",
      "url": "https://mcp-bitrix.karpovpartners-it.ru/mcp/<your MCP_PATH_SECRET>"
    }
  }
}

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

Keys and settings

MCP_PATH_SECRETsecret, required
секрет в пути URL для доступа к MCP-коннектору
BITRIX_WEBHOOK_URLsecret, required
URL входящего вебхука Bitrix24 с правами CRM+Задачи

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 Bridge": {
      "url": "https://mcp-bitrix.karpovpartners-it.ru/mcp/<your MCP_PATH_SECRET>"
    }
  }
}

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

Keys and settings

MCP_PATH_SECRETsecret, required
секрет в пути URL для доступа к MCP-коннектору
BITRIX_WEBHOOK_URLsecret, required
URL входящего вебхука Bitrix24 с правами CRM+Задачи

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

Checked against the repository on Sep 26, 2026, commit 825224d.

Text for your agent

Create a Bitrix24 inbound webhook scoped to CRM and tasks, deploy server.mjs and app.js on your hosting with the @modelcontextprotocol/sdk, express, zod and undici dependencies, set the secret and webhook URL in .htaccess, then add a Claude custom connector pointing at /mcp/<secret>.

Other ways from the author
npm install

Installs express, zod, @modelcontextprotocol/sdk and undici in the site directory on the hosting.

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

What it does

A small Express server translates MCP requests from Claude into plain Bitrix24 REST API calls through an inbound webhook scoped to CRM and tasks only. It exposes six tools: a universal bitrix24_call restricted to crm., task., tasks., user.current and profile prefixes, plus separate list, read, create and update tools for CRM records and tasks. The server itself enforces the prefix whitelist as a safeguard if the webhook's rights are ever widened. The author built this after finding Bitrix24's own marketplace connector broken: its OAuth endpoints return a bare 404 even with an active subscription.

Who it is for. For people whose official Bitrix24 marketplace connector for Claude does not work and who need a working webhook-based workaround.

Good fit when

  • Bitrix24's official Claude connector returns 404 on its OAuth endpoints even with an active subscription
  • You need a simple bridge to CRM and tasks without parsing the full REST API by hand
  • You have your own hosting (e.g. Beget) where a small Node server can run

Not a fit when

  • Bitrix24's official native connector already works for you: it gives more control through OAuth
  • You have no hosting of your own to deploy the bridge on

Example request

Show my open CRM deals and update deal 42's status to in progress

Limitations

This is the author's personal project, deployed and verified on one specific Beget hosting with old Node.js 16.20.2, which is why polyfills for modern dependencies were added to the code. The auth secret is embedded directly in the URL path rather than a header, because Claude's custom connector UI has no field for arbitrary headers. The real .htaccess with secrets is not published, only an example.

How to disable. Disable the connector in Claude's settings and stop or remove the server deployment, deactivating the webhook in Bitrix24.

MCP

Transport
http
Authentication
API key
Environment variables
BITRIX_WEBHOOK_URL
required, secret		Bitrix24 inbound webhook scoped to CRM and tasks
MCP_PATH_SECRET
required, secret		A secret embedded in the URL path, standing in for the auth header Claude's custom connectors lack

Security check

  • It can create and update CRM records and tasks under the webhook owner's rights
  • The access secret is embedded in the URL: anyone with the link has CRM access

README in short

The README walks through the bridge architecture, the URL-secret auth scheme, a step-by-step Beget deployment with a debug log (old Node.js, domain attachment, ESM vs CommonJS in Passenger), connecting it in Claude, and an open question about fixing Bitrix24's native connector.

FAQ

Why not use Bitrix24's native connector?

It did not work for the author: the /authorize and OAuth-discovery endpoints return 404, a bug on Bitrix24's side, not a configuration mistake.

Does it need modern Node.js?

No, the README shows how to run it even on Node 16.20.2 with polyfills for fetch, crypto and streams.

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 bridge for Claude via a webhook

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