Server Details
MCP server that delivers up-to-date Bitrix24 REST API documentation.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
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 |
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 |
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 |
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 |
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 |
Verify Ownership
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 verified, the connector will appear as claimed by you.
Last verification attempt failed.
Failed to fetch .well-known/glama.json: HTTP 403
Control your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
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!