MCP adapter for 1C-Bitrix
MCP-адаптер для 1С-Битрикс
The dimkox.mcp module for 1C-Bitrix: the site exposes infoblocks and orders to an agent over MCP within user permissions, writing disabled
- 1 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The module gives the agent access to a production site: the catalog and, when enabled, orders and users with personal data
- With writing enabled the agent creates and edits infoblock elements on a live site
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/mcp-adapter-dlya-1s-bitriksDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The module gives the agent access to a production site: the catalog and, when enabled, orders and users with personal data
- With writing enabled the agent creates and edits infoblock elements on a live site
This is third-party code. Review the repository files before installing.
What it does
The `dimkox.mcp` module installs on a 1C-Bitrix site like any solution from "Marketplace, Installed solutions" and turns site functions into abilities. The adapter exposes them to an agent as MCP tools, resources and prompts. The idea comes from the WordPress MCP Adapter; the code is written from scratch for Bitrix. Read abilities are on out of the box: `main-current-user`, `iblock-list-iblocks`, `iblock-list-sections`, `iblock-search-elements` and `iblock-get-element`, plus the `bitrix://site/info` resource with domains and core version. Switched off until an administrator enables them: creating and editing infoblock elements, user search, shop orders and the `iblock-describe-element` prompt that asks for a sales description from element data. The agent acts as a specific user through a `bxmcp_...` token. Reads go through `CHECK_PERMISSIONS`, writes are checked against infoblock rights. Connection works over HTTP at `/bitrix/tools/dimkox.mcp/index.php` or locally over stdio through `cli/stdio.php`. Other modules can add their own abilities.
Who it is for. Developers and administrators of 1C-Bitrix sites who want to give an agent access to the catalog and orders with the same permission model as staff.
Good fit when
- A content manager asks to find products in an infoblock by name and show their properties
- A sales description has to be drafted from catalog element data, with the draft saved inactive for review
- A shop manager wants to see orders in the statuses they are allowed to view
- The agent runs on the site server and a remote address is unwanted, so stdio is needed
- A custom module has functions worth exposing to an agent through a single ability registry
Not a fit when
- Your site runs in Bitrix24 cloud: the module installs on boxed 1C-Bitrix with access to `/local/modules/`
- You are on PHP below 8.1: the module relies on D7 ORM and modern PHP
- You need writes to file properties or to infoblocks with document flow or business processes: the agent is barred from them
- You want help with the core API rather than access to site data: core indexers such as `bitrix-mcp` cover that
Example request
Find catalog infoblock products with the word "kettle" and show the properties of the first one without changing anything.MCP
- Transport
- http, stdio
- Authentication
- key is optional
Environment variables
BITRIX_MCP_TOKENsecret- Token like bxmcp_..., needed for local stdio launch.
Limitations
PHP 8.1 or newer and the `main` module with D7 ORM are required. The `iblock` and `sale` modules are optional, but their abilities appear only when the modules are installed. Copy the `dimkox.mcp` folder to `/local/modules/` and install the module through the admin interface.
The agent edits only string, number, list and element or section link properties. File properties are blocked, and property codes listed in settings, such as purchase price, stay invisible to the agent. Writing needs both the ability checkbox and the global "Allow data changes" switch.
The token is shown once and only its SHA-256 hash stays in the database. Give the token to a dedicated user with minimal rights rather than an administrator.
How to disable. Turn the MCP server off on the module's Settings tab, revoke tokens on the Tokens tab, or uninstall the module from Installed solutions.
FAQ
How do I connect 1C-Bitrix to Claude Code over MCP?
Install the `dimkox.mcp` module, enable the server, issue a token and run `claude mcp add --transport http bitrix https://your-site.ru/bitrix/tools/dimkox.mcp/index.php --header "Authorization: Bearer bxmcp_YOUR_TOKEN"`. For Cursor put the URL and header in `.cursor/mcp.json`.
What will the agent see right after installation?
Nothing. The server is off and only abilities that an administrator ticked on the Abilities tab are visible. Infoblock reading is on by default, while writing, users and orders are off.
Can the agent see unpublished products?
Only if the token's user has the "view in admin" right or higher, as in Bitrix itself. Inactive and not yet published elements are hidden otherwise.
How do I run the adapter locally without a public address?
Use stdio: the command `php /var/www/site/local/modules/dimkox.mcp/cli/stdio.php --root=/var/www/site` with `BITRIX_MCP_TOKEN` in the environment. This is how Claude Desktop on the same server works, for example.
How are the token and requests protected?
Only a token hash is stored, tokens can have an expiry and be revoked at any time. Authorization uses a Bearer header without cookies, so CSRF is impossible. The Origin header of browser clients is checked against the domains in site settings.
Discussion
No questions or reviews yet.
Related
All 1C-Bitrix toolsA 1C-Bitrix CMS module that turns the website itself into an MCP server exposing infoblocks and the user profile via tokens
MCP module for 1C-Bitrix Site Manager
wise108.bsm
A module for 1C-Bitrix Site Manager that runs an MCP right on the CMS server for working with infoblock content from Cursor and Claude Desktop
Read-only MCP server for 1C-Bitrix
MCP-сервер для 1С-Битрикс (только чтение)
A 1C-Bitrix module with 35 read-only MCP tools: catalog, orders, reports, code files and SQL, with per-group access rights
Delight MCP module for 1C-Bitrix
delight.mcp
A 1C-Bitrix module with an MCP server: the agent inspects the site environment, searches core functions, and can run PHP, shell and SQL on the server
A 1C-Bitrix module that runs an MCP server inside the project: infoblocks, HL blocks, routes, agents and console commands for AI development
A reference to your own 1C-Bitrix API for an agent: a core index with module versions so it stops mixing methods from different versions
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| MCP adapter for 1C-Bitrix (this card) | no | key is optional | 1 | |
| Bitrix24 REST API documentation MCP | yes | not required | 7 | a REST method reference rather than access to site data |
| Bitrix Agent Skill | no | 22 | a skill with Bitrix guidance, with no connection to a live site |
README in short
The README covers installation into `/local/modules/`, connecting Claude Code, Cursor and local stdio, the list of abilities with defaults, security measures and adding custom abilities. License MIT, PHP 8.1 required.