Bitrix MCP
Server Details
MCP server that delivers up-to-date Bitrix24 REST API documentation.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.2/5 across 5 of 5 tools scored. Lowest: 3.4/5.
Each tool has a clearly distinct purpose: bitrix-search is for general searching, while the other four tools each fetch details for a specific documentation type (app development, articles, events, methods). The descriptions explicitly differentiate them by doc_type and output format, leaving no ambiguity about which tool to use for a given task.
All tool names follow a consistent pattern: 'bitrix-' prefix, followed by a descriptive noun or noun phrase (e.g., 'search', 'method-details'), and ending with '-details' for the four detail-fetching tools. This verb_noun-like structure is uniform throughout the set, making it predictable and easy to understand.
With 5 tools, the set is well-scoped for a documentation server focused on Bitrix24. It includes a search tool and four detail tools covering key documentation types, which is efficient and avoids bloat. Each tool serves a clear, necessary function without redundancy.
The tool surface is complete for the domain of fetching Bitrix24 documentation. It covers the full workflow: searching across all doc types with bitrix-search, then retrieving detailed information for each specific type (app development, articles, events, methods). There are no obvious gaps, as agents can seamlessly move from search to details without dead ends.
Available Tools
5 toolsbitrix-app-development-doc-detailsInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| title_or_hint | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
bitrix-article-detailsInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| title_or_hint | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
bitrix-event-detailsInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| title_or_hint | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
bitrix-method-detailsInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| field | No | all | |
| filter | No | ||
| method | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
bitrix-searchInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | Yes | ||
| doc_type | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
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 published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!