mcp-bitrix24 (CRest for OpenClaw)

Install

Works in

• SourceCraft
• Koda
• Coddy

Services

• Bitrix24

Manual install

{"mcpServers":{"bitrix24":{"command":"php","args":["/var/www/html/mcp_server.php"],"env":{"C_REST_WEB_HOOK_URL":"https://your-domain.bitrix24.ru/rest/1/webhook_token/"}}}}

What it does

The project on PHP 8.1 or newer combines an MCP server and a webhook receiver to tie the OpenClaw AI agent to a Bitrix24 portal. It uses the official CRest library and leaves it unmodified. The `mcp_server.php` server runs in two modes: over STDIO and as HTTP POST with JSON-RPC 2.0. The outgoing webhook receiver is `chatWeebhook.php`. For the first stage, customer support, the server has fifteen strictly typed tools. CRM reading goes through `b24_get_leads`, `b24_get_deals`, `b24_get_companies`, `b24_get_contacts` and `b24_get_contracts` for the Contracts smart process. `b24_get_client_dossier` assembles a client dossier in one batch request and `b24_search_crm_by_comm` searches entities by phone or email. For tasks there is a list and a card with checklists, results and comments. For chats there are `b24_get_chat_history`, `b24_chat_action` with a reply, a typing indicator and handover to a live operator, and `b24_poll_openlines` for polling Open Lines. In the CRM the agent only reads. Writing goes to chats and tasks: `b24_create_task` creates a task, `b24_add_task_checklist` adds a checklist and `b24_get_workgroups` helps choose a workgroup. Tasks are created by a company policy of six points. The project-manager agent stub is disabled by the `B24_ENABLE_PM_AGENT_TOOLS` flag.

Who it is for. Bitrix24 PHP developers and integrators building a first-line support agent on OpenClaw who want to give it chat access and CRM reads.

Example request

Build a dossier for the client with the number +7 900 123-45-67, show their deals and open tasks and prepare a reply in the Open Line.

MCP

Transport

stdio, http

Authentication

API key

Limitations

PHP 8.1 or newer and an incoming webhook with `crm`, `task`, `tasks_extended`, `im`, `imbot`, `imopenlines`, `user`, `sonet_group` and `disk` permissions are required. The webhook URL is set in `settings.php` or the `C_REST_WEB_HOOK_URL` variable. The outgoing event receiver checks the application token `B24_OUTGOING_WEBHOOK_TOKEN`.

The project is written for a specific pairing with OpenClaw, and part of the settings and README messages are oriented to it. Deployment is described for Ubuntu with Nginx and PHP-FPM, and Open Lines polling is hung on cron. The repository has no license file.

In the CRM the first-phase tools only read. Chat replies and task creation run as the webhook's user, so its rights set the agent's action boundaries.

How to disable. Remove the server from the agent configuration, turn off the outgoing webhook in Bitrix24 and delete the incoming one. Comment out the cron job for `poll_openlines.php`.

README in short

The README covers architectural rules, the project structure, webhook permissions, `settings.php` setup, a list of fifteen tools, Nginx configuration, connecting to OpenClaw over STDIO and HTTP, Open Lines polling and the task creation policy with JSON-RPC examples.