Bitrix24

Server Details

MCP server enabling AI agents to manage Bitrix24 features via standardized protocol

Status: Healthy
Last Tested: 2026-03-22 12:30
Transport: Streamable HTTP
URL

See and control every tool call

Log every tool call with full inputs and outputs

Control which tools are enabled per connector

Manage credentials once, use from any MCP client

Monitor uptime and get alerted when servers go down

Available Tools

43 tools

add_accomplicesInspect

Adds accomplices to the task by their user IDs.

ParametersJSON Schema

Name	Required	Description	Default
`taskId`	Yes	Identifier of the task. Must be a positive integer.
`accompliceIds`	Yes	Array of user identifiers to add as accomplices. Must not be an empty array.

add_auditorsInspect

Adds auditors to the task by their user IDs.

ParametersJSON Schema

Name	Required	Description	Default
`taskId`	Yes	Identifier of the task. Must be a positive integer.
`auditorIds`	Yes	Array of user identifiers to add as auditors. Must not be an empty array.

add_current_user_as_auditorInspect

Adds current user as an auditor to the specified task.

ParametersJSON Schema

Name	Required	Description	Default
`taskId`	Yes	Identifier of the task. Must be a positive integer.

add_task_reminderInspect

Adds or updates a reminder for a task, specifying whom and when to remind.

ParametersJSON Schema

Name	Required	Description
`taskId`	Yes	Identifier of the task. Must be a positive integer.
`remindAt`	Yes	When to send the reminder, in 'Y/m/d H:i' format (e.g., '2024/08/15 10:00').
`remindBy`	No	The principle for reminding. Defaults to 'date'.
`recipient`	Yes	Task participant to send a reminder to.
`remindVia`	No	How to send the reminder. Defaults to 'notification'.

add_task_resultInspect

Adds a formal work summary or result to the task. This is typically used to document the final outcome of a task.

ParametersJSON Schema

Name	Required	Description	Default
`text`	Yes	The result text. Must not be an empty string.
`taskId`	Yes	Identifier of the task. Must be a positive integer.

clear_task_deadlineInspect

Clears the deadline for a task.

ParametersJSON Schema

Name	Required	Description	Default
`taskId`	No	Identifier of the task to update. Must be a positive integer.

create_check_listInspect

Creates a new checklist inside a task.

ParametersJSON Schema

Name	Required	Description
`title`	Yes	Title of the checklist. Must not be an empty string.
`taskId`	Yes	Identifier of the task. Must be a positive integer.
`checkListItems`	No	List of items to be added to the checklist.

create_check_list_itemInspect

Adds a new item to a checklist.

ParametersJSON Schema

Name	Required	Description	Default
`title`	Yes	Title of the checklist item. Must not be an empty string.
`checkListId`	Yes	Identifier of the checklist. Must not be null.

create_crm_custom_fieldInspect

Creates a custom field for a CRM deal. Use this function when a new CRM field needs to be created

ParametersJSON Schema

Name	Required	Description
`type`	Yes	Type of the custom field being created
`label`	Yes	Name of the custom field to be created
`categoryId`	Yes	Identifier of the CRM deal funnel, also referred to as 'category'
`isMultiple`	Yes	Indicates if the custom field accepts multiple values. Always false for boolean fields. For enumeration fields, set to true if multiple options can be chosen (similar to a multi-select list); otherwise, set to false (standard single-select enumeration)
`enumerationList`	No	List of selectable options for a custom enumeration-type field. Required if the field type is set to 'enumeration'

create_dealInspect

Creates a deal with the title specified by title in the funnel identified by categoryId. Use this function when explicitly instructed to create a new deal in a particular CRM funnel

ParametersJSON Schema

Name	Required	Description	Default
`title`	Yes	Title of the deal. Must not be an empty string
`categoryId`	Yes	Identifier of the funnel in which the deal will be created

create_default_funnelInspect

Creates a new funnel with the specified name and sets the default stages. Use this function to add a standard funnel to the CRM without customizing the stages.

ParametersJSON Schema

Name	Required	Description	Default
`name`	Yes	Name of the funnel to be created

create_funnel_with_custom_stagesInspect

Creates a new funnel with the specified name and custom 'In Progress' stages, while keeping the default stages unchanged. Use this to add a customized funnel to the CRM.

ParametersJSON Schema

Name	Required	Description	Default
`name`	Yes	Name of the funnel to be created
`stages`	Yes	Array of custom stages (cannot be empty)

create_new_funnel_stageInspect

Creates a new stage with the specified fields for the entity with entity type identifier entityTypeId in the funnel identified by categoryId. Use this function when explicitly instructed to add a new custom funnel stage

ParametersJSON Schema

Name	Required	Description
`fields`	Yes	Fields for the new CRM funnel stage
`categoryId`	Yes	Identifier of the CRM entity funnel. Must be null if entityTypeId is 1 or 7. In all other cases, categoryId must not be null
`entityTypeId`	Yes	CRM entity type identifier. Possible values: 1 (Lead), 2 (Deal), 7 (Proposal), 31 (Invoice), or an identifier of a smart-process type

create_taskInspect

Creates a new task with the provided title and other details.

ParametersJSON Schema

Name	Required	Description
`title`	Yes	Task title. Must be a non-empty string
`status`	No	Task status
`groupId`	No	Identifier of the group for the task. Must be a positive integer.
`priority`	No	Task priority. 'high' marks it as important, 'average' unmarks it.
`creatorId`	No	Identifier of the creator. Defaults to the current user.
`auditorIds`	No	List of user IDs to add as auditors
`description`	No	Task description
`deadlineDate`	No	Task deadline in 'Y/m/d H:i' format
`parentTaskId`	No	Identifier of the parent task to create a subtask. Must be a positive integer
`accompliceIds`	No	List of user IDs to add as accomplices
`responsibleId`	No	Identifier of the responsible user. Defaults to the current user.

deal_category_listInspect

Searches for CRM deals categories (funnels). Use this function when you need to find all categories (funnels) for deals or find the funnel identifier by funnel name.

ParametersJSON Schema

Name	Required	Description	Default
`name`	No	CRM deal category (funnel) name (minimum 2 characters).

deal_stage_listInspect

Searches for CRM deal stages for deal in the specified category (funnel). Use this function when you need to find all stages for deal in the specified category (funnel) or find the stage identifier by stage name in the specified category (funnel).

ParametersJSON Schema

Name	Required	Description	Default
`name`	No	CRM deal stage name (minimum 2 characters).
`categoryId`	Yes	Deal category (funnel) identifier.

delete_accomplicesInspect

Removes accomplices from the task. This action is irreversible.

ParametersJSON Schema

Name	Required	Description	Default
`taskId`	Yes	Identifier of the task. Must be a positive integer.
`accompliceIds`	Yes	Array of user identifiers to remove from accomplices. Must not be an empty array.

delete_auditorsInspect

Removes auditors from the task. This action is irreversible.

ParametersJSON Schema

Name	Required	Description	Default
`taskId`	Yes	Identifier of the task. Must be a positive integer.
`auditorIds`	Yes	Array of user identifiers to remove from auditors. Must not be an empty array.

delete_check_listInspect

Deletes an entire checklist or checklist item from a task. This action is irreversible.

ParametersJSON Schema

Name	Required	Description	Default
`checkListId`	Yes	Identifier of the checklist to delete. Must be a positive integer.

delete_check_list_itemInspect

Deletes an entire checklist item from a task. This action is irreversible.

ParametersJSON Schema

Name	Required	Description	Default
`itemId`	No	Identifier of the checklist item to delete. Must be a positive integer.

delete_funnelInspect

Deletes the funnel identified by categoryId for the entity with the entity type identifier entityTypeId

ParametersJSON Schema

Name	Required	Description	Default
`categoryId`	Yes	Identifier of the CRM funnel to be deleted
`entityTypeId`	Yes	CRM entity type identifier. Possible values: 2 (Deal) or the identifier of a smart-process type

delete_funnel_stageInspect

Deletes the stage identified by stageId for the entity with the entity type identifier entityTypeId in the funnel identified by categoryId.

ParametersJSON Schema

Name	Required	Description
`stageId`	Yes	Identifier of the funnel stage to be deleted. Must not be an empty string.
`categoryId`	Yes	Identifier of the CRM entity funnel. Must be null if entityTypeId is 1 or 7. In all other cases, categoryId must not be null
`entityTypeId`	Yes	CRM entity type identifier. Possible values: 1 (Lead), 2 (Deal), 7 (Proposal), 31 (Invoice), or an identifier of a smart-process type

delete_taskInspect

Deletes the specified task. This action is irreversible.

ParametersJSON Schema

Name	Required	Description	Default
`taskId`	Yes	Identifier of the task to delete. Must be a positive integer.

detach_task_from_groupInspect

Detaches a task from a group.

ParametersJSON Schema

Name	Required	Description	Default
`taskId`	No	Identifier of the task to update. Must be a positive integer.

get_task_by_idInspect

Retrieves full task data by its identifier.

ParametersJSON Schema

Name	Required	Description	Default
`taskId`	Yes	Identifier of the task. Must be a positive integer.

lead_stage_listInspect

Searches for CRM leads stages. Use this function when you need to find all stages for leads or find the stage identifier by stage name.

ParametersJSON Schema

Name	Required	Description	Default
`name`	No	CRM lead stage name (minimum 2 characters).

move_deals_between_funnelsInspect

Moves all deals (maximum 100) from one funnel identified by from to another funnel identified by to. Use this function when explicitly instructed to transfer deals between different funnels

ParametersJSON Schema

Name	Required	Description	Default
`to`	Yes	Identifier of the funnel to which the deals will be transferred
`from`	Yes	Identifier of the funnel from which the deals will be transferred

move_deals_between_stagesInspect

Moves all deals (maximum 100) from the stage identified by from to the stage identified by to within the funnel specified by categoryId. Use this function when explicitly instructed to transfer deals between different stages of the same funnel

ParametersJSON Schema

Name	Required	Description
`to`	Yes	Identifier of the stage to which the deals should be transferred
`from`	Yes	Identifier of the stage from which the deals should be transferred
`categoryId`	Yes	Identifier of the funnel within which deals are moved between stages

rename_funnel_stagesInspect

Renames the stage names for the entity with an entity type identifier entityTypeId in the funnel identified by categoryId. Use this function when explicitly instructed to rename one or more stages

ParametersJSON Schema

Name	Required	Description
`names`	Yes	Object containing information about the funnel stage and its new name
`categoryId`	Yes	Identifier of the CRM entity funnel. Must be null if entityTypeId is 1 or 7. In all other cases, categoryId must not be null
`entityTypeId`	Yes	CRM entity type identifier. Possible values: 1 (Lead), 2 (Deal), 7 (Proposal), 31 (Invoice), or an identifier of a smart-process type

rename_funnel_titleInspect

Renames the funnel identified by categoryId to title for an entity with the entity type identifier entityTypeId. Use this function to update the existing CRM funnel name

ParametersJSON Schema

Name	Required	Description
`title`	Yes	New funnel title. Must not be an empty string
`categoryId`	Yes	Identifier of the CRM entity sales funnel, also referred to as 'category'
`entityTypeId`	Yes	CRM entity type identifier. Can be either 2 (Deal) or a smart-process type identifier

search_tasksInspect

Searches for tasks based on various criteria. Returns their identifiers, names and deadline. If you want to search for tasks by 'RESPONSIBLE_ID', 'CREATED_BY' or 'GROUP_ID', the value must be a numeric identifier, not a user's or group's name. If you don't know identifiers, use another tools for find it firstly.

ParametersJSON Schema

Name	Required	Description
`tag`	No	Tag name to search for or null if not needed.
`title`	No	Keyword to search in the task title or null if not needed.
`status`	No	Task status to search for. By default, tasks in progress are searched.
`groupId`	No	Identifier of the group. Must be a positive integer or null if not needed.
`memberId`	No	Identifier of a task member. Leave null for the current user.
`auditorId`	No	Identifier of the auditor. Must be a positive integer or null if not needed.
`creatorId`	No	Identifier of the user who created the task. Must be a positive integer or null if not needed.
`deadlineTo`	No	The end of the deadline range in 'Y/m/d H:i' format or null if not needed.
`description`	No	Keyword to search in the task description or null if not needed.
`accompliceId`	No	Identifier of the accomplice. Must be a positive integer or null if not needed.
`deadlineFrom`	No	The start of the deadline range in 'Y/m/d H:i' format or null if not needed.
`responsibleId`	No	Identifier of the responsible user. Must be a positive integer or null if not needed.

search_usersInspect

Searches for a SINGLE user to get their ID by trying a list of possible name variations. Use this to find one user's ID, which can then be used in other tools.

ParametersJSON Schema

Name	Required	Description	Default
`searchQueries`	Yes	A list of name variations for the user you are trying to find. Provide different spellings, diminutive forms, or transliterations.

send_chat_messageInspect

Sends a free‐form message in the task's chat on behalf of the current user. Also can be used to leave a comment on a task.

ParametersJSON Schema

Name	Required	Description	Default
`text`	Yes	Text to send. Must not be an empty string.
`taskId`	Yes	Identifier of the task whose chat to post into. Must be a positive integer.

set_daily_task_recurrenceInspect

Sets up a daily recurrence for a task. Allows specifying an interval and can restrict the recurrence to workdays only.

ParametersJSON Schema

Name	Required	Description
`time`	No	Time of day for the recurrence in 'HH:MM:SS' format. Default is 05:00.
`times`	No	If repeatTill is "times" it must be a number of repeats
`taskId`	Yes	Identifier of the task. Must be a positive integer.
`endDate`	No	End date for recurrence if repeatTill is 'date', in 'Y/m/d H:i' format.
`everyDay`	No	The number of days between repetitions.
`startDate`	No	Recurrence start date, in Y/m/d H:i format. Default is save date.
`repeatTill`	No	Condition for stopping recurrence.
`workdayOnly`	No	If true, the task will only recur on workdays. Default is false.
`dailyMonthInterval`	No	The interval in months between repetitions of the task. Default is 0.

set_monthly_by_month_days_task_recurrenceInspect

Sets up a monthly recurrence for a task based on a specific day of the month. Use this to make a task repeat on the same date every month or every few months.

ParametersJSON Schema

Name	Required	Description
`time`	No	Time of day for the recurrence in 'HH:MM:SS' format. Default is 05:00.
`times`	No	If repeatTill is "times" it must be a number of repeats
`taskId`	Yes	Identifier of the task. Must be a positive integer.
`endDate`	No	End date for recurrence if repeatTill is 'date', in 'Y/m/d H:i' format.
`startDate`	No	Recurrence start date, in Y/m/d H:i format. Default is save date.
`repeatTill`	No	Condition for stopping recurrence.
`workdayOnly`	No	If true, the task will only recur on workdays. Default is false.
`monthlyDayNum`	No	The date on which the task repetition in the month will be created. Starts with 1.
`monthlyMonthNum1`	No	The month on which the task repetition will be created. Starts with 0.
`monthlyMonthNum2`	No	The month in which the task repetition will be created in the week is specified here. Starts with 0.

set_monthly_by_week_days_task_recurrenceInspect

Sets up a monthly recurrence for a task based on the day of the week and its order within the month. Use for complex patterns like "the second Friday of every month" or "the last Monday every 3 months".

ParametersJSON Schema

Name	Required	Description
`time`	No	Time of day for the recurrence in 'HH:MM:SS' format. Default is 05:00.
`times`	No	If repeatTill is "times" it must be a number of repeats
`taskId`	Yes	Identifier of the task. Must be a positive integer.
`endDate`	No	End date for recurrence if repeatTill is 'date', in 'Y/m/d H:i' format.
`startDate`	No	Recurrence start date, in Y/m/d H:i format. Default is save date.
`repeatTill`	No	Condition for stopping recurrence.
`workdayOnly`	No	If true, the task will only recur on workdays. Default is false.
`monthlyWeekDay`	No	The day of the week on which the task will be repeated is reflected. Starts with 0.
`monthlyMonthNum2`	No	The month in which the task repetition will be created in the week is specified here. Starts with 0.
`monthlyWeekDayNum`	No	Which week the task will be repeated. Starts with 0.

set_weekly_task_recurrenceInspect

Sets up a weekly recurrence for a task. Allows selecting specific days of the week (e.g., Monday, Wednesday) and setting a weekly interval (e.g., every 2 weeks).

ParametersJSON Schema

Name	Required	Description
`time`	No	Time of day for the recurrence in 'HH:MM:SS' format. Default is 05:00.
`times`	No	If repeatTill is "times" it must be a number of repeats
`taskId`	Yes	Identifier of the task. Must be a positive integer.
`endDate`	No	End date for recurrence if repeatTill is 'date', in 'Y/m/d H:i' format.
`weekDays`	No	The numbers of the days of the week.
`everyWeek`	No	The number of weeks between repetitions.
`startDate`	No	Recurrence start date, in Y/m/d H:i format. Default is save date.
`repeatTill`	No	Condition for stopping recurrence.
`workdayOnly`	No	If true, the task will only recur on workdays. Default is false.

set_yearly_by_month_days_task_recurrenceInspect

Sets up a yearly (annual) recurrence for a task on a specific calendar date. Use this to make a task repeat on the same day and month each year, such as "every April 25th".

ParametersJSON Schema

Name	Required	Description
`time`	No	Time of day for the recurrence in 'HH:MM:SS' format. Default is 05:00.
`times`	No	If repeatTill is "times" it must be a number of repeats
`taskId`	Yes	Identifier of the task. Must be a positive integer.
`endDate`	No	End date for recurrence if repeatTill is 'date', in 'Y/m/d H:i' format.
`startDate`	No	Recurrence start date, in Y/m/d H:i format. Default is save date.
`repeatTill`	No	Condition for stopping recurrence.
`workdayOnly`	No	If true, the task will only recur on workdays. Default is false.
`yearlyDayNum`	No	The date on which the task repetition in the month will be created. Starts with 1.
`yearlyMonth1`	No	The month on which the task repetition will be created. Starts with 0.
`yearlyMonth2`	No	The month in which the task repetition will be created in the week is specified here. Starts with 0.

set_yearly_by_week_days_task_recurrenceInspect

Sets up a yearly recurrence for a task based on the day of the week and its order within a specific month. Use for complex annual patterns like "the fourth Thursday of November" every year.

ParametersJSON Schema

Name	Required	Description
`time`	No	Time of day for the recurrence in 'HH:MM:SS' format. Default is 05:00.
`times`	No	If repeatTill is "times" it must be a number of repeats
`taskId`	Yes	Identifier of the task. Must be a positive integer.
`endDate`	No	End date for recurrence if repeatTill is 'date', in 'Y/m/d H:i' format.
`startDate`	No	Recurrence start date, in Y/m/d H:i format. Default is save date.
`repeatTill`	No	Condition for stopping recurrence.
`workdayOnly`	No	If true, the task will only recur on workdays. Default is false.
`yearlyMonth2`	No	The month in which the task repetition will be created in the week is specified here. Starts with 0.
`yearlyWeekDay`	No	The day of the week on which the task repetition will be created. Starts with 0.
`yearlyWeekDayNum`	No	In which week the task will be repeated. Starts with 0.

update_check_listInspect

Updates the name or order of an existing checklist or checklist item.

ParametersJSON Schema

Name	Required	Description
`title`	No	New title. Must be a non-empty string or null to leave it unchanged.
`sortIndex`	No	New sort index for reordering the checklists. Must be a non-negative integer or null to leave it unchanged.
`checkListId`	Yes	Identifier of the checklist. Must be a positive integer.

update_check_list_itemInspect

Updates the name or order of an existing checklist item.

ParametersJSON Schema

Name	Required	Description
`title`	No	New title. Must be a non-empty string or null to leave it unchanged.
`itemId`	No	Identifier of the checklist item. Must be a positive integer.
`sortIndex`	No	New sort index for reordering the checklist items. Must be a non-negative integer or null to leave it unchanged.

update_funnel_stagesInspect

Updates the 'In Progress' stages for the funnel identified by categoryId. The default stages remain unchanged. Use this function to modify the custom stages of an existing CRM funnel.

ParametersJSON Schema

Name	Required	Description	Default
`stages`	Yes	Array of stage definitions (cannot be empty)
`categoryId`	Yes	Identifier of the target funnel

update_taskInspect

Updates an existing task with the provided data. Requires task ID.

ParametersJSON Schema

Name	Required	Description
`title`	No	New title. Null to leave unchanged
`status`	No	New status. Null to leave unchanged.
`taskId`	Yes	Identifier of the task to update. Must be a positive integer.
`groupId`	No	New group ID. Must be a positive integer. Null to leave unchanged. To detach from a group, use a dedicated tool.
`priority`	No	New priority. 'high' marks it as important, 'average' unmarks it.Null to leave unchanged.
`creatorId`	No	New creator's user ID. Must be a positive integer. Null to leave unchanged.
`description`	No	New description. Null to leave unchanged.
`deadlineDate`	No	New deadline in 'Y/m/d H:i' format. Null to leave unchanged. To clear the deadline, use a dedicated tool.
`parentTaskId`	No	New parent task ID. Must be a positive integer. Null to leave unchanged.
`responsibleId`	No	New responsible user's ID. Must be a positive integer. Null to leave unchanged.

Verify Ownership

Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "maintainers": [
    {
      "email": "your-email@example.com"
    }
  ]
}

The email address must match the email associated with your Glama account. Once verified, the connector will appear as claimed by you.

Last verification attempt failed. 2026-03-21 00:00

Discussions

No comments yet. Be the first to start the discussion!

Try in Browser

Server Details

Available Tools

Verify Ownership

Discussions

Your Connectors

Resources