Name: Bitrix24 MCP-DEV
Author: bitrix24

LABSCO SUMMARY

Stops the model inventing Bitrix24 REST methods.

This one never touches your portal — it serves the documentation, so the code an assistant writes for a chatbot, an app or an integration points at methods that exist. If you have been getting 404s when the model opens a Bitrix24 documentation link, that is the gap it closes.

What it is

Bitrix24's documentation server for developers. It hands an AI assistant the current Bitrix24 REST reference — method descriptions, parameter lists, allowed values and usage hints — as structured data rather than free text.

What you get

Current method descriptions, parameters and allowed values, read at the moment you ask
The API methods and fields that fit the task you described
Structured data instead of pasted documentation prose
Connection instructions for Codex CLI, Cursor, GitHub Copilot Chat in VS Code, Claude Desktop, Claude Code CLI, Gemini Code Assist CLI and Google Antigravity

Requirements

The server address https://mcp-dev.bitrix24.com/mcp, and a client set to Streamable HTTP — it does not speak SSE, so choose transport type http rather than sse. The server is reachable without authorization.

Setup effort

One command — claude mcp add --transport http b24-dev-mcp https://mcp-dev.bitrix24.com/mcp

See installation options

USE CASES

01

Writing an integration against the REST API

Describe the task and the assistant pulls the methods and fields that fit, with their parameters and allowed values, before it writes a line of code.

02

Building a chatbot for Bitrix24

The assistant works from the current method reference rather than from memory, so the parameters it sends are the ones the portal accepts.

03

Checking a method the model just proposed

Look the method up against the live documentation and get its real parameter list — the quickest way to catch an invented call.

04

Setting up automation or an AI agent on a portal

Get the methods and usage hints for the part of Bitrix24 you are automating, so a no-code scenario is built on calls that resolve.

BEFORE YOU INSTALL

What to know first

Requires

An MCP client that supports Streamable HTTP — choose transport type http, not sse (the server does not support SSE)
No account or key: the server is accessible without authorization

INSTALLATION

Connect your client

Server setup

claude mcp add

Claude Code

TERMINAL

claude mcp add --transport http b24-dev-mcp https://mcp-dev.bitrix24.com/mcp

Hosted endpoint

ENDPOINT URL

https://mcp-dev.bitrix24.com/mcp

Add this hosted endpoint to your MCP client.

MCP Clients

Codex

CODEX · TERMINAL

codex mcp add b24-dev-mcp --url https://mcp-dev.bitrix24.com/mcp

Codex — config.toml

CODEX — CONFIG.TOML · TOML

[mcp_servers.b24-dev-mcp]
url = "https://mcp-dev.bitrix24.com/mcp"

Cursor

CURSOR · JSON

{
  "mcpServers": {
    "b24-dev-mcp": {
      "url": "https://mcp-dev.bitrix24.com/mcp",
      "timeout": 30000
    }
  }
}

GitHub Copilot

GITHUB COPILOT · JSON

{
  "servers": {
    "b24-dev-mcp": {
      "url": "https://mcp-dev.bitrix24.com/mcp",
      "type": "http"
    }
  },
  "inputs": []
}

Gemini CLI

GEMINI CLI · TERMINAL

gemini mcp add --transport http b24-dev-mcp https://mcp-dev.bitrix24.com/mcp

Antigravity

ANTIGRAVITY · JSON

{
  "mcpServers": {
    "b24-dev-mcp": {
      "serverUrl": "https://mcp-dev.bitrix24.com/mcp"
    }
  }
}

Bitrix24 MCP-DEV