bitrix24-tasks-mcp-server
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 5 of 5 tools tried
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y bitrix24-tasks-mcp-server@1.8.0
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
5 tools that take no input and look read-only were called once with nothing. 5 returned a result.
bitrix24_list_tasks | Returned a result under 0.1 s · 69 characters |
bitrix24_get_latest_tasks | Returned a result under 0.1 s · 69 characters |
bitrix24_list_projects | Returned a result under 0.1 s · 69 characters |
bitrix24_get_crm_sources | Returned a result under 0.1 s · 69 characters |
bitrix24_get_crm_lead_stages | Returned a result under 0.1 s · 69 characters |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
bitrix24_create_task title, description, responsibleId, creatorId, projectId, parentTaskId, deadline, priority, filePaths, diskFolderId, checklist
Create a new task in Bitrix24
bitrix24_get_task_summary taskId, select
Read a strict bounded task projection for workflow intake and routing. DESCRIPTION is capped at 12000 characters; TITLE is display metadata and must not be used as a routing signal.
bitrix24_get_task_stage taskId
Read the current task stage and minimal routing metadata without loading comments, description, or files.
bitrix24_get_task id, includeComments, includeTaskFiles, includeCommentAttachments, preferApi, commentsLimit, includeSystemMessages, includeContent, imagesOnly, saveToDirectory
Get task by ID with all legacy UF_* custom fields, comments, and file attachments in one call. Comments use task chat (im) when available; attachments download via disk.file.get (not browser SSO URLs).
bitrix24_list_tasks limit, onlyMy, filter, orderBy, orderDirection
List tasks with optional filtering and ordering
44 more tools
bitrix24_get_latest_tasks limit
Get the most recent tasks ordered by creation date
bitrix24_get_tasks_from_date_range startDate, endDate, limit
Get tasks created within a specific date range
bitrix24_get_task_comments taskId, preferApi, orderBy, orderDirection, filter, limit, lastId, firstId, includeSystemMessages, commentIds, includeAttachments, attachmentIds, includeContent, imagesOnly, saveToDirectory
Get task comments/messages. Uses modern task chat API (im.dialog.messages.get) when available, falls back to legacy task.commentitem.getlist. Downloads attachments from chat files or ATTACHED_OBJECTS.
bitrix24_get_comments_after taskId, afterCommentId, preferApi, limit, includeSystemMessages, maxCommentChars, maxTotalChars
Read compact comments newer than a known comment/message ID. Returns text and metadata only; never downloads attachments or file bytes.
bitrix24_update_task id, title, description, responsibleId, projectId, parentTaskId, deadline, priority, status
Update an existing task in Bitrix24
bitrix24_update_task_custom_fields taskId, fields, overwriteExisting
Update one or more Bitrix24 task custom fields (UF_TASK_*). Reads current values first, protects populated fields by default, and verifies the write.
bitrix24_get_task_stages entityId, entityType
Get Kanban/My Plan stages for a Bitrix24 task group or user plan
bitrix24_can_move_task_in_stages entityId, entityType
Check whether the webhook user can move tasks in a Bitrix24 Kanban/My Plan object
bitrix24_move_task_to_stage taskId, stageId, stageName, entityId, entityType, before, after
Move a task to another Kanban/My Plan stage using task.stages.movetask. Provide stageId directly or stageName with entityId.
bitrix24_get_task_files taskId, diskFileIds, includeContent, imagesOnly, saveToDirectory
Download files attached to a Bitrix24 task (UF_TASK_WEBDAV_FILES and [disk file id=...] in description). Returns metadata and optional base64 content for images.
bitrix24_get_task_files_metadata taskId, diskFileIds, imagesOnly, afterFileId, limit
Read one bounded page of task attachment metadata without downloading file bytes or emitting base64.
bitrix24_add_task_comment taskId, text, filePaths, diskFolderId, authorId, preferApi
Post a comment/message to a task. Modern path: tasks.task.chat.message.send + im.disk.file.commit; legacy fallback: task.commentitem.add.
bitrix24_publish_task_composite taskId, runId, evidenceSha256, comments, targetStageId, expectedCurrentStageId, preferApi, diskFolderId
Idempotently publish a bounded ordered set of final comments/evidence attachments and then move the task to one exact stage with read-back verification. Use one call for final workflow publication.
bitrix24_attach_files_to_task taskId, filePaths, diskFolderId
Upload local files (images, documents) to Bitrix24 Disk and attach them to an existing task
bitrix24_add_task_checklist_item taskId, title, parentId, sortIndex, isComplete, isImportant
Add a checklist item to a task
bitrix24_list_task_checklist_items taskId, orderBy, orderDirection
List checklist items for a task
bitrix24_update_task_checklist_item taskId, itemId, title, parentId, sortIndex, isComplete, isImportant
Update a checklist item in a task
bitrix24_delete_task_checklist_item taskId, itemId
Delete a checklist item from a task
bitrix24_get_task_dependencies taskId
Get task dependencies from DEPENDS_ON field
bitrix24_add_task_dependency taskIdFrom, taskIdTo, linkType
Create dependency link between two tasks
bitrix24_delete_task_dependency taskIdFrom, taskIdTo, linkType
Delete dependency link between two tasks
bitrix24_create_project name, description, ownerId, opened
Create a new workgroup/project in Bitrix24
bitrix24_get_project id
Retrieve project information by ID
bitrix24_list_projects limit, filter, orderBy, orderDirection
List projects/workgroups with optional filtering
bitrix24_update_project id, name, description, ownerId, opened, closed, active
Update an existing project/workgroup in Bitrix24
bitrix24_search_tasks_projects query, includeTasks, includeProjects, limit
Search tasks and projects by title/name and description
bitrix24_validate_webhook
Validate Bitrix24 webhook connection for tasks/projects scope
bitrix24_diagnose_permissions
Diagnose webhook permissions for tasks and projects endpoints
bitrix24_get_user userId
Get user information by ID
bitrix24_get_all_users
Get all users in the system
bitrix24_find_users_by_full_name fullName, activeOnly, emailDomain
Find active Bitrix24 users by exact normalized full name using server-side user filters. Returns none, unique, or ambiguous status; use an ID only when status is unique.
bitrix24_resolve_user_names userIds
Resolve user IDs to user names
bitrix24_get_crm_sources
Read all CRM lead sources via crm.status.list (ENTITY_ID=SOURCE). Returns STATUS_ID codes and NAME labels. Discover the mail source before creating leads; this tool only reads configuration.
bitrix24_get_crm_lead_stages
Read all CRM lead stages/statuses via crm.status.list (ENTITY_ID=STATUS), including STATUS_ID, NAME, SEMANTICS and colors. Verify NEW before creating a lead; these are CRM stages, not task stages.
bitrix24_get_crm_fields entity, customOnly, fieldNames
Read CRM field metadata via crm.lead.fields, crm.company.fields or crm.contact.fields. Includes standard and UF_CRM_* custom fields, types, labels, required/read-only/multiple flags and enumeration items with their IDs. Does not read card values or change CRM settings.
bitrix24_get_crm_user_fields entity, fieldNames
Read only CRM custom/user fields (UF_CRM_*) and enum item IDs using the entity fields API. Discover Message-ID, run ID and parse-status field codes/values before a write. This returns field definitions, not customer data.
bitrix24_find_crm_lead_by_message_id messageIdField, messageId
Read-only CRM lead lookup by exact Message-ID in an existing single string UF_CRM_* field. Validate the field, read all matching pages and return none/unique/ambiguous with card URLs. Use before retrying an uncertain write; this tool never creates a lead.
bitrix24_find_crm_user_by_email email, fallbackUserId
Find one active Bitrix24 employee by exact email and select a configured fallback when none is found.
bitrix24_find_crm_company inn, phone, email, title
Find a CRM company sequentially by exact INN, phone, email, then exact normalized title. Returns none, unique, or ambiguous.
bitrix24_resolve_or_create_crm_company inn, phone, email, title, assignedById, requisitePresetId, comments, additionalFields
Reuse one matching company, return candidates on ambiguity, or create a draft company without creating an obvious duplicate.
bitrix24_find_crm_contact phone, email
Find a CRM contact by client phone and then client email. Does not infer contact data.
bitrix24_resolve_or_create_crm_contact name, lastName, secondName, phone, email, companyId, assignedById, comments, additionalFields
Reuse one matching client contact, report ambiguity, or create a contact only when phone or email is supplied.
bitrix24_create_crm_lead_idempotent title, sourceId, assignedById, comments, messageId, runId, messageIdField, runIdField, parseStatusField, parseStatus, companyId, contactId, name, lastName, phone, email, additionalFields
Create a NEW CRM lead with Message-ID duplicate lookup, same-host serialization, read-back verification and recovery lookup after an uncertain REST response. Orchestrators must serialize distributed workers and reconcile uncertain writes before retrying.
bitrix24_get_crm_entity entity, id
Get a CRM lead, company, or contact by ID and return its Bitrix24 detail URL.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=18.0.0 |
| Source | not stated |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-Pvrph6kZFPafD5doqO/avTncoD6TCr3rNaaDReyuGqk99hDlq5wmLlh6KMg0WJ3KLBsI8FUYDi5uddk0/wGP8Q== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/bitrix24-tasks-mcp-server)
New version out? Ask for a fresh report.