technique102.aitools MCP
A 1C-Bitrix module that runs an MCP server inside the project: infoblocks, HL blocks, routes, agents and console commands for AI development
- 6 ★ on the repository
- Last commit
Extended access
Why this level
- Runs PHP code inside the project environment
- Exposes the site's data structure and settings to the agent
Install
- Works in
- Services
Manual install
{
"mcpServers": {
"Technique102AiTools": {
"command": "php",
"args": ["#Путь в системе до корня проекта#/local/technique102.aitools/tools/server.php"]
}
}
}Use when PHP runs locally.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Runs PHP code inside the project environment
- Exposes the site's data structure and settings to the agent
This is third-party code. Review the repository files before installing.
What it does
The module installs into a 1C-Bitrix project's /local/modules and tells the agent about the site itself. The agent gets PHP and platform versions, routes and console commands, infoblock types and infoblocks with all properties, HL blocks with fields and scheduled agents. With that data the agent writes code against the project's real structure. Other modules can add their own tools via module settings or the OnBuildMcpServerToolsList event.
Who it is for. PHP developers of 1C-Bitrix sites who write code with an AI agent.
Good fit when
- The agent needs infoblocks and their properties before writing a component
- You need to understand an unfamiliar 1C-Bitrix project quickly
- You want to expose your own module's tools to the agent
Not a fit when
- The project is cloud Bitrix24 rather than 1C-Bitrix CMS
- The platform is older than 24.0 or PHP is below 8.2
Example request
Show the catalog infoblock properties and write a product query filtered by brandMCP
- Transport
- stdio
- Authentication
- not required
Limitations
Requires PHP 8.2 and 1C-Bitrix 24.0 or newer. Built-in tools only read the project structure; tools for standard modules and guidelines are still planned. The server runs via local php or inside a Docker container, so the agent needs access to the project environment. The repository has no license.
How to disable. Remove the Technique102AiTools block from the MCP config and uninstall the module in the 1C-Bitrix admin panel.
FAQ
Does the module change site data?
Built-in tools only read: versions, routes, commands, infoblocks, HL blocks and agents. What your added tools do depends on your code.
How do I add my own tool?
Create a PHP class with methods marked by the McpTool attribute and register it in your module's .settings.php or via an OnBuildMcpServerToolsList handler.
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
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
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
AI toolkit for 1C-Bitrix development
bitrix-ai-toolkit
A set of rules, skills, linters and an MCP profile for AI development on 1C-Bitrix, with one core shared across Claude Code, Codex and Gemini CLI
Bitrix Framework code indexer
Bitrix MCP
A local, token-free MCP indexer for 1C-Bitrix projects: symbols, events, ORM, a dependency graph and optional DB access
README in short
The Russian README covers requirements, installing the module via the admin panel and registering the MCP server in an editor two ways: docker exec or local php. It has a table of nine tools. It explains in detail how to extend the server with your own tools via module config or an event, with PHP examples. It ends with a roadmap: tools for standard modules, guidelines, skills and subagents.