Bitrix24 MCP Bridge
A Bitrix24 MCP bridge without a webhook or admin rights: a browser extension reuses an already-open portal session
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- It acts as the logged-in user through their live session
- Some tools and the generic bitrix_call perform mutating operations
- The extension loads in developer mode and gets access to the portal tab
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/darwim-bitrix24-mcp-bridgeDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
This entry is high risk, so there is no one-click install. Review the code and add the config by hand.
Run in a terminal
claude mcp add --transport stdio bitrix24-bridge -- npx -y bitrix24-mcp-bridgeOr add to the file .mcp.json, in the project
{
"mcpServers": {
"bitrix24-bridge": {
"command": "npx",
"args": [
"-y",
"bitrix24-mcp-bridge"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
Add to the file ~/.cursor/mcp.json, for all projects
{
"mcpServers": {
"bitrix24-bridge": {
"command": "npx",
"args": [
"-y",
"bitrix24-mcp-bridge"
]
}
}
}If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.
Run in a terminal
code --add-mcp '{"name":"bitrix24-bridge","type":"stdio","command":"npx","args":["-y","bitrix24-mcp-bridge"]}'Or add to the file .vscode/mcp.json, in the project
{
"servers": {
"bitrix24-bridge": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"bitrix24-mcp-bridge"
]
}
}
}If the file already exists, add the server inside the servers key.
Run in a terminal
codex mcp add bitrix24-bridge -- npx -y bitrix24-mcp-bridgeOr add to the file ~/.codex/config.toml, for all projects
[mcp_servers.bitrix24-bridge]
command = "npx"
args = ["-y", "bitrix24-mcp-bridge"]If the file already exists, append the block to the end.
Add to the file ~/.gemini/settings.json, for all projects
{
"mcpServers": {
"bitrix24-bridge": {
"command": "npx",
"args": [
"-y",
"bitrix24-mcp-bridge"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
Add to the file ~/.config/devin/mcp_config.json, for all projects
{
"mcpServers": {
"bitrix24-bridge": {
"command": "npx",
"args": [
"-y",
"bitrix24-mcp-bridge"
]
}
}
}If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.
Formerly Windsurf.
Add to the file cline_mcp_settings.json, for all projects
{
"mcpServers": {
"bitrix24-bridge": {
"command": "npx",
"args": [
"-y",
"bitrix24-mcp-bridge"
]
}
}
}If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.
Add to the file .roo/mcp.json, in the project
{
"mcpServers": {
"bitrix24-bridge": {
"command": "npx",
"args": [
"-y",
"bitrix24-mcp-bridge"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
A fork of Roo Code, same .roo folders.
Add to the file opencode.json, in the project
{
"mcp": {
"bitrix24-bridge": {
"type": "local",
"command": [
"npx",
"-y",
"bitrix24-mcp-bridge"
]
}
}
}If the file already exists, add the server inside the mcp key.
Add to the file ~/.config/zed/settings.json, for all projects
{
"context_servers": {
"bitrix24-bridge": {
"command": "npx",
"args": [
"-y",
"bitrix24-mcp-bridge"
]
}
}
}If the file already exists, add the server inside the context_servers key.
Add to the file .codeassistant/mcp.json, in the project
{
"mcpServers": {
"bitrix24-bridge": {
"command": "npx",
"args": [
"-y",
"bitrix24-mcp-bridge"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
Run npx -y bitrix24-mcp-bridge setup to configure the portal and build the extension, load ~/.bitrix24-mcp-bridge/extension/ as an unpacked extension in chrome://extensions with Developer mode on, keep the portal tab open, and register the server with claude mcp add bitrix24-bridge -s user -- npx -y bitrix24-mcp-bridge.
Other ways from the author
npx -y bitrix24-mcp-bridge setupThe first run creates a token, config.json and the extension in ~/.bitrix24-mcp-bridge/. After that, load the extension in chrome://extensions manually.
This is third-party code. Review the repository files before installing.
What it does
Instead of the official REST webhook, the bridge reads the user's live session through a browser extension: the agent talks to a local daemon over stdio via a unix socket, the daemon reaches the extension over a token- and Origin-checked WebSocket on 127.0.0.1, and the extension makes requests against the open portal tab with a fresh sessid and cookies. This gives the agent access to tasks, projects and chats at the regular user's permission level, with no webhook and no portal admin rights. Setup via npx bitrix24-mcp-bridge setup generates a shared token and config, and two manual steps remain: loading the unpacked extension in chrome://extensions and keeping a logged-in portal tab open.
Who it is for. For Bitrix24 users without admin rights who need an MCP without creating a portal webhook.
Good fit when
- You have no admin rights to create a webhook or a local app
- Access at your own account's level is enough, no shared service token needed
- You need several portals configured at once
Not a fit when
- You need a stable service without an open browser tab and a running daemon
- Your company bans developer-mode browser extensions
- You need the official REST webhook with predictable app-level access
Example request
Show my Bitrix24 tasks and a task card with sprint and story-point infoLimitations
It works only while a logged-in portal tab is open in the browser and the daemon is running; it is not an always-on service. The extension loads in developer mode manually, and while file updates are automatic, reloading the extension in chrome://extensions still needs a manual click. Bun is needed only by maintainers, not end users. Access is limited to the portal's regular user permissions rather than a service webhook.
How to disable. Remove the server from your MCP client with claude mcp remove bitrix24-bridge, stop the daemon (pkill -f -- --daemon), and remove the extension in chrome://extensions.
MCP
- Transport
- stdio
- Authentication
- API key
Security check
- It acts as the logged-in user through their live session
- Some tools and the generic bitrix_call perform mutating operations
- The extension loads in developer mode and gets access to the portal tab
README in short
The Russian README carefully explains the bridge architecture: stdio, a unix socket, a token- and Origin-checked WebSocket, and the tab's live session. It covers a quick start via npx setup, a portal reconfiguration menu, automatic updates to the method catalog and extension files with one remaining manual step, multi-portal support, and a table of typed tools for tasks, projects and chats with mutating operations flagged.
FAQ
Do I need a webhook or admin rights?
No, the bridge works through the browser's live session at the regular user's permission level.
What if the portal stops responding?
bitrix_status shows the connection state; usually you need to reopen the portal tab or reload the extension in chrome://extensions.
Related
An MCP server with n8n node and template knowledge: the agent picks nodes, validates configs and, with API access, creates workflows in your n8n
Zapier's official MCP plugin: the agent gets actions across thousands of apps through your Zapier account
Awesome Claude Skills by Composio
Awesome Claude Skills
A curated list of Claude skills and plugins, plus Composio's own automation skills for 78 SaaS apps
A plugin and CLI catalog for agents: generates command-line interfaces for GUI apps like GIMP and Blender and installs ready ones via CLI-Hub