mcp server
Bitrix MCP
MCP server that delivers up-to-date Bitrix24 REST API documentation.
Description as published by the maintainer. Source
- version 1.0.0
- slowing
- documentation
- document understanding
slowing — Registry entry last updated 2025-11-26. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
5 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
bitrix-app-development-doc-details(title_or_hint)- Fetch Bitrix24 app development documentation by exact title (use `bitrix-search` with doc_type app_development_docs). Returns plain text labeled fields (Title, URL, Module, Category, Description, Content) without Markdown. Required: title_or_hint.
bitrix-article-details(title_or_hint)- Fetch a non-method Bitrix24 documentation article by exact title (use `bitrix-search` with doc_type other). Returns Markdown with title, metadata (URL/module/category), description, and content. Required: title_or_hint.
bitrix-event-details(title_or_hint)- Fetch Bitrix24 event documentation by exact event name (use `bitrix-search` with doc_type event). Returns Markdown with title, metadata (URL/module/category), description, and content. Required: title_or_hint.
bitrix-method-details(field, filter, method)- Get details for a Bitrix24 REST method by exact name (use `bitrix-search` first). Returns plain text with labeled sections including parameters, returns, errors, and examples. Optional `field` limits output; `filter` narrows params by entity or examples by language. Required: method.
bitrix-search(limit, query, doc_type)- Search Bitrix24 REST docs by natural-language query and return a short plain-text list of matches (method/event/article/app doc) with name, type, and brief description. Use the exact name/title from results when calling details tools. Optional filters: `limit` and `doc_type` (method|event|other|app_development_docs). Required: query.
Last successful function declaration observed on . Source: https://mcp-dev.bitrix24.com/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://mcp-dev.bitrix24.com/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2025-11-26 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2025-11-26 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 5 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | mcp-dev.bitrix24.com | |
| mcp endpoint status | ok | The server listed 5 functions when asked. | as of probe | mcp-dev.bitrix24.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json