1C: Platform Tools MCP
A VS Code and Cursor extension that exposes 1C: Platform Tools commands to the agent: tests, launch profiles, configuration builds and infobase work
- 42 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Runs configuration builds and tests against a local infobase
- Calls editor extension commands over IPC
Install
- Works in
- Services
Manual install
{
"mcpServers": {
"mcp-1c-platform-tools": {
"command": "node",
"args": ["<путь к каталогу расширения>/out/src/index.js"],
"env": {
"ONEC_IPC_HOST": "127.0.0.1",
"ONEC_IPC_PORT": "40241",
"ONEC_IPC_TOKEN": ""
}
}
}
}Manual setup is needed only when not using the extension's command. ONEC_IPC_* values come from the 1c-platform-tools.ipc settings.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Runs configuration builds and tests against a local infobase
- Calls editor extension commands over IPC
This is third-party code. Review the repository files before installing.
What it does
The extension runs an MCP server that calls 1C: Platform Tools commands in the editor over IPC. The agent can read the 1C environment state, meaning the active launch profile, platform version and infobase path, switch profiles, run tests and build the configuration. In VS Code the server registers automatically. For Cursor the extension creates and updates the project's .cursor/mcp.json and fixes the server path after version updates.
Who it is for. For 1C developers who work in VS Code or Cursor with the 1C: Platform Tools extension.
Good fit when
- You want the agent to run 1C tests and builds from the editor
- You want to switch launch profiles from chat
- A 1C project with packagedef is already open in VS Code or Cursor
Not a fit when
- You work in the Designer or EDT without VS Code
- You need a server that runs without the editor open
Example request
Show the 1C environment state, switch to the test infobase profile and run the testsMCP
- Transport
- stdio
- Authentication
- not required
Environment variables
ONEC_IPC_HOST- IPC host of the 1C: Platform Tools extension
ONEC_IPC_PORT- IPC port
ONEC_IPC_TOKENsecret- IPC access token
Limitations
Works only with the 1C: Platform Tools extension in an open editor. In Cursor the new server is added disabled and must be enabled in MCP settings. With manual setup the path contains the extension version and breaks after updates. The IPC setting in 1C: Platform Tools must be enabled.
How to disable. Uninstall the 1C: Platform Tools MCP extension and remove the mcp-1c-platform-tools entry from .cursor/mcp.json.
FAQ
Do I need to configure anything in VS Code?
No, VS Code registers the server automatically through its MCP server provider.
Why does the server fail with MODULE_NOT_FOUND after an update?
The server path includes the extension version. The extension fixes paths it wrote itself on startup, but a manual path must be updated by hand.
How is 1C: Platform Tools MCP different from other MCP servers for 1C development?
It is a VS Code and Cursor extension that starts an MCP server and calls 1C: Platform Tools extension commands over IPC: environment state, launch profiles, tests, configuration builds and database work.
What do I set up in VS Code and why does the server fail with MODULE_NOT_FOUND after an update?
Install the 1C: Platform Tools extension and open a 1C project. MODULE_NOT_FOUND after an update is usually fixed by reinstalling the extension and restarting the editor. It works in VS Code, Cursor and Copilot.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsA VS Code and Cursor extension pack for 1C development: platform tools, an MCP bridge to them, and BSL syntax support
A ready-made Cursor setup: a live 1C infobase via LN_MCP plus seven Docker containers of MCP_Distr static analysis for code and BSP search
An MCP server that exposes the cloud 1C:Napparnik (1C.ai) assistant and a local BSL Language Server to agents in Cursor and other IDEs
1C AI development environment
1C AI Development Environment
1C development environment with an MCP server offering 10 tools: 11 BSL analyzers, JSON DSL to XML, dependency graph, and EPF build without 1C
A 1C extension built on vladimir-kharin/1c_mcp that adds execution of arbitrary built-in-language code right in the infobase context
A 1C:EDT plugin that gives agents projects, errors, BSL analysis, form screenshots, metadata refactoring and infobase launch over MCP
README in short
The README covers installing two extensions from the Visual Studio Marketplace or Open VSX and opening a 1C project folder. VS Code needs no extra steps, and for Cursor there is a command that writes the project config. Verification is asking for the environment state. It ends with manual setup using ONEC_IPC_HOST, ONEC_IPC_PORT and ONEC_IPC_TOKEN. MIT license.