technique102.aitools
A 1C-Bitrix module that runs an MCP server inside the project: infoblocks, HL blocks, routes, agents and console commands for AI development
Install
{
"mcpServers": {
"Technique102AiTools": {
"command": "php",
"args": ["#Путь в системе до корня проекта#/local/technique102.aitools/tools/server.php"]
}
}
}Use when PHP runs locally.
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 brandLimitations
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.
MCP
- Transport
- stdio
- Authentication
- not required
Security check
- Runs PHP code inside the project environment
- Exposes the site's data structure and settings to the agent
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.
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.
Related
The official FastAPI skill, bundled with the package, teaching agents to write code for the installed version
Official skills and agents from the .NET team: performance, MSBuild, NuGet, upgrades, testing, ASP.NET Core, Blazor and MAUI
Firebase MCP Server
Firebase CLI and MCP Server
Official Firebase MCP server from the Firebase CLI: projects, Firestore, Auth, Crashlytics, Remote Config and function logs
Laravel's official MCP server, guidelines and skills: the agent sees the DB schema, logs and package versions and searches ecosystem docs