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

  • 0 ★ on the repository
  • Last commit
MCP server

Broad access

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-claude

Install

Services

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/bitrix24-mcp-bridge

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • 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

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

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

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.

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.

Discussion

No questions or reviews yet.

Bitrix24 MCP by Bit2Beat

Bitrix24 MCP Server

Russian stack

Bitrix24 MCP server over an inbound webhook: CRM, tasks, disk, calendar, chat, business processes and config migration between portals

MCP serverBroad access6Repository stars
Russian stack

A Bitrix24 MCP bridge without a webhook or admin rights: a browser extension reuses an already-open portal session

MCP serverBroad access
Russian stack

An MCP server for Bitrix24 CRM contacts and deals via an inbound webhook: search, lists and deal stage changes

MCP serverBroad access65Repository stars
Russian stack

Bitrix24 for an agent through an incoming webhook: deals, leads, contacts, tasks and pipeline reports with a manager ranking and stalled deals

MCP serverBroad access1Repository stars
Russian stack

A Bitrix24 MCP server with 43 tools and about 870 actions that executes real REST API calls instead of just serving documentation

MCP serverBroad access3Repository stars

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.

README badge

Report a problem