create_taskLABSCO SUMMARY
Task writes checked against your instance before they are sent.
The field validation is the detail worth noticing: Bitrix24 portals are customised heavily, and get_task_fields lets a write be shaped against what this portal defines rather than rejected by it. Authentication is an inbound webhook URL rather than OAuth, which makes setup a copy-and-paste but also means that one string is the whole credential.
What it is
A Bitrix24 server covering tasks, workgroups and users. Task writes are validated before they go out — if you pass custom fields, the keys are checked against what the instance says a task holds — and every call is a JSON-RPC exchange over stdio against your own Bitrix24 webhook.
What you get
- Tasks created with title, description, responsible person, group and custom fields
- Tasks updated, closed and reopened by id
- Tasks listed by responsible person or group, with paging
- The field definitions a task on your instance actually holds, used to validate what you send
- A task's history returned as entries with date, field, value and the user who changed it
- Workgroups created and listed
- Users listed with Bitrix24's own filter syntax, and the current user resolved
- The user field definitions available
Requirements
Node.js 18 or newer, and an inbound webhook URL from your portal set in the environment. That webhook's own scope is the ceiling on what any of these tools can reach.
Setup effort
One command plus credentials — npx mcp-bitrix24, then supply credentials
USE CASES
01
Filing a task from wherever the work was decided
Read what fields a task carries on your portal, then create it with title, description and responsible person already correct instead of leaving them blank for someone to fix.
02
Seeing what someone is carrying
List tasks by responsible person or by workgroup, paged, so a workload question is answered without opening the portal's task view.
03
Closing out what is finished
Close the tasks that are done and reopen the one that came back, from the conversation where the outcome was established.
04
Working out what happened to a task
Read the history and get back who changed which field and when — the record that settles a disagreement about scope or a due date.
05
Standing up a workgroup for new work
Create the group, then file its first tasks against it, rather than creating tasks in the inbox and moving them later.
06
Finding out who you are connected as
Resolve the current user and read the available user fields, which is the quickest way to confirm a webhook is pointed where you think it is.
12 tools
Listed in project docs. Your client may show a different list.
update_taskclose_taskreopen_tasklist_tasksget_task_fieldslist_task_historycreate_grouplist_groupslist_usersget_user_fieldsget_current_userBEFORE YOU INSTALL
What to know first
Tools you get
12 tools named in the project's documentation.
Requires
- npx on PATH
- Node.js >= 18
- BITRIX24_WEBHOOK_URL in your environment
INSTALLATION
Connect your client
Server setup
TERMINAL
npx mcp-bitrix24MCP Clients
Codex
CODEX · TOML
[mcp_servers.bitrix24]
command = "npx"
args = ["-y", "mcp-bitrix24"]
[mcp_servers.bitrix24.env]
BITRIX24_WEBHOOK_URL = "https://<YOUR_DOMAIN>/rest/<YOUR_USER_ID>/<YOUR_WEBHOOK>/"
