@theyahia/bitrix24-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITRIX24_WEBHOOK_URL | Yes | Full Bitrix24 webhook URL including auth key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_dealsA | List CRM deals from Bitrix24 with optional filters by stage, responsible user, and sort order. |
| get_dealA | Get a single CRM deal by ID with all fields. |
| create_dealA | Create a new CRM deal in Bitrix24 with title, amount, stage, and linked contact/company. |
| update_dealB | Update an existing CRM deal fields: title, stage, amount, contacts, etc. |
| list_contactsA | List CRM contacts from Bitrix24 with optional filters by name, phone, or email. |
| create_contactB | Create a new CRM contact with name, last name, phone, and email. |
| list_tasksB | List tasks from Bitrix24 with optional filters by status, responsible user, and group. |
| create_taskB | Create a new task in Bitrix24 with title, description, responsible user, and deadline. |
| complete_taskA | Mark a Bitrix24 task as completed by task ID. |
| list_usersA | List Bitrix24 users with optional filters by active status and department. |
| upload_fileA | Upload a file to Bitrix24 disk folder (base64-encoded content). |
| send_messageA | Send an instant message via Bitrix24 IM to a user or chat. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool targets a clearly distinct resource and action, such as list_deals vs get_deal or create_task vs complete_task. No two tools appear to overlap in purpose.
All tool names follow a consistent verb_noun snake_case pattern, e.g. list_deals, create_deal, update_deal, upload_file, send_message. This makes the API surface predictable.
Twelve tools is a reasonable, focused set for a Bitrix24 integration covering deals, contacts, tasks, users, files, and messaging. Each tool earns its place without bloat.
Core workflows for deals, contacts, and tasks are present, but there are notable gaps: contacts lack update/delete and get-by-id, tasks lack get/update/delete, and deals lack delete. These missing operations could force agents into workarounds.