1C Platform Extension Pack plugin

A VS Code and Cursor extension pack for 1C development: platform tools, an MCP bridge to them, and BSL syntax support

  • 28 ★ on the repository
  • Last commit
  • MIT
Plugin

Extended access

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
All reasons and checks
Russian stack

yellow-hammer/vscode-1c-platform-extension-pack

Install

Manual install

Text for your agent

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.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • 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

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 Tools

Limitations

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.

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.

How is the 1C platform extension pack different from standalone extensions?

The pack installs three extensions with one command: 1C Platform Tools (project panel, command tree, configurator, debugging, TODO, vrunner), 1C Platform Tools MCP and BSL highlighting. It works in VS Code and Cursor.

How do I install the 1C extension pack for VS Code and can I install them separately?

Install the pack from the VS Code or Cursor extension marketplace and all three extensions arrive. They can also be installed one by one. BSL highlighting needs no separate IPC channel.

Discussion

No questions or reviews yet.

Russian stack

A VS Code and Cursor extension that exposes 1C: Platform Tools commands to the agent: tests, launch profiles, configuration builds and infobase work

MCP serverExtended access45Repository stars
Russian stack

A VS Code and Cursor extension for 1C: vanessa-runner commands, metadata, debugging, tests and skills for AI agents.

PluginExtended access241Repository stars
Russian stack

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

MCP serverExtended access22Repository stars
Russian stack

A 1C extension that runs an MCP server inside the infobase: metadata tools out of the box and custom tools in BSL

MCP serverBroad access573Repository stars

1C AI development environment

1C AI Development Environment

Russian stack

1C development environment with an MCP server offering 10 tools: 11 BSL analyzers, JSON DSL to XML, dependency graph, and EPF build without 1C

MCP serverBroad access18Repository stars
Russian stack

Ten MCP servers for 1C development: platform reference, targeted object dump and load, COM, storage, file search and BSL Language Server

MCP serverBroad access1Repository stars

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.

README badge

Report a problem