1C Platform Extension Pack
A VS Code and Cursor extension pack for 1C development: platform tools, an MCP bridge to them, and BSL syntax support
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- MCP tools launch the 1C configurator and debugging commands in the developer's environment
- The extension talks over IPC to a local process that has access to the project
Install
Manual install
Install the yellow-hammer.1c-platform-extension-pack extension pack in VS Code or Cursor from the Marketplace or Open VSX, enable IPC in 1C Platform Tools, and connect to the yellow-hammer.mcp-1c-platform-tools MCP server.
This is third-party code. Review the repository files before installing.
What it does
The pack installs three extensions in one go: 1C Platform Tools adds a project panel, a command tree, configurator launch and debugging, a TODO list and vrunner integration; 1C Platform Tools MCP exposes those same commands to Cursor and VS Code agents over MCP via IPC; Language 1C (BSL) from 1c-syntax provides syntax highlighting, completion and diagnostics through the BSL Language Server. It installs like a regular extension pack from the VS Code Marketplace or Open VSX, and all three extensions come along automatically.
Who it is for. For 1C developers who work in VS Code or Cursor and want to give an agent access to platform commands through MCP.
Good fit when
- You develop 1C configurations in VS Code or Cursor and want one bundle instead of installing three extensions by hand
- You need an agent to call 1C Platform Tools commands (launching the configurator, debugging) via MCP
- You need BSL syntax highlighting and diagnostics right in the editor
Not a fit when
- Development happens in EDT or the 1C Configurator, not VS Code/Cursor
- You do not need an agent's MCP access to platform commands, just BSL highlighting is enough
Example request
Launch the 1C configurator and show the TODO list for the current configuration via 1C Platform ToolsLimitations
The MCP part requires the 1C Platform Tools extension to be installed with IPC enabled, and the pack's README does not detail IPC setup. The three bundled extensions are developed in separate repositories, so bug reports for each go to their own place. VS Code 1.60.0 or newer is required.
How to disable. Remove the extension pack from VS Code or Cursor, optionally keeping only the specific extensions you still need.
Security check
- MCP tools launch the 1C configurator and debugging commands in the developer's environment
- The extension talks over IPC to a local process that has access to the project
README in short
The README describes the three bundled extensions with links to the Marketplace, Open VSX and their repositories, lists each one's capabilities and requirements (VS Code 1.60+), and points to separate issue trackers for bugs in specific extensions. MIT license.
FAQ
Can the extensions be installed separately?
Yes, the pack just groups three independent extensions from the same publisher for convenient installation.
Does BSL highlighting need IPC?
No, IPC is only needed by the MCP extension to talk to 1C Platform Tools; BSL highlighting works on its own.
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