Loading ToolBench
Universal, full-featured, portable MCP server for the Bitrix24 REST API (CRM, tasks, scrum, calendar, disk, users, messaging) — read and write.
BitrixMCP provides 30 tools with consistent naming (b24_ prefix) and basic schemas. However, descriptions are generic and parameter documentation is sparse. Most tools lack output schema documentation, and error handling guidance is minimal. Parameter descriptions are often single-phrase (e.g., 'Filter criteria', 'Maximum number of contacts to return') rather than actionable constraints. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear read/write distinctions. The universal tools (b24_call, b24_batch) are powerful but expose raw API complexity rather than abstracting it for LLM reasoning.
Batch up to 50 REST calls in one hit
List business process workflows
List calendar events with filtering
Universal REST method call - any Bitrix24 REST method
List catalog products
Poll for changes since a cursor position
List CRM contacts with filtering and pagination
List CRM deals with filtering and pagination
Generic parameter descriptions lack actionable constraints. 'Filter criteria' and 'Maximum number of contacts to return' do not specify valid ranges, formats, or examples. LLMs cannot infer whether limit=1000 is valid or if filter accepts nested objects.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., contact_id for follow-up updates). Responses are opaque.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk classifications. LLMs cannot distinguish safe reads from destructive writes without explicit hints.
Inferred effective spec: 2026-07-28+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 48 | 2026-07-28+ | v2 |
List CRM items (custom entity records) with filtering
List files in Bitrix24 Disk
List document generator templates
Acknowledge processed events
Query event history with filtering
Poll for pending events from the event queue
Get statistics about stored events
List groups/departments
Send a message in Bitrix24 messaging
List smart lists
List available REST methods from the catalog
List sales orders
Diagnose missing OAuth scopes against the live portal
List Scrum sprints
Create a new task
Get a single task by ID
List tasks with filtering and pagination
Update an existing task
Get Telegram forwarder settings
List telephony calls
Test connection to Bitrix24 portal and verify webhook
List users in the Bitrix24 portal
Universal tools (b24_call, b24_batch) expose raw Bitrix24 API complexity. LLMs must reason about method names, parameter structures, and error codes directly. No abstraction or guidance for common patterns.
Error handling lacks recovery guidance. No indication of retryable vs. fatal errors, missing scope hints, or suggestions for alternative tools when a call fails.