mcp-bitrix24
An MCP server for Bitrix24 tasks, workgroups and users via an inbound webhook, built with clean TypeScript architecture
- 4 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Creates, closes and reopens tasks in a live Bitrix24 portal
- The webhook carries whatever rights were set when it was created; issue a separate webhook scoped to just the needed methods
A similar tool with a larger community: Bitrix24 MCP Server, 65 ★ on the repository
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/mcp-bitrix24Detects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Creates, closes and reopens tasks in a live Bitrix24 portal
- The webhook carries whatever rights were set when it was created; issue a separate webhook scoped to just the needed methods
This is third-party code. Review the repository files before installing.
What it does
The server connects to a Bitrix24 portal via an inbound webhook and lets the agent handle tasks: create, update, close, reopen and list them, plus read a task's change history. It also supports workgroups (create and list) and users (list, current user and available fields). For creating tasks with custom fields, a get_task_fields tool validates the fields object's keys against Bitrix24's real fields. The server runs stdio-only, validates tool inputs with zod, and its code is split into mcp, adapters, domain and infrastructure layers.
Who it is for. For Bitrix24 teams who want a narrow, predictable tool set for tasks and workgroups without extra CRM entities.
Good fit when
- You need to create and close Bitrix24 tasks from a chat with an agent
- You need the change history of a specific task
- You only need the tasks and groups module, not deals, leads or contacts
Not a fit when
- You need to work with deals, leads, contacts or other CRM entities: the server does not cover them
- You need HTTP transport instead of stdio
- You have no Bitrix24 inbound webhook with rights for tasks and groups
Example request
Create a Prepare report task for the Marketing workgroup and list that group's open tasksMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
BITRIX24_WEBHOOK_URLrequired, secret- Bitrix24 inbound webhook URL with rights for tasks, groups and users
Limitations
It covers only tasks, workgroups and users; CRM entities are not supported. It runs stdio-only, with no HTTP transport. Task listing pulls 50 records per page from Bitrix24, and limit is applied afterward as a local slice.
How to disable. Remove the mcp_servers.bitrix24 block from your client config and revoke the webhook in Bitrix24 settings.
FAQ
Can I work with deals through this server?
No, the README scopes it to tasks, workgroups and users.
How do I check that a field in fields exists?
Call get_task_fields; create_task validates the fields keys you pass against that list.
Discussion
No questions or reviews yet.
Related
All Bitrix24 toolsA compact Bitrix24 MCP server on an inbound webhook: tasks, groups, kanban stages and task comments
Bitrix24 MCP by Bit2Beat
Bitrix24 MCP Server
Bitrix24 MCP server over an inbound webhook: CRM, tasks, disk, calendar, chat, business processes and config migration between portals
Bitrix24 MCP Server (gunnit)
Bitrix24 MCP Server
A TypeScript MCP server for Bitrix24 CRM: contacts, companies, leads, deals, tasks and sales rep performance reports
Bitrix24 MCP server with real calls
MCP Server for Bitrix24
A Bitrix24 MCP server with 43 tools and about 870 actions that executes real REST API calls instead of just serving documentation
A read and write MCP server for the Bitrix24 REST API: CRM, tasks, scrum, calendar, disk, messaging and portal events
Bitrix24 MCP Server (qwito)
Bitrix24 MCP Server
A TypeScript MCP server with 45-plus tools for Bitrix24 CRM: contacts, deals, leads, companies, tasks and activity analytics
README in short
The English README describes the server as an MCP/JSON-RPC over STDIO implementation for Bitrix24 tasks, workgroups and users. It gives a table of all tools with input and output parameters, a Codex config example with the BITRIX24_WEBHOOK_URL variable, and an architecture description across mcp, adapters, domain and infrastructure layers. It notes that validation uses zod and transport is STDIO only.