bitrix-mcp

Universal, full-featured, portable MCP server for the Bitrix24 REST API. Read and write. Not tied to any one application — it's a generic Bitrix24 gateway that any MCP client or agent can mount (Claude Code, Claude Desktop, Cursor, Windsurf, Cline, or your own Python/Node agent).

Language: Python + the official MCP SDK (mcp.server.mcpserver, 2.x)
Transports:stdio (default, most portable/reliable) and Streamable HTTP (stateless JSON — no fragile long-lived SSE bridge)
Coverage: universal b24_call / b24_batch reach 100% of the REST API; a catalogue built from the official docs (1930 methods) tells the agent which method it needs and what parameters it takes; 99 typed tools cover the high-traffic domains with the tricky bits handled.
Portal events: three ways to receive them — pull channel (works behind NAT and VPN), outgoing-webhook receiver, poller — plus a history archive and Telegram forwarding: docs/EVENTS.md

Why this exists / what it fixes

Rebuilt from field notes on a previous wrapper. The bugs that motivated it are fixed by design, not patched around:

Old behavior	Fix here
`filter` silently ignored (`groups_list`, `users_list`), full-portal dumps → timeouts	Params sent as JSON POST body, so nested `filter`/`select`/`order` are parsed correctly by Bitrix. Real pagination with a page cap.
Access errors swallowed into a fake "0 results" (`read_pipelines` etc.)	Errors are never swallowed — a Bitrix `error`/`error_description` always surfaces with its `code` (e.g. `ACCESS_DENIED`).
`calendar_list` returned 0 without explicit `ownerId`	`owner_id`auto-resolves to the acting user.
Scrum kanban read from the wrong place	Correct flow baked in: active-sprint filter + `tasks.api.scrum.kanban.getStages` (`b24_scrum_board` does it in one call).
Fragile `mcp-remote` SSE session drops / hangs	Prefer stdio (no bridge) or stateless Streamable HTTP.
`department.get` has no server-side filter at all (a Bitrix API limitation, undocumented) — any `filter` was silently ignored and the whole department tree (95+ rows) came back regardless	`b24_department_get` filters client-side after a full fetch, so `filter`/`ID` genuinely narrow the result instead of quietly dumping everything.
Bitrix sometimes reports a failure as `{"error": "", "error_description": "Access denied."}` — an empty-string error code — which a naive truthiness check (`if data.get("error")`) misses, losing the code and message to a generic HTTP-status fallback	Checked by key presence, not truthiness — `code`/`message` always reflect what Bitrix actually said.
`calendar.event.add` / `.update` silently drop `attendees` unless `is_meeting` is also set — 200 OK, event created, nobody invited, no error anywhere	`is_meeting` is auto-set to `'Y'` whenever `attendees` is non-empty and not already specified.
Moving a task on a Scrum sprint board has no single API call, and every obvious candidate fails while reporting success: `tasks.task.update`'s `STAGE_ID` changes the field and writes a history entry everyone can see, but the card stays put; `kanban.addTask` only places a card that is off the board and answers `true` without doing anything for one already in a column; `task.stages.movetask` answers `false`.	`b24_scrum_task_move` takes the card off the board and puts it back at the target column (`kanban.deleteTask` → `kanban.addTask`) — verified by watching a real board, not by trusting the response. It also warns that `STAGE_ID` cannot verify the result: it read `0` while the card was visibly in the target column.

Install

If nothing is installed on the machine, take the portable archive (dist/bitrix-mcp-portable.zip, built by python scripts/build_portable.py). It carries its own Python and every library — no uv, no pip, no PyPI access. Unzip it and run the bundled launcher.

From source:

uv sync # create venv + install# or, as a tool on PATH:
uv tool install .# exposes the `bitrix-mcp` command

Configure

Set the default webhook (see .env.example):

export BITRIX_WEBHOOK_URL="https://your-portal.bitrix24.ru/rest/1/xxxxxxxx/"# optional:export BITRIX_READ_ONLY=1 # block all writes

The webhook comes from Bitrix: Profile → Webhooks → inbound webhook, format https://<portal>/rest/<user_id>/<token>/. The token is a credential — keep it out of source control (.env is gitignored).

Auth precedence per call:personal_webhook → webhook_url → X-B24-Webhook HTTP header → BITRIX_WEBHOOK_URL. Pass personal_webhook to act (and write) as a specific user.

Run

bitrix-mcp # stdio (default)
bitrix-mcp --http # Streamable HTTP on 127.0.0.1:8000/mcp
bitrix-mcp --http --host 0.0.0.0 --port 5015 # shared network service

Connect a client

Claude Code (stdio, recommended):

claude mcp add -s user bitrix24 -- uv run --directory C:/Scripts/BitrixMCP bitrix-mcp

Repo-shared .mcp.json (stdio):

{
"mcpServers": {
"bitrix24": {
"command": "uv",
"args": ["run", "--directory", "C:/Scripts/BitrixMCP", "bitrix-mcp"],
"env": { "BITRIX_WEBHOOK_URL": "https://your-portal.bitrix24.ru/rest/1/xxxx/" }
}
}
}

Claude Code (HTTP):

bitrix-mcp --http --port 5015 # then, on the client:
claude mcp add -s user --transport http bitrix24 http://HOST:5015/mcp

Claude Desktop (stdio) — %APPDATA%\Claude\claude_desktop_config.json:

{
"mcpServers": {
"bitrix24": {
"command": "uv",
"args": ["run", "--directory", "C:/Scripts/BitrixMCP", "bitrix-mcp"],
"env": { "BITRIX_WEBHOOK_URL": "https://your-portal.bitrix24.ru/rest/1/xxxx/" }
}
}
}

(For a remote HTTP instance, Desktop still needs the mcp-remote bridge; stdio above avoids it entirely.)

Tool catalog (99)

Universal — b24_call, b24_batch, b24_test_connection, b24_list_methodsCRM — b24_crm_list, b24_crm_get, b24_crm_fields, b24_crm_add, b24_crm_update, b24_crm_delete, b24_crm_timeline_comment_add, b24_crm_timeline_comment_list, b24_crm_category_list (pipelines), b24_crm_status_list (stages/dictionaries), b24_crm_activity_list, b24_crm_activity_add, b24_crm_activity_delete, b24_crm_productrows_get, b24_crm_productrows_set, b24_crm_currency_list, b24_crm_requisite_list, b24_crm_deal_contacts_get, b24_crm_deal_contacts_set (classic entities and SPA via entity_type_id) Tasks — b24_tasks_list, b24_task_get, b24_task_add, b24_task_update, b24_task_complete, b24_task_delete, b24_task_comments_list, b24_task_comment_add, b24_task_stages_get, b24_task_checklist_list, b24_task_checklist_add, b24_task_elapsed_add, b24_task_result_listScrum — b24_scrum_sprint_list, b24_scrum_kanban_stages, b24_scrum_board, b24_scrum_task_moveCalendar — b24_calendar_event_list, b24_calendar_section_list, b24_calendar_event_add, b24_calendar_event_update, b24_calendar_event_deleteDisk — b24_disk_storage_list, b24_disk_folder_items, b24_disk_file_get, b24_disk_file_content (server-side download → base64), b24_disk_folder_add, b24_disk_file_upload, b24_disk_file_deleteUsers/structure — b24_user_get, b24_user_search, b24_user_current, b24_department_getGroups (workgroups) — b24_group_list, b24_group_users, b24_group_create, b24_group_update, b24_group_deleteMessaging — b24_im_recent, b24_im_dialog_messages, b24_im_message_add, b24_im_notify_personal, b24_im_user_get, b24_im_chat_create, b24_im_chat_user_add, b24_feed_post_addLists (universal lists) — b24_lists_get, b24_lists_element_list, b24_lists_element_add, b24_lists_element_update, b24_lists_element_deleteCatalog / products — b24_catalog_list, b24_catalog_section_list, b24_catalog_product_list, b24_catalog_product_get, b24_catalog_product_add, b24_catalog_product_update, b24_crm_product_listSale (orders) — b24_sale_order_list, b24_sale_order_getDocuments — b24_documentgenerator_templates, b24_documentgenerator_addBizproc — b24_bizproc_template_list, b24_bizproc_startTelephony — b24_telephony_statistics

Anything still not typed here is reachable through b24_call (e.g. mail, open-lines, sale basket writes, admin/app-placement methods).

Retrospective-app integration

This server has no knowledge of any downstream app. An agent connects to both this server and your app's MCP, reads Bitrix here, and relays into the app's contract. Field names from b24_tasks_list / b24_calendar_event_list map directly onto PushSprintTask / PushCalendarEvent, so the mapping is trivial — but that translation lives in the agent, not here.

Documentation

docs/USAGE.md — how to drive the tools: auth, filters, pagination, batch, errors, recipes.
ARCHITECTURE.md — components, call flow, deployment; diagrams in docs/diagrams/.
ROADMAP.md — status, history, and out-of-scope boundaries.

Development

uv sync # install runtime + dev deps
uv run pytest -q # offline unit tests (no portal needed)
uv run python scripts/smoke.py "<webhook>"# live read-only access map (run from a network with portal access)

Verification scripts

Each one exits non-zero when a check fails, so they can be chained in CI. Those marked offline need no portal; the rest need a reachable webhook.

Script	What it proves	Needs
`scripts/startup_check.py`	The server boots on both transports and registers every tool	offline
`scripts/leak_check.py`	The sanitizer strips webhooks/tokens from output and from httpx logs	offline
`scripts/git_secret_scan.py`	No secret is present in tracked files or anywhere in git history	offline
`scripts/events_tools_check.py`	poll → ack → history → stats against a seeded store	offline
`scripts/coverage_check.py`	Requirement R-1: catalogue + scope diagnosis reach the whole API	portal
`scripts/poller_check.py`	`b24_changes_since` cursors advance and do not skip rows	portal
`scripts/pull_channel_check.py`	Push & Pull channel subscribes and receives	portal
`scripts/receiver_e2e_check.py`	Outgoing-webhook receiver end to end, including TLS	portal
`scripts/telegram_check.py`	Filter DSL routes the right events	offline
`scripts/telegram_live_check.py`	The bot and chat really accept a message	Telegram
`scripts/smoke.py`	Live read-only access map across every domain	portal
`scripts/build_catalog.py`	Regenerates `data/catalog.json` from the official docs	docs checkout

Probes (diagnostics, no pass/fail verdict): pull_probe.py, probe_listener.py, tg_conn_probe.py.

Diagrams are regenerated with java -jar plantuml.jar -tpng docs/diagrams/*.puml.

Notes on limits

fetch_all=true is capped by BITRIX_MAX_PAGES (default 40 pages ≈ 2000 records) and reports truncated: true when it hits the cap — it never silently stops short.
The read-only guard classifies writes by method verb; typed write tools are always classified correctly. b24_call/b24_batch use the heuristic.

Licence

MIT — see LICENSE.

Security

Found a vulnerability? Please report it privately, not in a public issue — see SECURITY.md. The webhook URL this server uses is a bearer credential for the whole portal.

Support author

BTC: bc1q3frrup5neh7nhfg944etu2agd4j9u0vg3jyee6

ETH(Arbitrum): 0x43B349d8Cea83215D707EBa3bc35e9917f746b0a

TRX: THSzvy49KNeqRjXsGkurh2A5G4avV4RgN4

XRP: rLWZjS3DMupC4ZdXCX3BVYn4dEtC3iNhgy

SOL: 3xwfybxJ6Tz5t6pjBBkL5yYQCZo6wfbv932UNA4ThdP8

ADA: addr1q926ys75jp5wn2pv32a3t8r8pdhr7w02v0t9j4a8pmg0ruww5rlkctu4lnz2hfcwa5qfn3zhsd0s23r22uqwzx9gu6cq5c4e76

TON: UQC4qlAOD9Nly4K_66GJ_yCsSM3x2sB0vZ2GrBQbc--gZUui

DOGE: DTjNYmbtymzcjUiV4MsZY8MP4dM7MJ6qLC

XMR: 44qRqM6YtnxXUhkgCFqDDrKMPjWriu69FLBoop8Kwp7e1VQsBUJoVQ8JYQjfMV5C6uidTUgSSyoJ65mq8aYG2esZ1rrqfwt

bitrix-mcp

English · Русский

Universal, full-featured, portable MCP server for the Bitrix24 REST API. Read and write. Not tied to any one application — it's a generic Bitrix24 gateway that any MCP client or agent can mount (Claude Code, Claude Desktop, Cursor, Windsurf, Cline, or your own Python/Node agent).

Language: Python + the official MCP SDK (mcp.server.mcpserver, 2.x)
Transports:stdio (default, most portable/reliable) and Streamable HTTP (stateless JSON — no fragile long-lived SSE bridge)
Coverage: universal b24_call / b24_batch reach 100% of the REST API; a catalogue built from the official docs (1930 methods) tells the agent which method it needs and what parameters it takes; 99 typed tools cover the high-traffic domains with the tricky bits handled.
Portal events: three ways to receive them — pull channel (works behind NAT and VPN), outgoing-webhook receiver, poller — plus a history archive and Telegram forwarding: docs/EVENTS.md

Why this exists / what it fixes

Rebuilt from field notes on a previous wrapper. The bugs that motivated it are fixed by design, not patched around:

Old behavior	Fix here
`filter` silently ignored (`groups_list`, `users_list`), full-portal dumps → timeouts	Params sent as JSON POST body, so nested `filter`/`select`/`order` are parsed correctly by Bitrix. Real pagination with a page cap.
Access errors swallowed into a fake "0 results" (`read_pipelines` etc.)	Errors are never swallowed — a Bitrix `error`/`error_description` always surfaces with its `code` (e.g. `ACCESS_DENIED`).
`calendar_list` returned 0 without explicit `ownerId`	`owner_id`auto-resolves to the acting user.
Scrum kanban read from the wrong place	Correct flow baked in: active-sprint filter + `tasks.api.scrum.kanban.getStages` (`b24_scrum_board` does it in one call).
Fragile `mcp-remote` SSE session drops / hangs	Prefer stdio (no bridge) or stateless Streamable HTTP.
`department.get` has no server-side filter at all (a Bitrix API limitation, undocumented) — any `filter` was silently ignored and the whole department tree (95+ rows) came back regardless	`b24_department_get` filters client-side after a full fetch, so `filter`/`ID` genuinely narrow the result instead of quietly dumping everything.
Bitrix sometimes reports a failure as `{"error": "", "error_description": "Access denied."}` — an empty-string error code — which a naive truthiness check (`if data.get("error")`) misses, losing the code and message to a generic HTTP-status fallback	Checked by key presence, not truthiness — `code`/`message` always reflect what Bitrix actually said.
`calendar.event.add` / `.update` silently drop `attendees` unless `is_meeting` is also set — 200 OK, event created, nobody invited, no error anywhere	`is_meeting` is auto-set to `'Y'` whenever `attendees` is non-empty and not already specified.
Moving a task on a Scrum sprint board has no single API call, and every obvious candidate fails while reporting success: `tasks.task.update`'s `STAGE_ID` changes the field and writes a history entry everyone can see, but the card stays put; `kanban.addTask` only places a card that is off the board and answers `true` without doing anything for one already in a column; `task.stages.movetask` answers `false`.	`b24_scrum_task_move` takes the card off the board and puts it back at the target column (`kanban.deleteTask` → `kanban.addTask`) — verified by watching a real board, not by trusting the response. It also warns that `STAGE_ID` cannot verify the result: it read `0` while the card was visibly in the target column.

Install

If nothing is installed on the machine, take the portable archive (dist/bitrix-mcp-portable.zip, built by python scripts/build_portable.py). It carries its own Python and every library — no uv, no pip, no PyPI access. Unzip it and run the bundled launcher.

From source:

uv sync # create venv + install# or, as a tool on PATH:
uv tool install .# exposes the `bitrix-mcp` command

Configure

Set the default webhook (see .env.example):

export BITRIX_WEBHOOK_URL="https://your-portal.bitrix24.ru/rest/1/xxxxxxxx/"# optional:export BITRIX_READ_ONLY=1 # block all writes

The webhook comes from Bitrix: Profile → Webhooks → inbound webhook, format https://<portal>/rest/<user_id>/<token>/. The token is a credential — keep it out of source control (.env is gitignored).

Auth precedence per call:personal_webhook → webhook_url → X-B24-Webhook HTTP header → BITRIX_WEBHOOK_URL. Pass personal_webhook to act (and write) as a specific user.

Run

bitrix-mcp # stdio (default)
bitrix-mcp --http # Streamable HTTP on 127.0.0.1:8000/mcp
bitrix-mcp --http --host 0.0.0.0 --port 5015 # shared network service

Connect a client

Claude Code (stdio, recommended):

claude mcp add -s user bitrix24 -- uv run --directory C:/Scripts/BitrixMCP bitrix-mcp

Repo-shared .mcp.json (stdio):

{
"mcpServers": {
"bitrix24": {
"command": "uv",
"args": ["run", "--directory", "C:/Scripts/BitrixMCP", "bitrix-mcp"],
"env": { "BITRIX_WEBHOOK_URL": "https://your-portal.bitrix24.ru/rest/1/xxxx/" }
}
}
}

Claude Code (HTTP):

bitrix-mcp --http --port 5015 # then, on the client:
claude mcp add -s user --transport http bitrix24 http://HOST:5015/mcp

Claude Desktop (stdio) — %APPDATA%\Claude\claude_desktop_config.json:

{
"mcpServers": {
"bitrix24": {
"command": "uv",
"args": ["run", "--directory", "C:/Scripts/BitrixMCP", "bitrix-mcp"],
"env": { "BITRIX_WEBHOOK_URL": "https://your-portal.bitrix24.ru/rest/1/xxxx/" }
}
}
}

(For a remote HTTP instance, Desktop still needs the mcp-remote bridge; stdio above avoids it entirely.)

Tool catalog (99)

Universal — b24_call, b24_batch, b24_test_connection, b24_list_methodsCRM — b24_crm_list, b24_crm_get, b24_crm_fields, b24_crm_add, b24_crm_update, b24_crm_delete, b24_crm_timeline_comment_add, b24_crm_timeline_comment_list, b24_crm_category_list (pipelines), b24_crm_status_list (stages/dictionaries), b24_crm_activity_list, b24_crm_activity_add, b24_crm_activity_delete, b24_crm_productrows_get, b24_crm_productrows_set, b24_crm_currency_list, b24_crm_requisite_list, b24_crm_deal_contacts_get, b24_crm_deal_contacts_set (classic entities and SPA via entity_type_id) Tasks — b24_tasks_list, b24_task_get, b24_task_add, b24_task_update, b24_task_complete, b24_task_delete, b24_task_comments_list, b24_task_comment_add, b24_task_stages_get, b24_task_checklist_list, b24_task_checklist_add, b24_task_elapsed_add, b24_task_result_listScrum — b24_scrum_sprint_list, b24_scrum_kanban_stages, b24_scrum_board, b24_scrum_task_moveCalendar — b24_calendar_event_list, b24_calendar_section_list, b24_calendar_event_add, b24_calendar_event_update, b24_calendar_event_deleteDisk — b24_disk_storage_list, b24_disk_folder_items, b24_disk_file_get, b24_disk_file_content (server-side download → base64), b24_disk_folder_add, b24_disk_file_upload, b24_disk_file_deleteUsers/structure — b24_user_get, b24_user_search, b24_user_current, b24_department_getGroups (workgroups) — b24_group_list, b24_group_users, b24_group_create, b24_group_update, b24_group_deleteMessaging — b24_im_recent, b24_im_dialog_messages, b24_im_message_add, b24_im_notify_personal, b24_im_user_get, b24_im_chat_create, b24_im_chat_user_add, b24_feed_post_addLists (universal lists) — b24_lists_get, b24_lists_element_list, b24_lists_element_add, b24_lists_element_update, b24_lists_element_deleteCatalog / products — b24_catalog_list, b24_catalog_section_list, b24_catalog_product_list, b24_catalog_product_get, b24_catalog_product_add, b24_catalog_product_update, b24_crm_product_listSale (orders) — b24_sale_order_list, b24_sale_order_getDocuments — b24_documentgenerator_templates, b24_documentgenerator_addBizproc — b24_bizproc_template_list, b24_bizproc_startTelephony — b24_telephony_statistics

Anything still not typed here is reachable through b24_call (e.g. mail, open-lines, sale basket writes, admin/app-placement methods).

Retrospective-app integration

This server has no knowledge of any downstream app. An agent connects to both this server and your app's MCP, reads Bitrix here, and relays into the app's contract. Field names from b24_tasks_list / b24_calendar_event_list map directly onto PushSprintTask / PushCalendarEvent, so the mapping is trivial — but that translation lives in the agent, not here.

Documentation

docs/USAGE.md — how to drive the tools: auth, filters, pagination, batch, errors, recipes.
ARCHITECTURE.md — components, call flow, deployment; diagrams in docs/diagrams/.
ROADMAP.md — status, history, and out-of-scope boundaries.

Development

uv sync # install runtime + dev deps
uv run pytest -q # offline unit tests (no portal needed)
uv run python scripts/smoke.py "<webhook>"# live read-only access map (run from a network with portal access)

Verification scripts

Each one exits non-zero when a check fails, so they can be chained in CI. Those marked offline need no portal; the rest need a reachable webhook.

Script	What it proves	Needs
`scripts/startup_check.py`	The server boots on both transports and registers every tool	offline
`scripts/leak_check.py`	The sanitizer strips webhooks/tokens from output and from httpx logs	offline
`scripts/git_secret_scan.py`	No secret is present in tracked files or anywhere in git history	offline
`scripts/events_tools_check.py`	poll → ack → history → stats against a seeded store	offline
`scripts/coverage_check.py`	Requirement R-1: catalogue + scope diagnosis reach the whole API	portal
`scripts/poller_check.py`	`b24_changes_since` cursors advance and do not skip rows	portal
`scripts/pull_channel_check.py`	Push & Pull channel subscribes and receives	portal
`scripts/receiver_e2e_check.py`	Outgoing-webhook receiver end to end, including TLS	portal
`scripts/telegram_check.py`	Filter DSL routes the right events	offline
`scripts/telegram_live_check.py`	The bot and chat really accept a message	Telegram
`scripts/smoke.py`	Live read-only access map across every domain	portal
`scripts/build_catalog.py`	Regenerates `data/catalog.json` from the official docs	docs checkout

Probes (diagnostics, no pass/fail verdict): pull_probe.py, probe_listener.py, tg_conn_probe.py.

Diagrams are regenerated with java -jar plantuml.jar -tpng docs/diagrams/*.puml.

Notes on limits

fetch_all=true is capped by BITRIX_MAX_PAGES (default 40 pages ≈ 2000 records) and reports truncated: true when it hits the cap — it never silently stops short.
The read-only guard classifies writes by method verb; typed write tools are always classified correctly. b24_call/b24_batch use the heuristic.

Licence

MIT — see LICENSE.

Security

Found a vulnerability? Please report it privately, not in a public issue — see SECURITY.md. The webhook URL this server uses is a bearer credential for the whole portal.

Support author

BTC: bc1q3frrup5neh7nhfg944etu2agd4j9u0vg3jyee6

ETH(Arbitrum): 0x43B349d8Cea83215D707EBa3bc35e9917f746b0a

TRX: THSzvy49KNeqRjXsGkurh2A5G4avV4RgN4

XRP: rLWZjS3DMupC4ZdXCX3BVYn4dEtC3iNhgy

SOL: 3xwfybxJ6Tz5t6pjBBkL5yYQCZo6wfbv932UNA4ThdP8

ADA: addr1q926ys75jp5wn2pv32a3t8r8pdhr7w02v0t9j4a8pmg0ruww5rlkctu4lnz2hfcwa5qfn3zhsd0s23r22uqwzx9gu6cq5c4e76

TON: UQC4qlAOD9Nly4K_66GJ_yCsSM3x2sB0vZ2GrBQbc--gZUui

DOGE: DTjNYmbtymzcjUiV4MsZY8MP4dM7MJ6qLC

XMR: 44qRqM6YtnxXUhkgCFqDDrKMPjWriu69FLBoop8Kwp7e1VQsBUJoVQ8JYQjfMV5C6uidTUgSSyoJ65mq8aYG2esZ1rrqfwt

bitrix-mcp

English · Русский

Universal, full-featured, portable MCP server for the Bitrix24 REST API. Read and write. Not tied to any one application — it's a generic Bitrix24 gateway that any MCP client or agent can mount (Claude Code, Claude Desktop, Cursor, Windsurf, Cline, or your own Python/Node agent).

Language: Python + the official MCP SDK (mcp.server.mcpserver, 2.x)
Transports:stdio (default, most portable/reliable) and Streamable HTTP (stateless JSON — no fragile long-lived SSE bridge)
Coverage: universal b24_call / b24_batch reach 100% of the REST API; a catalogue built from the official docs (1930 methods) tells the agent which method it needs and what parameters it takes; 99 typed tools cover the high-traffic domains with the tricky bits handled.
Portal events: three ways to receive them — pull channel (works behind NAT and VPN), outgoing-webhook receiver, poller — plus a history archive and Telegram forwarding: docs/EVENTS.md

Why this exists / what it fixes

Rebuilt from field notes on a previous wrapper. The bugs that motivated it are fixed by design, not patched around:

Old behavior	Fix here
`filter` silently ignored (`groups_list`, `users_list`), full-portal dumps → timeouts	Params sent as JSON POST body, so nested `filter`/`select`/`order` are parsed correctly by Bitrix. Real pagination with a page cap.
Access errors swallowed into a fake "0 results" (`read_pipelines` etc.)	Errors are never swallowed — a Bitrix `error`/`error_description` always surfaces with its `code` (e.g. `ACCESS_DENIED`).
`calendar_list` returned 0 without explicit `ownerId`	`owner_id`auto-resolves to the acting user.
Scrum kanban read from the wrong place	Correct flow baked in: active-sprint filter + `tasks.api.scrum.kanban.getStages` (`b24_scrum_board` does it in one call).
Fragile `mcp-remote` SSE session drops / hangs	Prefer stdio (no bridge) or stateless Streamable HTTP.
`department.get` has no server-side filter at all (a Bitrix API limitation, undocumented) — any `filter` was silently ignored and the whole department tree (95+ rows) came back regardless	`b24_department_get` filters client-side after a full fetch, so `filter`/`ID` genuinely narrow the result instead of quietly dumping everything.
Bitrix sometimes reports a failure as `{"error": "", "error_description": "Access denied."}` — an empty-string error code — which a naive truthiness check (`if data.get("error")`) misses, losing the code and message to a generic HTTP-status fallback	Checked by key presence, not truthiness — `code`/`message` always reflect what Bitrix actually said.
`calendar.event.add` / `.update` silently drop `attendees` unless `is_meeting` is also set — 200 OK, event created, nobody invited, no error anywhere	`is_meeting` is auto-set to `'Y'` whenever `attendees` is non-empty and not already specified.
Moving a task on a Scrum sprint board has no single API call, and every obvious candidate fails while reporting success: `tasks.task.update`'s `STAGE_ID` changes the field and writes a history entry everyone can see, but the card stays put; `kanban.addTask` only places a card that is off the board and answers `true` without doing anything for one already in a column; `task.stages.movetask` answers `false`.	`b24_scrum_task_move` takes the card off the board and puts it back at the target column (`kanban.deleteTask` → `kanban.addTask`) — verified by watching a real board, not by trusting the response. It also warns that `STAGE_ID` cannot verify the result: it read `0` while the card was visibly in the target column.

Install

If nothing is installed on the machine, take the portable archive (dist/bitrix-mcp-portable.zip, built by python scripts/build_portable.py). It carries its own Python and every library — no uv, no pip, no PyPI access. Unzip it and run the bundled launcher.

From source:

uv sync # create venv + install# or, as a tool on PATH:
uv tool install .# exposes the `bitrix-mcp` command

Configure

Set the default webhook (see .env.example):

export BITRIX_WEBHOOK_URL="https://your-portal.bitrix24.ru/rest/1/xxxxxxxx/"# optional:export BITRIX_READ_ONLY=1 # block all writes

The webhook comes from Bitrix: Profile → Webhooks → inbound webhook, format https://<portal>/rest/<user_id>/<token>/. The token is a credential — keep it out of source control (.env is gitignored).

Auth precedence per call:personal_webhook → webhook_url → X-B24-Webhook HTTP header → BITRIX_WEBHOOK_URL. Pass personal_webhook to act (and write) as a specific user.

Run

bitrix-mcp # stdio (default)
bitrix-mcp --http # Streamable HTTP on 127.0.0.1:8000/mcp
bitrix-mcp --http --host 0.0.0.0 --port 5015 # shared network service

Connect a client

Claude Code (stdio, recommended):

claude mcp add -s user bitrix24 -- uv run --directory C:/Scripts/BitrixMCP bitrix-mcp

Repo-shared .mcp.json (stdio):

{
"mcpServers": {
"bitrix24": {
"command": "uv",
"args": ["run", "--directory", "C:/Scripts/BitrixMCP", "bitrix-mcp"],
"env": { "BITRIX_WEBHOOK_URL": "https://your-portal.bitrix24.ru/rest/1/xxxx/" }
}
}
}

Claude Code (HTTP):

bitrix-mcp --http --port 5015 # then, on the client:
claude mcp add -s user --transport http bitrix24 http://HOST:5015/mcp

Claude Desktop (stdio) — %APPDATA%\Claude\claude_desktop_config.json:

{
"mcpServers": {
"bitrix24": {
"command": "uv",
"args": ["run", "--directory", "C:/Scripts/BitrixMCP", "bitrix-mcp"],
"env": { "BITRIX_WEBHOOK_URL": "https://your-portal.bitrix24.ru/rest/1/xxxx/" }
}
}
}

(For a remote HTTP instance, Desktop still needs the mcp-remote bridge; stdio above avoids it entirely.)

Tool catalog (99)

Universal — b24_call, b24_batch, b24_test_connection, b24_list_methodsCRM — b24_crm_list, b24_crm_get, b24_crm_fields, b24_crm_add, b24_crm_update, b24_crm_delete, b24_crm_timeline_comment_add, b24_crm_timeline_comment_list, b24_crm_category_list (pipelines), b24_crm_status_list (stages/dictionaries), b24_crm_activity_list, b24_crm_activity_add, b24_crm_activity_delete, b24_crm_productrows_get, b24_crm_productrows_set, b24_crm_currency_list, b24_crm_requisite_list, b24_crm_deal_contacts_get, b24_crm_deal_contacts_set (classic entities and SPA via entity_type_id) Tasks — b24_tasks_list, b24_task_get, b24_task_add, b24_task_update, b24_task_complete, b24_task_delete, b24_task_comments_list, b24_task_comment_add, b24_task_stages_get, b24_task_checklist_list, b24_task_checklist_add, b24_task_elapsed_add, b24_task_result_listScrum — b24_scrum_sprint_list, b24_scrum_kanban_stages, b24_scrum_board, b24_scrum_task_moveCalendar — b24_calendar_event_list, b24_calendar_section_list, b24_calendar_event_add, b24_calendar_event_update, b24_calendar_event_deleteDisk — b24_disk_storage_list, b24_disk_folder_items, b24_disk_file_get, b24_disk_file_content (server-side download → base64), b24_disk_folder_add, b24_disk_file_upload, b24_disk_file_deleteUsers/structure — b24_user_get, b24_user_search, b24_user_current, b24_department_getGroups (workgroups) — b24_group_list, b24_group_users, b24_group_create, b24_group_update, b24_group_deleteMessaging — b24_im_recent, b24_im_dialog_messages, b24_im_message_add, b24_im_notify_personal, b24_im_user_get, b24_im_chat_create, b24_im_chat_user_add, b24_feed_post_addLists (universal lists) — b24_lists_get, b24_lists_element_list, b24_lists_element_add, b24_lists_element_update, b24_lists_element_deleteCatalog / products — b24_catalog_list, b24_catalog_section_list, b24_catalog_product_list, b24_catalog_product_get, b24_catalog_product_add, b24_catalog_product_update, b24_crm_product_listSale (orders) — b24_sale_order_list, b24_sale_order_getDocuments — b24_documentgenerator_templates, b24_documentgenerator_addBizproc — b24_bizproc_template_list, b24_bizproc_startTelephony — b24_telephony_statistics

Anything still not typed here is reachable through b24_call (e.g. mail, open-lines, sale basket writes, admin/app-placement methods).

Retrospective-app integration

This server has no knowledge of any downstream app. An agent connects to both this server and your app's MCP, reads Bitrix here, and relays into the app's contract. Field names from b24_tasks_list / b24_calendar_event_list map directly onto PushSprintTask / PushCalendarEvent, so the mapping is trivial — but that translation lives in the agent, not here.

Documentation

docs/USAGE.md — how to drive the tools: auth, filters, pagination, batch, errors, recipes.
ARCHITECTURE.md — components, call flow, deployment; diagrams in docs/diagrams/.
ROADMAP.md — status, history, and out-of-scope boundaries.

Development

uv sync # install runtime + dev deps
uv run pytest -q # offline unit tests (no portal needed)
uv run python scripts/smoke.py "<webhook>"# live read-only access map (run from a network with portal access)

Verification scripts

Each one exits non-zero when a check fails, so they can be chained in CI. Those marked offline need no portal; the rest need a reachable webhook.

Script	What it proves	Needs
`scripts/startup_check.py`	The server boots on both transports and registers every tool	offline
`scripts/leak_check.py`	The sanitizer strips webhooks/tokens from output and from httpx logs	offline
`scripts/git_secret_scan.py`	No secret is present in tracked files or anywhere in git history	offline
`scripts/events_tools_check.py`	poll → ack → history → stats against a seeded store	offline
`scripts/coverage_check.py`	Requirement R-1: catalogue + scope diagnosis reach the whole API	portal
`scripts/poller_check.py`	`b24_changes_since` cursors advance and do not skip rows	portal
`scripts/pull_channel_check.py`	Push & Pull channel subscribes and receives	portal
`scripts/receiver_e2e_check.py`	Outgoing-webhook receiver end to end, including TLS	portal
`scripts/telegram_check.py`	Filter DSL routes the right events	offline
`scripts/telegram_live_check.py`	The bot and chat really accept a message	Telegram
`scripts/smoke.py`	Live read-only access map across every domain	portal
`scripts/build_catalog.py`	Regenerates `data/catalog.json` from the official docs	docs checkout

Probes (diagnostics, no pass/fail verdict): pull_probe.py, probe_listener.py, tg_conn_probe.py.

Diagrams are regenerated with java -jar plantuml.jar -tpng docs/diagrams/*.puml.

Notes on limits

fetch_all=true is capped by BITRIX_MAX_PAGES (default 40 pages ≈ 2000 records) and reports truncated: true when it hits the cap — it never silently stops short.
The read-only guard classifies writes by method verb; typed write tools are always classified correctly. b24_call/b24_batch use the heuristic.

Licence

MIT — see LICENSE.

Security

Found a vulnerability? Please report it privately, not in a public issue — see SECURITY.md. The webhook URL this server uses is a bearer credential for the whole portal.

Support author

BTC: bc1q3frrup5neh7nhfg944etu2agd4j9u0vg3jyee6

ETH(Arbitrum): 0x43B349d8Cea83215D707EBa3bc35e9917f746b0a

TRX: THSzvy49KNeqRjXsGkurh2A5G4avV4RgN4

XRP: rLWZjS3DMupC4ZdXCX3BVYn4dEtC3iNhgy

SOL: 3xwfybxJ6Tz5t6pjBBkL5yYQCZo6wfbv932UNA4ThdP8

ADA: addr1q926ys75jp5wn2pv32a3t8r8pdhr7w02v0t9j4a8pmg0ruww5rlkctu4lnz2hfcwa5qfn3zhsd0s23r22uqwzx9gu6cq5c4e76

TON: UQC4qlAOD9Nly4K_66GJ_yCsSM3x2sB0vZ2GrBQbc--gZUui

DOGE: DTjNYmbtymzcjUiV4MsZY8MP4dM7MJ6qLC

XMR: 44qRqM6YtnxXUhkgCFqDDrKMPjWriu69FLBoop8Kwp7e1VQsBUJoVQ8JYQjfMV5C6uidTUgSSyoJ65mq8aYG2esZ1rrqfwt

bitrix-mcp

English · Русский

Universal, full-featured, portable MCP server for the Bitrix24 REST API. Read and write. Not tied to any one application — it's a generic Bitrix24 gateway that any MCP client or agent can mount (Claude Code, Claude Desktop, Cursor, Windsurf, Cline, or your own Python/Node agent).

Language: Python + the official MCP SDK (mcp.server.mcpserver, 2.x)
Transports:stdio (default, most portable/reliable) and Streamable HTTP (stateless JSON — no fragile long-lived SSE bridge)
Coverage: universal b24_call / b24_batch reach 100% of the REST API; a catalogue built from the official docs (1930 methods) tells the agent which method it needs and what parameters it takes; 99 typed tools cover the high-traffic domains with the tricky bits handled.
Portal events: three ways to receive them — pull channel (works behind NAT and VPN), outgoing-webhook receiver, poller — plus a history archive and Telegram forwarding: docs/EVENTS.md

Why this exists / what it fixes

Rebuilt from field notes on a previous wrapper. The bugs that motivated it are fixed by design, not patched around:

Old behavior	Fix here
`filter` silently ignored (`groups_list`, `users_list`), full-portal dumps → timeouts	Params sent as JSON POST body, so nested `filter`/`select`/`order` are parsed correctly by Bitrix. Real pagination with a page cap.
Access errors swallowed into a fake "0 results" (`read_pipelines` etc.)	Errors are never swallowed — a Bitrix `error`/`error_description` always surfaces with its `code` (e.g. `ACCESS_DENIED`).
`calendar_list` returned 0 without explicit `ownerId`	`owner_id`auto-resolves to the acting user.
Scrum kanban read from the wrong place	Correct flow baked in: active-sprint filter + `tasks.api.scrum.kanban.getStages` (`b24_scrum_board` does it in one call).
Fragile `mcp-remote` SSE session drops / hangs	Prefer stdio (no bridge) or stateless Streamable HTTP.
`department.get` has no server-side filter at all (a Bitrix API limitation, undocumented) — any `filter` was silently ignored and the whole department tree (95+ rows) came back regardless	`b24_department_get` filters client-side after a full fetch, so `filter`/`ID` genuinely narrow the result instead of quietly dumping everything.
Bitrix sometimes reports a failure as `{"error": "", "error_description": "Access denied."}` — an empty-string error code — which a naive truthiness check (`if data.get("error")`) misses, losing the code and message to a generic HTTP-status fallback	Checked by key presence, not truthiness — `code`/`message` always reflect what Bitrix actually said.
`calendar.event.add` / `.update` silently drop `attendees` unless `is_meeting` is also set — 200 OK, event created, nobody invited, no error anywhere	`is_meeting` is auto-set to `'Y'` whenever `attendees` is non-empty and not already specified.
Moving a task on a Scrum sprint board has no single API call, and every obvious candidate fails while reporting success: `tasks.task.update`'s `STAGE_ID` changes the field and writes a history entry everyone can see, but the card stays put; `kanban.addTask` only places a card that is off the board and answers `true` without doing anything for one already in a column; `task.stages.movetask` answers `false`.	`b24_scrum_task_move` takes the card off the board and puts it back at the target column (`kanban.deleteTask` → `kanban.addTask`) — verified by watching a real board, not by trusting the response. It also warns that `STAGE_ID` cannot verify the result: it read `0` while the card was visibly in the target column.

Install

If nothing is installed on the machine, take the portable archive (dist/bitrix-mcp-portable.zip, built by python scripts/build_portable.py). It carries its own Python and every library — no uv, no pip, no PyPI access. Unzip it and run the bundled launcher.

From source:

uv sync # create venv + install# or, as a tool on PATH:
uv tool install .# exposes the `bitrix-mcp` command

Configure

Set the default webhook (see .env.example):

export BITRIX_WEBHOOK_URL="https://your-portal.bitrix24.ru/rest/1/xxxxxxxx/"# optional:export BITRIX_READ_ONLY=1 # block all writes

The webhook comes from Bitrix: Profile → Webhooks → inbound webhook, format https://<portal>/rest/<user_id>/<token>/. The token is a credential — keep it out of source control (.env is gitignored).

Auth precedence per call:personal_webhook → webhook_url → X-B24-Webhook HTTP header → BITRIX_WEBHOOK_URL. Pass personal_webhook to act (and write) as a specific user.

Run

bitrix-mcp # stdio (default)
bitrix-mcp --http # Streamable HTTP on 127.0.0.1:8000/mcp
bitrix-mcp --http --host 0.0.0.0 --port 5015 # shared network service

Connect a client

Claude Code (stdio, recommended):

claude mcp add -s user bitrix24 -- uv run --directory C:/Scripts/BitrixMCP bitrix-mcp

Repo-shared .mcp.json (stdio):

{
"mcpServers": {
"bitrix24": {
"command": "uv",
"args": ["run", "--directory", "C:/Scripts/BitrixMCP", "bitrix-mcp"],
"env": { "BITRIX_WEBHOOK_URL": "https://your-portal.bitrix24.ru/rest/1/xxxx/" }
}
}
}

Claude Code (HTTP):

bitrix-mcp --http --port 5015 # then, on the client:
claude mcp add -s user --transport http bitrix24 http://HOST:5015/mcp

Claude Desktop (stdio) — %APPDATA%\Claude\claude_desktop_config.json:

{
"mcpServers": {
"bitrix24": {
"command": "uv",
"args": ["run", "--directory", "C:/Scripts/BitrixMCP", "bitrix-mcp"],
"env": { "BITRIX_WEBHOOK_URL": "https://your-portal.bitrix24.ru/rest/1/xxxx/" }
}
}
}

(For a remote HTTP instance, Desktop still needs the mcp-remote bridge; stdio above avoids it entirely.)

Tool catalog (99)

Universal — b24_call, b24_batch, b24_test_connection, b24_list_methodsCRM — b24_crm_list, b24_crm_get, b24_crm_fields, b24_crm_add, b24_crm_update, b24_crm_delete, b24_crm_timeline_comment_add, b24_crm_timeline_comment_list, b24_crm_category_list (pipelines), b24_crm_status_list (stages/dictionaries), b24_crm_activity_list, b24_crm_activity_add, b24_crm_activity_delete, b24_crm_productrows_get, b24_crm_productrows_set, b24_crm_currency_list, b24_crm_requisite_list, b24_crm_deal_contacts_get, b24_crm_deal_contacts_set (classic entities and SPA via entity_type_id) Tasks — b24_tasks_list, b24_task_get, b24_task_add, b24_task_update, b24_task_complete, b24_task_delete, b24_task_comments_list, b24_task_comment_add, b24_task_stages_get, b24_task_checklist_list, b24_task_checklist_add, b24_task_elapsed_add, b24_task_result_listScrum — b24_scrum_sprint_list, b24_scrum_kanban_stages, b24_scrum_board, b24_scrum_task_moveCalendar — b24_calendar_event_list, b24_calendar_section_list, b24_calendar_event_add, b24_calendar_event_update, b24_calendar_event_deleteDisk — b24_disk_storage_list, b24_disk_folder_items, b24_disk_file_get, b24_disk_file_content (server-side download → base64), b24_disk_folder_add, b24_disk_file_upload, b24_disk_file_deleteUsers/structure — b24_user_get, b24_user_search, b24_user_current, b24_department_getGroups (workgroups) — b24_group_list, b24_group_users, b24_group_create, b24_group_update, b24_group_deleteMessaging — b24_im_recent, b24_im_dialog_messages, b24_im_message_add, b24_im_notify_personal, b24_im_user_get, b24_im_chat_create, b24_im_chat_user_add, b24_feed_post_addLists (universal lists) — b24_lists_get, b24_lists_element_list, b24_lists_element_add, b24_lists_element_update, b24_lists_element_deleteCatalog / products — b24_catalog_list, b24_catalog_section_list, b24_catalog_product_list, b24_catalog_product_get, b24_catalog_product_add, b24_catalog_product_update, b24_crm_product_listSale (orders) — b24_sale_order_list, b24_sale_order_getDocuments — b24_documentgenerator_templates, b24_documentgenerator_addBizproc — b24_bizproc_template_list, b24_bizproc_startTelephony — b24_telephony_statistics

Anything still not typed here is reachable through b24_call (e.g. mail, open-lines, sale basket writes, admin/app-placement methods).

Retrospective-app integration

This server has no knowledge of any downstream app. An agent connects to both this server and your app's MCP, reads Bitrix here, and relays into the app's contract. Field names from b24_tasks_list / b24_calendar_event_list map directly onto PushSprintTask / PushCalendarEvent, so the mapping is trivial — but that translation lives in the agent, not here.

Documentation

docs/USAGE.md — how to drive the tools: auth, filters, pagination, batch, errors, recipes.
ARCHITECTURE.md — components, call flow, deployment; diagrams in docs/diagrams/.
ROADMAP.md — status, history, and out-of-scope boundaries.

Development

uv sync # install runtime + dev deps
uv run pytest -q # offline unit tests (no portal needed)
uv run python scripts/smoke.py "<webhook>"# live read-only access map (run from a network with portal access)

Verification scripts

Each one exits non-zero when a check fails, so they can be chained in CI. Those marked offline need no portal; the rest need a reachable webhook.

Script	What it proves	Needs
`scripts/startup_check.py`	The server boots on both transports and registers every tool	offline
`scripts/leak_check.py`	The sanitizer strips webhooks/tokens from output and from httpx logs	offline
`scripts/git_secret_scan.py`	No secret is present in tracked files or anywhere in git history	offline
`scripts/events_tools_check.py`	poll → ack → history → stats against a seeded store	offline
`scripts/coverage_check.py`	Requirement R-1: catalogue + scope diagnosis reach the whole API	portal
`scripts/poller_check.py`	`b24_changes_since` cursors advance and do not skip rows	portal
`scripts/pull_channel_check.py`	Push & Pull channel subscribes and receives	portal
`scripts/receiver_e2e_check.py`	Outgoing-webhook receiver end to end, including TLS	portal
`scripts/telegram_check.py`	Filter DSL routes the right events	offline
`scripts/telegram_live_check.py`	The bot and chat really accept a message	Telegram
`scripts/smoke.py`	Live read-only access map across every domain	portal
`scripts/build_catalog.py`	Regenerates `data/catalog.json` from the official docs	docs checkout

Probes (diagnostics, no pass/fail verdict): pull_probe.py, probe_listener.py, tg_conn_probe.py.

Diagrams are regenerated with java -jar plantuml.jar -tpng docs/diagrams/*.puml.

Notes on limits

fetch_all=true is capped by BITRIX_MAX_PAGES (default 40 pages ≈ 2000 records) and reports truncated: true when it hits the cap — it never silently stops short.
The read-only guard classifies writes by method verb; typed write tools are always classified correctly. b24_call/b24_batch use the heuristic.

Licence

MIT — see LICENSE.

Security

Found a vulnerability? Please report it privately, not in a public issue — see SECURITY.md. The webhook URL this server uses is a bearer credential for the whole portal.

Support author

BTC: bc1q3frrup5neh7nhfg944etu2agd4j9u0vg3jyee6

ETH(Arbitrum): 0x43B349d8Cea83215D707EBa3bc35e9917f746b0a

TRX: THSzvy49KNeqRjXsGkurh2A5G4avV4RgN4

XRP: rLWZjS3DMupC4ZdXCX3BVYn4dEtC3iNhgy

SOL: 3xwfybxJ6Tz5t6pjBBkL5yYQCZo6wfbv932UNA4ThdP8

ADA: addr1q926ys75jp5wn2pv32a3t8r8pdhr7w02v0t9j4a8pmg0ruww5rlkctu4lnz2hfcwa5qfn3zhsd0s23r22uqwzx9gu6cq5c4e76

TON: UQC4qlAOD9Nly4K_66GJ_yCsSM3x2sB0vZ2GrBQbc--gZUui

DOGE: DTjNYmbtymzcjUiV4MsZY8MP4dM7MJ6qLC

XMR: 44qRqM6YtnxXUhkgCFqDDrKMPjWriu69FLBoop8Kwp7e1VQsBUJoVQ8JYQjfMV5C6uidTUgSSyoJ65mq8aYG2esZ1rrqfwt

bitrix-mcp

English · Русский

Universal, full-featured, portable MCP server for the Bitrix24 REST API. Read and write. Not tied to any one application — it's a generic Bitrix24 gateway that any MCP client or agent can mount (Claude Code, Claude Desktop, Cursor, Windsurf, Cline, or your own Python/Node agent).

Language: Python + the official MCP SDK (mcp.server.mcpserver, 2.x)
Transports:stdio (default, most portable/reliable) and Streamable HTTP (stateless JSON — no fragile long-lived SSE bridge)
Coverage: universal b24_call / b24_batch reach 100% of the REST API; a catalogue built from the official docs (1930 methods) tells the agent which method it needs and what parameters it takes; 99 typed tools cover the high-traffic domains with the tricky bits handled.
Portal events: three ways to receive them — pull channel (works behind NAT and VPN), outgoing-webhook receiver, poller — plus a history archive and Telegram forwarding: docs/EVENTS.md

Why this exists / what it fixes

Rebuilt from field notes on a previous wrapper. The bugs that motivated it are fixed by design, not patched around:

Old behavior	Fix here
`filter` silently ignored (`groups_list`, `users_list`), full-portal dumps → timeouts	Params sent as JSON POST body, so nested `filter`/`select`/`order` are parsed correctly by Bitrix. Real pagination with a page cap.
Access errors swallowed into a fake "0 results" (`read_pipelines` etc.)	Errors are never swallowed — a Bitrix `error`/`error_description` always surfaces with its `code` (e.g. `ACCESS_DENIED`).
`calendar_list` returned 0 without explicit `ownerId`	`owner_id`auto-resolves to the acting user.
Scrum kanban read from the wrong place	Correct flow baked in: active-sprint filter + `tasks.api.scrum.kanban.getStages` (`b24_scrum_board` does it in one call).
Fragile `mcp-remote` SSE session drops / hangs	Prefer stdio (no bridge) or stateless Streamable HTTP.
`department.get` has no server-side filter at all (a Bitrix API limitation, undocumented) — any `filter` was silently ignored and the whole department tree (95+ rows) came back regardless	`b24_department_get` filters client-side after a full fetch, so `filter`/`ID` genuinely narrow the result instead of quietly dumping everything.
Bitrix sometimes reports a failure as `{"error": "", "error_description": "Access denied."}` — an empty-string error code — which a naive truthiness check (`if data.get("error")`) misses, losing the code and message to a generic HTTP-status fallback	Checked by key presence, not truthiness — `code`/`message` always reflect what Bitrix actually said.
`calendar.event.add` / `.update` silently drop `attendees` unless `is_meeting` is also set — 200 OK, event created, nobody invited, no error anywhere	`is_meeting` is auto-set to `'Y'` whenever `attendees` is non-empty and not already specified.
Moving a task on a Scrum sprint board has no single API call, and every obvious candidate fails while reporting success: `tasks.task.update`'s `STAGE_ID` changes the field and writes a history entry everyone can see, but the card stays put; `kanban.addTask` only places a card that is off the board and answers `true` without doing anything for one already in a column; `task.stages.movetask` answers `false`.	`b24_scrum_task_move` takes the card off the board and puts it back at the target column (`kanban.deleteTask` → `kanban.addTask`) — verified by watching a real board, not by trusting the response. It also warns that `STAGE_ID` cannot verify the result: it read `0` while the card was visibly in the target column.

Install

If nothing is installed on the machine, take the portable archive (dist/bitrix-mcp-portable.zip, built by python scripts/build_portable.py). It carries its own Python and every library — no uv, no pip, no PyPI access. Unzip it and run the bundled launcher.

From source:

uv sync # create venv + install# or, as a tool on PATH:
uv tool install .# exposes the `bitrix-mcp` command

Configure

Set the default webhook (see .env.example):

export BITRIX_WEBHOOK_URL="https://your-portal.bitrix24.ru/rest/1/xxxxxxxx/"# optional:export BITRIX_READ_ONLY=1 # block all writes

The webhook comes from Bitrix: Profile → Webhooks → inbound webhook, format https://<portal>/rest/<user_id>/<token>/. The token is a credential — keep it out of source control (.env is gitignored).

Auth precedence per call:personal_webhook → webhook_url → X-B24-Webhook HTTP header → BITRIX_WEBHOOK_URL. Pass personal_webhook to act (and write) as a specific user.

Run

bitrix-mcp # stdio (default)
bitrix-mcp --http # Streamable HTTP on 127.0.0.1:8000/mcp
bitrix-mcp --http --host 0.0.0.0 --port 5015 # shared network service

Connect a client

Claude Code (stdio, recommended):

claude mcp add -s user bitrix24 -- uv run --directory C:/Scripts/BitrixMCP bitrix-mcp

Repo-shared .mcp.json (stdio):

{
"mcpServers": {
"bitrix24": {
"command": "uv",
"args": ["run", "--directory", "C:/Scripts/BitrixMCP", "bitrix-mcp"],
"env": { "BITRIX_WEBHOOK_URL": "https://your-portal.bitrix24.ru/rest/1/xxxx/" }
}
}
}

Claude Code (HTTP):

bitrix-mcp --http --port 5015 # then, on the client:
claude mcp add -s user --transport http bitrix24 http://HOST:5015/mcp

Claude Desktop (stdio) — %APPDATA%\Claude\claude_desktop_config.json:

{
"mcpServers": {
"bitrix24": {
"command": "uv",
"args": ["run", "--directory", "C:/Scripts/BitrixMCP", "bitrix-mcp"],
"env": { "BITRIX_WEBHOOK_URL": "https://your-portal.bitrix24.ru/rest/1/xxxx/" }
}
}
}

(For a remote HTTP instance, Desktop still needs the mcp-remote bridge; stdio above avoids it entirely.)

Tool catalog (99)

Universal — b24_call, b24_batch, b24_test_connection, b24_list_methodsCRM — b24_crm_list, b24_crm_get, b24_crm_fields, b24_crm_add, b24_crm_update, b24_crm_delete, b24_crm_timeline_comment_add, b24_crm_timeline_comment_list, b24_crm_category_list (pipelines), b24_crm_status_list (stages/dictionaries), b24_crm_activity_list, b24_crm_activity_add, b24_crm_activity_delete, b24_crm_productrows_get, b24_crm_productrows_set, b24_crm_currency_list, b24_crm_requisite_list, b24_crm_deal_contacts_get, b24_crm_deal_contacts_set (classic entities and SPA via entity_type_id) Tasks — b24_tasks_list, b24_task_get, b24_task_add, b24_task_update, b24_task_complete, b24_task_delete, b24_task_comments_list, b24_task_comment_add, b24_task_stages_get, b24_task_checklist_list, b24_task_checklist_add, b24_task_elapsed_add, b24_task_result_listScrum — b24_scrum_sprint_list, b24_scrum_kanban_stages, b24_scrum_board, b24_scrum_task_moveCalendar — b24_calendar_event_list, b24_calendar_section_list, b24_calendar_event_add, b24_calendar_event_update, b24_calendar_event_deleteDisk — b24_disk_storage_list, b24_disk_folder_items, b24_disk_file_get, b24_disk_file_content (server-side download → base64), b24_disk_folder_add, b24_disk_file_upload, b24_disk_file_deleteUsers/structure — b24_user_get, b24_user_search, b24_user_current, b24_department_getGroups (workgroups) — b24_group_list, b24_group_users, b24_group_create, b24_group_update, b24_group_deleteMessaging — b24_im_recent, b24_im_dialog_messages, b24_im_message_add, b24_im_notify_personal, b24_im_user_get, b24_im_chat_create, b24_im_chat_user_add, b24_feed_post_addLists (universal lists) — b24_lists_get, b24_lists_element_list, b24_lists_element_add, b24_lists_element_update, b24_lists_element_deleteCatalog / products — b24_catalog_list, b24_catalog_section_list, b24_catalog_product_list, b24_catalog_product_get, b24_catalog_product_add, b24_catalog_product_update, b24_crm_product_listSale (orders) — b24_sale_order_list, b24_sale_order_getDocuments — b24_documentgenerator_templates, b24_documentgenerator_addBizproc — b24_bizproc_template_list, b24_bizproc_startTelephony — b24_telephony_statistics

Anything still not typed here is reachable through b24_call (e.g. mail, open-lines, sale basket writes, admin/app-placement methods).

Retrospective-app integration

This server has no knowledge of any downstream app. An agent connects to both this server and your app's MCP, reads Bitrix here, and relays into the app's contract. Field names from b24_tasks_list / b24_calendar_event_list map directly onto PushSprintTask / PushCalendarEvent, so the mapping is trivial — but that translation lives in the agent, not here.

Documentation

docs/USAGE.md — how to drive the tools: auth, filters, pagination, batch, errors, recipes.
ARCHITECTURE.md — components, call flow, deployment; diagrams in docs/diagrams/.
ROADMAP.md — status, history, and out-of-scope boundaries.

Development

uv sync # install runtime + dev deps
uv run pytest -q # offline unit tests (no portal needed)
uv run python scripts/smoke.py "<webhook>"# live read-only access map (run from a network with portal access)

Verification scripts

Each one exits non-zero when a check fails, so they can be chained in CI. Those marked offline need no portal; the rest need a reachable webhook.

Script	What it proves	Needs
`scripts/startup_check.py`	The server boots on both transports and registers every tool	offline
`scripts/leak_check.py`	The sanitizer strips webhooks/tokens from output and from httpx logs	offline
`scripts/git_secret_scan.py`	No secret is present in tracked files or anywhere in git history	offline
`scripts/events_tools_check.py`	poll → ack → history → stats against a seeded store	offline
`scripts/coverage_check.py`	Requirement R-1: catalogue + scope diagnosis reach the whole API	portal
`scripts/poller_check.py`	`b24_changes_since` cursors advance and do not skip rows	portal
`scripts/pull_channel_check.py`	Push & Pull channel subscribes and receives	portal
`scripts/receiver_e2e_check.py`	Outgoing-webhook receiver end to end, including TLS	portal
`scripts/telegram_check.py`	Filter DSL routes the right events	offline
`scripts/telegram_live_check.py`	The bot and chat really accept a message	Telegram
`scripts/smoke.py`	Live read-only access map across every domain	portal
`scripts/build_catalog.py`	Regenerates `data/catalog.json` from the official docs	docs checkout

Probes (diagnostics, no pass/fail verdict): pull_probe.py, probe_listener.py, tg_conn_probe.py.

Diagrams are regenerated with java -jar plantuml.jar -tpng docs/diagrams/*.puml.

Notes on limits

fetch_all=true is capped by BITRIX_MAX_PAGES (default 40 pages ≈ 2000 records) and reports truncated: true when it hits the cap — it never silently stops short.
The read-only guard classifies writes by method verb; typed write tools are always classified correctly. b24_call/b24_batch use the heuristic.

Licence

MIT — see LICENSE.

Security

Found a vulnerability? Please report it privately, not in a public issue — see SECURITY.md. The webhook URL this server uses is a bearer credential for the whole portal.

Support author

BTC: bc1q3frrup5neh7nhfg944etu2agd4j9u0vg3jyee6

ETH(Arbitrum): 0x43B349d8Cea83215D707EBa3bc35e9917f746b0a

TRX: THSzvy49KNeqRjXsGkurh2A5G4avV4RgN4

XRP: rLWZjS3DMupC4ZdXCX3BVYn4dEtC3iNhgy

SOL: 3xwfybxJ6Tz5t6pjBBkL5yYQCZo6wfbv932UNA4ThdP8

ADA: addr1q926ys75jp5wn2pv32a3t8r8pdhr7w02v0t9j4a8pmg0ruww5rlkctu4lnz2hfcwa5qfn3zhsd0s23r22uqwzx9gu6cq5c4e76

TON: UQC4qlAOD9Nly4K_66GJ_yCsSM3x2sB0vZ2GrBQbc--gZUui

DOGE: DTjNYmbtymzcjUiV4MsZY8MP4dM7MJ6qLC

XMR: 44qRqM6YtnxXUhkgCFqDDrKMPjWriu69FLBoop8Kwp7e1VQsBUJoVQ8JYQjfMV5C6uidTUgSSyoJ65mq8aYG2esZ1rrqfwt

bitrix-mcp

English · Русский

Universal, full-featured, portable MCP server for the Bitrix24 REST API. Read and write. Not tied to any one application — it's a generic Bitrix24 gateway that any MCP client or agent can mount (Claude Code, Claude Desktop, Cursor, Windsurf, Cline, or your own Python/Node agent).

Language: Python + the official MCP SDK (mcp.server.mcpserver, 2.x)
Transports:stdio (default, most portable/reliable) and Streamable HTTP (stateless JSON — no fragile long-lived SSE bridge)
Coverage: universal b24_call / b24_batch reach 100% of the REST API; a catalogue built from the official docs (1930 methods) tells the agent which method it needs and what parameters it takes; 99 typed tools cover the high-traffic domains with the tricky bits handled.
Portal events: three ways to receive them — pull channel (works behind NAT and VPN), outgoing-webhook receiver, poller — plus a history archive and Telegram forwarding: docs/EVENTS.md

Why this exists / what it fixes

Rebuilt from field notes on a previous wrapper. The bugs that motivated it are fixed by design, not patched around:

Old behavior	Fix here
`filter` silently ignored (`groups_list`, `users_list`), full-portal dumps → timeouts	Params sent as JSON POST body, so nested `filter`/`select`/`order` are parsed correctly by Bitrix. Real pagination with a page cap.
Access errors swallowed into a fake "0 results" (`read_pipelines` etc.)	Errors are never swallowed — a Bitrix `error`/`error_description` always surfaces with its `code` (e.g. `ACCESS_DENIED`).
`calendar_list` returned 0 without explicit `ownerId`	`owner_id`auto-resolves to the acting user.
Scrum kanban read from the wrong place	Correct flow baked in: active-sprint filter + `tasks.api.scrum.kanban.getStages` (`b24_scrum_board` does it in one call).
Fragile `mcp-remote` SSE session drops / hangs	Prefer stdio (no bridge) or stateless Streamable HTTP.
`department.get` has no server-side filter at all (a Bitrix API limitation, undocumented) — any `filter` was silently ignored and the whole department tree (95+ rows) came back regardless	`b24_department_get` filters client-side after a full fetch, so `filter`/`ID` genuinely narrow the result instead of quietly dumping everything.
Bitrix sometimes reports a failure as `{"error": "", "error_description": "Access denied."}` — an empty-string error code — which a naive truthiness check (`if data.get("error")`) misses, losing the code and message to a generic HTTP-status fallback	Checked by key presence, not truthiness — `code`/`message` always reflect what Bitrix actually said.
`calendar.event.add` / `.update` silently drop `attendees` unless `is_meeting` is also set — 200 OK, event created, nobody invited, no error anywhere	`is_meeting` is auto-set to `'Y'` whenever `attendees` is non-empty and not already specified.
Moving a task on a Scrum sprint board has no single API call, and every obvious candidate fails while reporting success: `tasks.task.update`'s `STAGE_ID` changes the field and writes a history entry everyone can see, but the card stays put; `kanban.addTask` only places a card that is off the board and answers `true` without doing anything for one already in a column; `task.stages.movetask` answers `false`.	`b24_scrum_task_move` takes the card off the board and puts it back at the target column (`kanban.deleteTask` → `kanban.addTask`) — verified by watching a real board, not by trusting the response. It also warns that `STAGE_ID` cannot verify the result: it read `0` while the card was visibly in the target column.

Install

If nothing is installed on the machine, take the portable archive (dist/bitrix-mcp-portable.zip, built by python scripts/build_portable.py). It carries its own Python and every library — no uv, no pip, no PyPI access. Unzip it and run the bundled launcher.

From source:

uv sync # create venv + install# or, as a tool on PATH:
uv tool install .# exposes the `bitrix-mcp` command

Configure

Set the default webhook (see .env.example):

export BITRIX_WEBHOOK_URL="https://your-portal.bitrix24.ru/rest/1/xxxxxxxx/"# optional:export BITRIX_READ_ONLY=1 # block all writes

The webhook comes from Bitrix: Profile → Webhooks → inbound webhook, format https://<portal>/rest/<user_id>/<token>/. The token is a credential — keep it out of source control (.env is gitignored).

Auth precedence per call:personal_webhook → webhook_url → X-B24-Webhook HTTP header → BITRIX_WEBHOOK_URL. Pass personal_webhook to act (and write) as a specific user.

Run

bitrix-mcp # stdio (default)
bitrix-mcp --http # Streamable HTTP on 127.0.0.1:8000/mcp
bitrix-mcp --http --host 0.0.0.0 --port 5015 # shared network service

Connect a client

Claude Code (stdio, recommended):

claude mcp add -s user bitrix24 -- uv run --directory C:/Scripts/BitrixMCP bitrix-mcp

Repo-shared .mcp.json (stdio):

{
"mcpServers": {
"bitrix24": {
"command": "uv",
"args": ["run", "--directory", "C:/Scripts/BitrixMCP", "bitrix-mcp"],
"env": { "BITRIX_WEBHOOK_URL": "https://your-portal.bitrix24.ru/rest/1/xxxx/" }
}
}
}

Claude Code (HTTP):

bitrix-mcp --http --port 5015 # then, on the client:
claude mcp add -s user --transport http bitrix24 http://HOST:5015/mcp

Claude Desktop (stdio) — %APPDATA%\Claude\claude_desktop_config.json:

{
"mcpServers": {
"bitrix24": {
"command": "uv",
"args": ["run", "--directory", "C:/Scripts/BitrixMCP", "bitrix-mcp"],
"env": { "BITRIX_WEBHOOK_URL": "https://your-portal.bitrix24.ru/rest/1/xxxx/" }
}
}
}

(For a remote HTTP instance, Desktop still needs the mcp-remote bridge; stdio above avoids it entirely.)

Tool catalog (99)

Universal — b24_call, b24_batch, b24_test_connection, b24_list_methodsCRM — b24_crm_list, b24_crm_get, b24_crm_fields, b24_crm_add, b24_crm_update, b24_crm_delete, b24_crm_timeline_comment_add, b24_crm_timeline_comment_list, b24_crm_category_list (pipelines), b24_crm_status_list (stages/dictionaries), b24_crm_activity_list, b24_crm_activity_add, b24_crm_activity_delete, b24_crm_productrows_get, b24_crm_productrows_set, b24_crm_currency_list, b24_crm_requisite_list, b24_crm_deal_contacts_get, b24_crm_deal_contacts_set (classic entities and SPA via entity_type_id) Tasks — b24_tasks_list, b24_task_get, b24_task_add, b24_task_update, b24_task_complete, b24_task_delete, b24_task_comments_list, b24_task_comment_add, b24_task_stages_get, b24_task_checklist_list, b24_task_checklist_add, b24_task_elapsed_add, b24_task_result_listScrum — b24_scrum_sprint_list, b24_scrum_kanban_stages, b24_scrum_board, b24_scrum_task_moveCalendar — b24_calendar_event_list, b24_calendar_section_list, b24_calendar_event_add, b24_calendar_event_update, b24_calendar_event_deleteDisk — b24_disk_storage_list, b24_disk_folder_items, b24_disk_file_get, b24_disk_file_content (server-side download → base64), b24_disk_folder_add, b24_disk_file_upload, b24_disk_file_deleteUsers/structure — b24_user_get, b24_user_search, b24_user_current, b24_department_getGroups (workgroups) — b24_group_list, b24_group_users, b24_group_create, b24_group_update, b24_group_deleteMessaging — b24_im_recent, b24_im_dialog_messages, b24_im_message_add, b24_im_notify_personal, b24_im_user_get, b24_im_chat_create, b24_im_chat_user_add, b24_feed_post_addLists (universal lists) — b24_lists_get, b24_lists_element_list, b24_lists_element_add, b24_lists_element_update, b24_lists_element_deleteCatalog / products — b24_catalog_list, b24_catalog_section_list, b24_catalog_product_list, b24_catalog_product_get, b24_catalog_product_add, b24_catalog_product_update, b24_crm_product_listSale (orders) — b24_sale_order_list, b24_sale_order_getDocuments — b24_documentgenerator_templates, b24_documentgenerator_addBizproc — b24_bizproc_template_list, b24_bizproc_startTelephony — b24_telephony_statistics

Anything still not typed here is reachable through b24_call (e.g. mail, open-lines, sale basket writes, admin/app-placement methods).

Retrospective-app integration

This server has no knowledge of any downstream app. An agent connects to both this server and your app's MCP, reads Bitrix here, and relays into the app's contract. Field names from b24_tasks_list / b24_calendar_event_list map directly onto PushSprintTask / PushCalendarEvent, so the mapping is trivial — but that translation lives in the agent, not here.

Documentation

docs/USAGE.md — how to drive the tools: auth, filters, pagination, batch, errors, recipes.
ARCHITECTURE.md — components, call flow, deployment; diagrams in docs/diagrams/.
ROADMAP.md — status, history, and out-of-scope boundaries.

Development

uv sync # install runtime + dev deps
uv run pytest -q # offline unit tests (no portal needed)
uv run python scripts/smoke.py "<webhook>"# live read-only access map (run from a network with portal access)

Verification scripts

Each one exits non-zero when a check fails, so they can be chained in CI. Those marked offline need no portal; the rest need a reachable webhook.

Script	What it proves	Needs
`scripts/startup_check.py`	The server boots on both transports and registers every tool	offline
`scripts/leak_check.py`	The sanitizer strips webhooks/tokens from output and from httpx logs	offline
`scripts/git_secret_scan.py`	No secret is present in tracked files or anywhere in git history	offline
`scripts/events_tools_check.py`	poll → ack → history → stats against a seeded store	offline
`scripts/coverage_check.py`	Requirement R-1: catalogue + scope diagnosis reach the whole API	portal
`scripts/poller_check.py`	`b24_changes_since` cursors advance and do not skip rows	portal
`scripts/pull_channel_check.py`	Push & Pull channel subscribes and receives	portal
`scripts/receiver_e2e_check.py`	Outgoing-webhook receiver end to end, including TLS	portal
`scripts/telegram_check.py`	Filter DSL routes the right events	offline
`scripts/telegram_live_check.py`	The bot and chat really accept a message	Telegram
`scripts/smoke.py`	Live read-only access map across every domain	portal
`scripts/build_catalog.py`	Regenerates `data/catalog.json` from the official docs	docs checkout

Probes (diagnostics, no pass/fail verdict): pull_probe.py, probe_listener.py, tg_conn_probe.py.

Diagrams are regenerated with java -jar plantuml.jar -tpng docs/diagrams/*.puml.

Notes on limits

fetch_all=true is capped by BITRIX_MAX_PAGES (default 40 pages ≈ 2000 records) and reports truncated: true when it hits the cap — it never silently stops short.
The read-only guard classifies writes by method verb; typed write tools are always classified correctly. b24_call/b24_batch use the heuristic.

Licence

MIT — see LICENSE.

Security

Found a vulnerability? Please report it privately, not in a public issue — see SECURITY.md. The webhook URL this server uses is a bearer credential for the whole portal.

Support author

BTC: bc1q3frrup5neh7nhfg944etu2agd4j9u0vg3jyee6

ETH(Arbitrum): 0x43B349d8Cea83215D707EBa3bc35e9917f746b0a

TRX: THSzvy49KNeqRjXsGkurh2A5G4avV4RgN4

XRP: rLWZjS3DMupC4ZdXCX3BVYn4dEtC3iNhgy

SOL: 3xwfybxJ6Tz5t6pjBBkL5yYQCZo6wfbv932UNA4ThdP8

ADA: addr1q926ys75jp5wn2pv32a3t8r8pdhr7w02v0t9j4a8pmg0ruww5rlkctu4lnz2hfcwa5qfn3zhsd0s23r22uqwzx9gu6cq5c4e76

TON: UQC4qlAOD9Nly4K_66GJ_yCsSM3x2sB0vZ2GrBQbc--gZUui

DOGE: DTjNYmbtymzcjUiV4MsZY8MP4dM7MJ6qLC

XMR: 44qRqM6YtnxXUhkgCFqDDrKMPjWriu69FLBoop8Kwp7e1VQsBUJoVQ8JYQjfMV5C6uidTUgSSyoJ65mq8aYG2esZ1rrqfwt

bitrix-mcp

English · Русский

Universal, full-featured, portable MCP server for the Bitrix24 REST API. Read and write. Not tied to any one application — it's a generic Bitrix24 gateway that any MCP client or agent can mount (Claude Code, Claude Desktop, Cursor, Windsurf, Cline, or your own Python/Node agent).

Language: Python + the official MCP SDK (mcp.server.mcpserver, 2.x)
Transports:stdio (default, most portable/reliable) and Streamable HTTP (stateless JSON — no fragile long-lived SSE bridge)
Coverage: universal b24_call / b24_batch reach 100% of the REST API; a catalogue built from the official docs (1930 methods) tells the agent which method it needs and what parameters it takes; 99 typed tools cover the high-traffic domains with the tricky bits handled.
Portal events: three ways to receive them — pull channel (works behind NAT and VPN), outgoing-webhook receiver, poller — plus a history archive and Telegram forwarding: docs/EVENTS.md

Why this exists / what it fixes

Rebuilt from field notes on a previous wrapper. The bugs that motivated it are fixed by design, not patched around:

Old behavior	Fix here
`filter` silently ignored (`groups_list`, `users_list`), full-portal dumps → timeouts	Params sent as JSON POST body, so nested `filter`/`select`/`order` are parsed correctly by Bitrix. Real pagination with a page cap.
Access errors swallowed into a fake "0 results" (`read_pipelines` etc.)	Errors are never swallowed — a Bitrix `error`/`error_description` always surfaces with its `code` (e.g. `ACCESS_DENIED`).
`calendar_list` returned 0 without explicit `ownerId`	`owner_id`auto-resolves to the acting user.
Scrum kanban read from the wrong place	Correct flow baked in: active-sprint filter + `tasks.api.scrum.kanban.getStages` (`b24_scrum_board` does it in one call).
Fragile `mcp-remote` SSE session drops / hangs	Prefer stdio (no bridge) or stateless Streamable HTTP.
`department.get` has no server-side filter at all (a Bitrix API limitation, undocumented) — any `filter` was silently ignored and the whole department tree (95+ rows) came back regardless	`b24_department_get` filters client-side after a full fetch, so `filter`/`ID` genuinely narrow the result instead of quietly dumping everything.
Bitrix sometimes reports a failure as `{"error": "", "error_description": "Access denied."}` — an empty-string error code — which a naive truthiness check (`if data.get("error")`) misses, losing the code and message to a generic HTTP-status fallback	Checked by key presence, not truthiness — `code`/`message` always reflect what Bitrix actually said.
`calendar.event.add` / `.update` silently drop `attendees` unless `is_meeting` is also set — 200 OK, event created, nobody invited, no error anywhere	`is_meeting` is auto-set to `'Y'` whenever `attendees` is non-empty and not already specified.
Moving a task on a Scrum sprint board has no single API call, and every obvious candidate fails while reporting success: `tasks.task.update`'s `STAGE_ID` changes the field and writes a history entry everyone can see, but the card stays put; `kanban.addTask` only places a card that is off the board and answers `true` without doing anything for one already in a column; `task.stages.movetask` answers `false`.	`b24_scrum_task_move` takes the card off the board and puts it back at the target column (`kanban.deleteTask` → `kanban.addTask`) — verified by watching a real board, not by trusting the response. It also warns that `STAGE_ID` cannot verify the result: it read `0` while the card was visibly in the target column.

Install

If nothing is installed on the machine, take the portable archive (dist/bitrix-mcp-portable.zip, built by python scripts/build_portable.py). It carries its own Python and every library — no uv, no pip, no PyPI access. Unzip it and run the bundled launcher.

From source:

uv sync # create venv + install# or, as a tool on PATH:
uv tool install .# exposes the `bitrix-mcp` command

Configure

Set the default webhook (see .env.example):

export BITRIX_WEBHOOK_URL="https://your-portal.bitrix24.ru/rest/1/xxxxxxxx/"# optional:export BITRIX_READ_ONLY=1 # block all writes

The webhook comes from Bitrix: Profile → Webhooks → inbound webhook, format https://<portal>/rest/<user_id>/<token>/. The token is a credential — keep it out of source control (.env is gitignored).

Auth precedence per call:personal_webhook → webhook_url → X-B24-Webhook HTTP header → BITRIX_WEBHOOK_URL. Pass personal_webhook to act (and write) as a specific user.

Run

bitrix-mcp # stdio (default)
bitrix-mcp --http # Streamable HTTP on 127.0.0.1:8000/mcp
bitrix-mcp --http --host 0.0.0.0 --port 5015 # shared network service

Connect a client

Claude Code (stdio, recommended):

claude mcp add -s user bitrix24 -- uv run --directory C:/Scripts/BitrixMCP bitrix-mcp

Repo-shared .mcp.json (stdio):

{
"mcpServers": {
"bitrix24": {
"command": "uv",
"args": ["run", "--directory", "C:/Scripts/BitrixMCP", "bitrix-mcp"],
"env": { "BITRIX_WEBHOOK_URL": "https://your-portal.bitrix24.ru/rest/1/xxxx/" }
}
}
}

Claude Code (HTTP):

bitrix-mcp --http --port 5015 # then, on the client:
claude mcp add -s user --transport http bitrix24 http://HOST:5015/mcp

Claude Desktop (stdio) — %APPDATA%\Claude\claude_desktop_config.json:

{
"mcpServers": {
"bitrix24": {
"command": "uv",
"args": ["run", "--directory", "C:/Scripts/BitrixMCP", "bitrix-mcp"],
"env": { "BITRIX_WEBHOOK_URL": "https://your-portal.bitrix24.ru/rest/1/xxxx/" }
}
}
}

(For a remote HTTP instance, Desktop still needs the mcp-remote bridge; stdio above avoids it entirely.)

Tool catalog (99)

Universal — b24_call, b24_batch, b24_test_connection, b24_list_methodsCRM — b24_crm_list, b24_crm_get, b24_crm_fields, b24_crm_add, b24_crm_update, b24_crm_delete, b24_crm_timeline_comment_add, b24_crm_timeline_comment_list, b24_crm_category_list (pipelines), b24_crm_status_list (stages/dictionaries), b24_crm_activity_list, b24_crm_activity_add, b24_crm_activity_delete, b24_crm_productrows_get, b24_crm_productrows_set, b24_crm_currency_list, b24_crm_requisite_list, b24_crm_deal_contacts_get, b24_crm_deal_contacts_set (classic entities and SPA via entity_type_id) Tasks — b24_tasks_list, b24_task_get, b24_task_add, b24_task_update, b24_task_complete, b24_task_delete, b24_task_comments_list, b24_task_comment_add, b24_task_stages_get, b24_task_checklist_list, b24_task_checklist_add, b24_task_elapsed_add, b24_task_result_listScrum — b24_scrum_sprint_list, b24_scrum_kanban_stages, b24_scrum_board, b24_scrum_task_moveCalendar — b24_calendar_event_list, b24_calendar_section_list, b24_calendar_event_add, b24_calendar_event_update, b24_calendar_event_deleteDisk — b24_disk_storage_list, b24_disk_folder_items, b24_disk_file_get, b24_disk_file_content (server-side download → base64), b24_disk_folder_add, b24_disk_file_upload, b24_disk_file_deleteUsers/structure — b24_user_get, b24_user_search, b24_user_current, b24_department_getGroups (workgroups) — b24_group_list, b24_group_users, b24_group_create, b24_group_update, b24_group_deleteMessaging — b24_im_recent, b24_im_dialog_messages, b24_im_message_add, b24_im_notify_personal, b24_im_user_get, b24_im_chat_create, b24_im_chat_user_add, b24_feed_post_addLists (universal lists) — b24_lists_get, b24_lists_element_list, b24_lists_element_add, b24_lists_element_update, b24_lists_element_deleteCatalog / products — b24_catalog_list, b24_catalog_section_list, b24_catalog_product_list, b24_catalog_product_get, b24_catalog_product_add, b24_catalog_product_update, b24_crm_product_listSale (orders) — b24_sale_order_list, b24_sale_order_getDocuments — b24_documentgenerator_templates, b24_documentgenerator_addBizproc — b24_bizproc_template_list, b24_bizproc_startTelephony — b24_telephony_statistics

Anything still not typed here is reachable through b24_call (e.g. mail, open-lines, sale basket writes, admin/app-placement methods).

Retrospective-app integration

This server has no knowledge of any downstream app. An agent connects to both this server and your app's MCP, reads Bitrix here, and relays into the app's contract. Field names from b24_tasks_list / b24_calendar_event_list map directly onto PushSprintTask / PushCalendarEvent, so the mapping is trivial — but that translation lives in the agent, not here.

Documentation

docs/USAGE.md — how to drive the tools: auth, filters, pagination, batch, errors, recipes.
ARCHITECTURE.md — components, call flow, deployment; diagrams in docs/diagrams/.
ROADMAP.md — status, history, and out-of-scope boundaries.

Development

uv sync # install runtime + dev deps
uv run pytest -q # offline unit tests (no portal needed)
uv run python scripts/smoke.py "<webhook>"# live read-only access map (run from a network with portal access)

Verification scripts

Each one exits non-zero when a check fails, so they can be chained in CI. Those marked offline need no portal; the rest need a reachable webhook.

Script	What it proves	Needs
`scripts/startup_check.py`	The server boots on both transports and registers every tool	offline
`scripts/leak_check.py`	The sanitizer strips webhooks/tokens from output and from httpx logs	offline
`scripts/git_secret_scan.py`	No secret is present in tracked files or anywhere in git history	offline
`scripts/events_tools_check.py`	poll → ack → history → stats against a seeded store	offline
`scripts/coverage_check.py`	Requirement R-1: catalogue + scope diagnosis reach the whole API	portal
`scripts/poller_check.py`	`b24_changes_since` cursors advance and do not skip rows	portal
`scripts/pull_channel_check.py`	Push & Pull channel subscribes and receives	portal
`scripts/receiver_e2e_check.py`	Outgoing-webhook receiver end to end, including TLS	portal
`scripts/telegram_check.py`	Filter DSL routes the right events	offline
`scripts/telegram_live_check.py`	The bot and chat really accept a message	Telegram
`scripts/smoke.py`	Live read-only access map across every domain	portal
`scripts/build_catalog.py`	Regenerates `data/catalog.json` from the official docs	docs checkout

Probes (diagnostics, no pass/fail verdict): pull_probe.py, probe_listener.py, tg_conn_probe.py.

Diagrams are regenerated with java -jar plantuml.jar -tpng docs/diagrams/*.puml.

Notes on limits

fetch_all=true is capped by BITRIX_MAX_PAGES (default 40 pages ≈ 2000 records) and reports truncated: true when it hits the cap — it never silently stops short.
The read-only guard classifies writes by method verb; typed write tools are always classified correctly. b24_call/b24_batch use the heuristic.

Licence

MIT — see LICENSE.

Security

Found a vulnerability? Please report it privately, not in a public issue — see SECURITY.md. The webhook URL this server uses is a bearer credential for the whole portal.

Support author

BTC: bc1q3frrup5neh7nhfg944etu2agd4j9u0vg3jyee6

ETH(Arbitrum): 0x43B349d8Cea83215D707EBa3bc35e9917f746b0a

TRX: THSzvy49KNeqRjXsGkurh2A5G4avV4RgN4

XRP: rLWZjS3DMupC4ZdXCX3BVYn4dEtC3iNhgy

SOL: 3xwfybxJ6Tz5t6pjBBkL5yYQCZo6wfbv932UNA4ThdP8

ADA: addr1q926ys75jp5wn2pv32a3t8r8pdhr7w02v0t9j4a8pmg0ruww5rlkctu4lnz2hfcwa5qfn3zhsd0s23r22uqwzx9gu6cq5c4e76

TON: UQC4qlAOD9Nly4K_66GJ_yCsSM3x2sB0vZ2GrBQbc--gZUui

DOGE: DTjNYmbtymzcjUiV4MsZY8MP4dM7MJ6qLC

XMR: 44qRqM6YtnxXUhkgCFqDDrKMPjWriu69FLBoop8Kwp7e1VQsBUJoVQ8JYQjfMV5C6uidTUgSSyoJ65mq8aYG2esZ1rrqfwt

bitrix-mcp

English · Русский

Universal, full-featured, portable MCP server for the Bitrix24 REST API. Read and write. Not tied to any one application — it's a generic Bitrix24 gateway that any MCP client or agent can mount (Claude Code, Claude Desktop, Cursor, Windsurf, Cline, or your own Python/Node agent).

Language: Python + the official MCP SDK (mcp.server.mcpserver, 2.x)
Transports:stdio (default, most portable/reliable) and Streamable HTTP (stateless JSON — no fragile long-lived SSE bridge)
Coverage: universal b24_call / b24_batch reach 100% of the REST API; a catalogue built from the official docs (1930 methods) tells the agent which method it needs and what parameters it takes; 99 typed tools cover the high-traffic domains with the tricky bits handled.
Portal events: three ways to receive them — pull channel (works behind NAT and VPN), outgoing-webhook receiver, poller — plus a history archive and Telegram forwarding: docs/EVENTS.md

Why this exists / what it fixes

Rebuilt from field notes on a previous wrapper. The bugs that motivated it are fixed by design, not patched around:

Old behavior	Fix here
`filter` silently ignored (`groups_list`, `users_list`), full-portal dumps → timeouts	Params sent as JSON POST body, so nested `filter`/`select`/`order` are parsed correctly by Bitrix. Real pagination with a page cap.
Access errors swallowed into a fake "0 results" (`read_pipelines` etc.)	Errors are never swallowed — a Bitrix `error`/`error_description` always surfaces with its `code` (e.g. `ACCESS_DENIED`).
`calendar_list` returned 0 without explicit `ownerId`	`owner_id`auto-resolves to the acting user.
Scrum kanban read from the wrong place	Correct flow baked in: active-sprint filter + `tasks.api.scrum.kanban.getStages` (`b24_scrum_board` does it in one call).
Fragile `mcp-remote` SSE session drops / hangs	Prefer stdio (no bridge) or stateless Streamable HTTP.
`department.get` has no server-side filter at all (a Bitrix API limitation, undocumented) — any `filter` was silently ignored and the whole department tree (95+ rows) came back regardless	`b24_department_get` filters client-side after a full fetch, so `filter`/`ID` genuinely narrow the result instead of quietly dumping everything.
Bitrix sometimes reports a failure as `{"error": "", "error_description": "Access denied."}` — an empty-string error code — which a naive truthiness check (`if data.get("error")`) misses, losing the code and message to a generic HTTP-status fallback	Checked by key presence, not truthiness — `code`/`message` always reflect what Bitrix actually said.
`calendar.event.add` / `.update` silently drop `attendees` unless `is_meeting` is also set — 200 OK, event created, nobody invited, no error anywhere	`is_meeting` is auto-set to `'Y'` whenever `attendees` is non-empty and not already specified.
Moving a task on a Scrum sprint board has no single API call, and every obvious candidate fails while reporting success: `tasks.task.update`'s `STAGE_ID` changes the field and writes a history entry everyone can see, but the card stays put; `kanban.addTask` only places a card that is off the board and answers `true` without doing anything for one already in a column; `task.stages.movetask` answers `false`.	`b24_scrum_task_move` takes the card off the board and puts it back at the target column (`kanban.deleteTask` → `kanban.addTask`) — verified by watching a real board, not by trusting the response. It also warns that `STAGE_ID` cannot verify the result: it read `0` while the card was visibly in the target column.

Install

If nothing is installed on the machine, take the portable archive (dist/bitrix-mcp-portable.zip, built by python scripts/build_portable.py). It carries its own Python and every library — no uv, no pip, no PyPI access. Unzip it and run the bundled launcher.

From source:

uv sync # create venv + install# or, as a tool on PATH:
uv tool install .# exposes the `bitrix-mcp` command

Configure

Set the default webhook (see .env.example):

export BITRIX_WEBHOOK_URL="https://your-portal.bitrix24.ru/rest/1/xxxxxxxx/"# optional:export BITRIX_READ_ONLY=1 # block all writes

The webhook comes from Bitrix: Profile → Webhooks → inbound webhook, format https://<portal>/rest/<user_id>/<token>/. The token is a credential — keep it out of source control (.env is gitignored).

Auth precedence per call:personal_webhook → webhook_url → X-B24-Webhook HTTP header → BITRIX_WEBHOOK_URL. Pass personal_webhook to act (and write) as a specific user.

Run

bitrix-mcp # stdio (default)
bitrix-mcp --http # Streamable HTTP on 127.0.0.1:8000/mcp
bitrix-mcp --http --host 0.0.0.0 --port 5015 # shared network service

Connect a client

Claude Code (stdio, recommended):

claude mcp add -s user bitrix24 -- uv run --directory C:/Scripts/BitrixMCP bitrix-mcp

Repo-shared .mcp.json (stdio):

{
"mcpServers": {
"bitrix24": {
"command": "uv",
"args": ["run", "--directory", "C:/Scripts/BitrixMCP", "bitrix-mcp"],
"env": { "BITRIX_WEBHOOK_URL": "https://your-portal.bitrix24.ru/rest/1/xxxx/" }
}
}
}

Claude Code (HTTP):

bitrix-mcp --http --port 5015 # then, on the client:
claude mcp add -s user --transport http bitrix24 http://HOST:5015/mcp

Claude Desktop (stdio) — %APPDATA%\Claude\claude_desktop_config.json:

{
"mcpServers": {
"bitrix24": {
"command": "uv",
"args": ["run", "--directory", "C:/Scripts/BitrixMCP", "bitrix-mcp"],
"env": { "BITRIX_WEBHOOK_URL": "https://your-portal.bitrix24.ru/rest/1/xxxx/" }
}
}
}

(For a remote HTTP instance, Desktop still needs the mcp-remote bridge; stdio above avoids it entirely.)

Tool catalog (99)

Universal — b24_call, b24_batch, b24_test_connection, b24_list_methodsCRM — b24_crm_list, b24_crm_get, b24_crm_fields, b24_crm_add, b24_crm_update, b24_crm_delete, b24_crm_timeline_comment_add, b24_crm_timeline_comment_list, b24_crm_category_list (pipelines), b24_crm_status_list (stages/dictionaries), b24_crm_activity_list, b24_crm_activity_add, b24_crm_activity_delete, b24_crm_productrows_get, b24_crm_productrows_set, b24_crm_currency_list, b24_crm_requisite_list, b24_crm_deal_contacts_get, b24_crm_deal_contacts_set (classic entities and SPA via entity_type_id) Tasks — b24_tasks_list, b24_task_get, b24_task_add, b24_task_update, b24_task_complete, b24_task_delete, b24_task_comments_list, b24_task_comment_add, b24_task_stages_get, b24_task_checklist_list, b24_task_checklist_add, b24_task_elapsed_add, b24_task_result_listScrum — b24_scrum_sprint_list, b24_scrum_kanban_stages, b24_scrum_board, b24_scrum_task_moveCalendar — b24_calendar_event_list, b24_calendar_section_list, b24_calendar_event_add, b24_calendar_event_update, b24_calendar_event_deleteDisk — b24_disk_storage_list, b24_disk_folder_items, b24_disk_file_get, b24_disk_file_content (server-side download → base64), b24_disk_folder_add, b24_disk_file_upload, b24_disk_file_deleteUsers/structure — b24_user_get, b24_user_search, b24_user_current, b24_department_getGroups (workgroups) — b24_group_list, b24_group_users, b24_group_create, b24_group_update, b24_group_deleteMessaging — b24_im_recent, b24_im_dialog_messages, b24_im_message_add, b24_im_notify_personal, b24_im_user_get, b24_im_chat_create, b24_im_chat_user_add, b24_feed_post_addLists (universal lists) — b24_lists_get, b24_lists_element_list, b24_lists_element_add, b24_lists_element_update, b24_lists_element_deleteCatalog / products — b24_catalog_list, b24_catalog_section_list, b24_catalog_product_list, b24_catalog_product_get, b24_catalog_product_add, b24_catalog_product_update, b24_crm_product_listSale (orders) — b24_sale_order_list, b24_sale_order_getDocuments — b24_documentgenerator_templates, b24_documentgenerator_addBizproc — b24_bizproc_template_list, b24_bizproc_startTelephony — b24_telephony_statistics

Anything still not typed here is reachable through b24_call (e.g. mail, open-lines, sale basket writes, admin/app-placement methods).

Retrospective-app integration

This server has no knowledge of any downstream app. An agent connects to both this server and your app's MCP, reads Bitrix here, and relays into the app's contract. Field names from b24_tasks_list / b24_calendar_event_list map directly onto PushSprintTask / PushCalendarEvent, so the mapping is trivial — but that translation lives in the agent, not here.

Documentation

docs/USAGE.md — how to drive the tools: auth, filters, pagination, batch, errors, recipes.
ARCHITECTURE.md — components, call flow, deployment; diagrams in docs/diagrams/.
ROADMAP.md — status, history, and out-of-scope boundaries.

Development

uv sync # install runtime + dev deps
uv run pytest -q # offline unit tests (no portal needed)
uv run python scripts/smoke.py "<webhook>"# live read-only access map (run from a network with portal access)

Verification scripts

Each one exits non-zero when a check fails, so they can be chained in CI. Those marked offline need no portal; the rest need a reachable webhook.

Script	What it proves	Needs
`scripts/startup_check.py`	The server boots on both transports and registers every tool	offline
`scripts/leak_check.py`	The sanitizer strips webhooks/tokens from output and from httpx logs	offline
`scripts/git_secret_scan.py`	No secret is present in tracked files or anywhere in git history	offline
`scripts/events_tools_check.py`	poll → ack → history → stats against a seeded store	offline
`scripts/coverage_check.py`	Requirement R-1: catalogue + scope diagnosis reach the whole API	portal
`scripts/poller_check.py`	`b24_changes_since` cursors advance and do not skip rows	portal
`scripts/pull_channel_check.py`	Push & Pull channel subscribes and receives	portal
`scripts/receiver_e2e_check.py`	Outgoing-webhook receiver end to end, including TLS	portal
`scripts/telegram_check.py`	Filter DSL routes the right events	offline
`scripts/telegram_live_check.py`	The bot and chat really accept a message	Telegram
`scripts/smoke.py`	Live read-only access map across every domain	portal
`scripts/build_catalog.py`	Regenerates `data/catalog.json` from the official docs	docs checkout

Probes (diagnostics, no pass/fail verdict): pull_probe.py, probe_listener.py, tg_conn_probe.py.

Diagrams are regenerated with java -jar plantuml.jar -tpng docs/diagrams/*.puml.

Notes on limits

fetch_all=true is capped by BITRIX_MAX_PAGES (default 40 pages ≈ 2000 records) and reports truncated: true when it hits the cap — it never silently stops short.
The read-only guard classifies writes by method verb; typed write tools are always classified correctly. b24_call/b24_batch use the heuristic.

Licence

MIT — see LICENSE.

Security

Found a vulnerability? Please report it privately, not in a public issue — see SECURITY.md. The webhook URL this server uses is a bearer credential for the whole portal.

Support author

BTC: bc1q3frrup5neh7nhfg944etu2agd4j9u0vg3jyee6

ETH(Arbitrum): 0x43B349d8Cea83215D707EBa3bc35e9917f746b0a

TRX: THSzvy49KNeqRjXsGkurh2A5G4avV4RgN4

XRP: rLWZjS3DMupC4ZdXCX3BVYn4dEtC3iNhgy

SOL: 3xwfybxJ6Tz5t6pjBBkL5yYQCZo6wfbv932UNA4ThdP8

ADA: addr1q926ys75jp5wn2pv32a3t8r8pdhr7w02v0t9j4a8pmg0ruww5rlkctu4lnz2hfcwa5qfn3zhsd0s23r22uqwzx9gu6cq5c4e76

TON: UQC4qlAOD9Nly4K_66GJ_yCsSM3x2sB0vZ2GrBQbc--gZUui

DOGE: DTjNYmbtymzcjUiV4MsZY8MP4dM7MJ6qLC

XMR: 44qRqM6YtnxXUhkgCFqDDrKMPjWriu69FLBoop8Kwp7e1VQsBUJoVQ8JYQjfMV5C6uidTUgSSyoJ65mq8aYG2esZ1rrqfwt

Name		Name	Last commit message	Last commit date
docs		docs
scripts		scripts
src/bitrix_mcp		src/bitrix_mcp
tests		tests
.env.example		.env.example
.gitattributes		.gitattributes
.gitignore		.gitignore
.python-version		.python-version
ARCHITECTURE.md		ARCHITECTURE.md
ARCHITECTURE.ru.md		ARCHITECTURE.ru.md
LICENSE		LICENSE
README.md		README.md
README.ru.md		README.ru.md
REQUIREMENTS.md		REQUIREMENTS.md
REQUIREMENTS.ru.md		REQUIREMENTS.ru.md
ROADMAP.md		ROADMAP.md
ROADMAP.ru.md		ROADMAP.ru.md
SECURITY.md		SECURITY.md
donate-qr.png		donate-qr.png
pyproject.toml		pyproject.toml
uv.lock		uv.lock

Name		Name	Last commit message	Last commit date
docs		docs
scripts		scripts
src/bitrix_mcp		src/bitrix_mcp
tests		tests
.env.example		.env.example
.gitattributes		.gitattributes
.gitignore		.gitignore
.python-version		.python-version
ARCHITECTURE.md		ARCHITECTURE.md
ARCHITECTURE.ru.md		ARCHITECTURE.ru.md
LICENSE		LICENSE
README.md		README.md
README.ru.md		README.ru.md
REQUIREMENTS.md		REQUIREMENTS.md
REQUIREMENTS.ru.md		REQUIREMENTS.ru.md
ROADMAP.md		ROADMAP.md
ROADMAP.ru.md		ROADMAP.ru.md
SECURITY.md		SECURITY.md
donate-qr.png		donate-qr.png
pyproject.toml		pyproject.toml
uv.lock		uv.lock

Name		Name	Last commit message	Last commit date
docs		docs
scripts		scripts
src/bitrix_mcp		src/bitrix_mcp
tests		tests
.env.example		.env.example
.gitattributes		.gitattributes
.gitignore		.gitignore
.python-version		.python-version
ARCHITECTURE.md		ARCHITECTURE.md
ARCHITECTURE.ru.md		ARCHITECTURE.ru.md
LICENSE		LICENSE
README.md		README.md
README.ru.md		README.ru.md
REQUIREMENTS.md		REQUIREMENTS.md
REQUIREMENTS.ru.md		REQUIREMENTS.ru.md
ROADMAP.md		ROADMAP.md
ROADMAP.ru.md		ROADMAP.ru.md
SECURITY.md		SECURITY.md
donate-qr.png		donate-qr.png
pyproject.toml		pyproject.toml
uv.lock		uv.lock

Name		Name	Last commit message	Last commit date
docs		docs
scripts		scripts
src/bitrix_mcp		src/bitrix_mcp
tests		tests
.env.example		.env.example
.gitattributes		.gitattributes
.gitignore		.gitignore
.python-version		.python-version
ARCHITECTURE.md		ARCHITECTURE.md
ARCHITECTURE.ru.md		ARCHITECTURE.ru.md
LICENSE		LICENSE
README.md		README.md
README.ru.md		README.ru.md
REQUIREMENTS.md		REQUIREMENTS.md
REQUIREMENTS.ru.md		REQUIREMENTS.ru.md
ROADMAP.md		ROADMAP.md
ROADMAP.ru.md		ROADMAP.ru.md
SECURITY.md		SECURITY.md
donate-qr.png		donate-qr.png
pyproject.toml		pyproject.toml
uv.lock		uv.lock

Name		Name	Last commit message	Last commit date
docs		docs
scripts		scripts
src/bitrix_mcp		src/bitrix_mcp
tests		tests
.env.example		.env.example
.gitattributes		.gitattributes
.gitignore		.gitignore
.python-version		.python-version
ARCHITECTURE.md		ARCHITECTURE.md
ARCHITECTURE.ru.md		ARCHITECTURE.ru.md
LICENSE		LICENSE
README.md		README.md
README.ru.md		README.ru.md
REQUIREMENTS.md		REQUIREMENTS.md
REQUIREMENTS.ru.md		REQUIREMENTS.ru.md
ROADMAP.md		ROADMAP.md
ROADMAP.ru.md		ROADMAP.ru.md
SECURITY.md		SECURITY.md
donate-qr.png		donate-qr.png
pyproject.toml		pyproject.toml
uv.lock		uv.lock

Latest commit

History

Folders and files

Repository files navigation

bitrix-mcp

Why this exists / what it fixes

Install

Configure

Run

Connect a client

Tool catalog (99)

Retrospective-app integration

Documentation

Development

Verification scripts

Notes on limits

Licence

Security

Support author

About

Topics

Resources

Security policy

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages

Latest commit

History

Folders and files

Repository files navigation

bitrix-mcp

Why this exists / what it fixes

Install

Configure

Run

Connect a client

Tool catalog (99)

Retrospective-app integration

Documentation

Development

Verification scripts

Notes on limits

Licence

Security

Support author

About

Topics

Resources

Security policy

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages

Latest commit

History

Folders and files

Repository files navigation

bitrix-mcp

Why this exists / what it fixes

Install

Configure

Run

Connect a client

Tool catalog (99)

Retrospective-app integration

Documentation

Development

Verification scripts

Notes on limits

Licence

Security

Support author

About