bitrix24-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Address the HTTP server binds to (used when MCP_TRANSPORT=http). | 127.0.0.1 |
| MCP_PORT | No | Port the HTTP server listens on (used when MCP_TRANSPORT=http). | 8000 |
| LOG_LEVEL | No | Log level; logs are written to stderr. | INFO |
| MCP_TRANSPORT | No | Transport mode: stdio or http. | stdio |
| MCP_AUTH_TOKEN | No | Bearer token required for the http transport; clients must send Authorization: Bearer <MCP_AUTH_TOKEN>. Mandatory when MCP_TRANSPORT=http — without a token the HTTP mode will not start. | |
| MCP_ALLOWED_HOSTS | No | Allowed Host headers (protection against DNS rebinding). | |
| BITRIX24_READ_ONLY | No | Server is read-only by default; set to false to enable write tools (create leads, deals and tasks, move deal stages, add timeline comments). | true |
| BITRIX24_WEBHOOK_URL | Yes | URL of the Bitrix24 inbound webhook, e.g. https://your-portal.bitrix24.com/rest/1/xxxxxxxx/. This is required. Create it under Developer resources → Other → Inbound webhook with only the scopes you need (crm, task, user). Treat it as a secret. | |
| BITRIX24_ALLOW_RAW_CALLS | No | Enables the call_method tool for calling any Bitrix24 REST API method. | false |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whoamiA | Return the Bitrix24 user the webhook acts as (ID, name, email). |
| list_deal_stagesB | List deal stages of a pipeline (category 0 is the default pipeline). |
| list_dealsB | List deals, newest first. Filters are optional and combined with AND. |
| get_dealC | Get all fields of one deal. |
| search_contactsA | Find contacts by phone, email or name. A query with '@' searches email, a query with 6+ digits searches phone, anything else searches first and last name. |
| get_contactB | Get one contact; phones and emails are returned as plain lists. |
| list_leadsA | List leads, newest first, optionally by status (e.g. NEW, IN_PROCESS). |
| list_tasksB | List tasks, newest first. status: 2 pending, 3 in progress, 4 awaiting control, 5 completed, 6 deferred. |
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 8 tools
Each tool maps to a distinct resource/action: identity, deal stages, deals list/get, contact search/get, leads, and tasks. The only near-neighbor pair is list_deals/list_deal_stages, but their descriptions make the boundary clear.
Seven of eight tools follow a predictable verb_noun snake_case pattern such as list_deals, get_deal, and search_contacts. whoami is an idiomatic exception, but otherwise singular/plural usage is consistent with the list-vs-get convention.
Eight tools is well within the recommended 3-15 range and each covers a distinct operation. There are no redundant or filler tools for the apparent read-only Bitrix24 subset.
The surface is almost entirely read-only: there are no create, update, or delete operations for deals, contacts, leads, or tasks. It also lacks get_lead, get_task, and a general list_contacts, so agents cannot complete mutating CRM workflows or inspect individual leads/tasks.