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
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.
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 testsLimitations
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.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| ONEC_IPC_HOST | IPC host of the 1C: Platform Tools extension |
| ONEC_IPC_PORT | IPC port |
| ONEC_IPC_TOKEN secret | IPC access token |
Security check
- Runs configuration builds and tests against a local infobase
- Calls editor extension commands over IPC
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.
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.
Related
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Skills for real engineers by Matt Pocock
Skills For Real Engineers
Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
Reference MCP servers
Model Context Protocol servers
Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything