Mcp 1c Platform Tools

io.github.yellow-hammerPublished by GitHub account yellow-hammerv0.1.5Updated Oct 24, 2026

MCP для команд 1c-platform-tools. Нужно расширение 1c-platform-tools с включённым IPC.

VerifiedSTDIODesktop onlyDatabasesDeveloper Tools

Overview

AI-generated overview

Gives AI coding agents access to 1C: Platform Tools commands in 1C projects, such as running tests, switching launch profiles, and building configurations.

What you can do
This local MCP server exposes the commands of the 1C: Platform Tools extension to agents in VS Code or Cursor. It works with configurator projects, 1C:EDT, and OneScript, covering tests, launch profiles, configuration builds, and database operations. An agent can report the 1C environment state, including the active launch profile, platform version, and database path, and can then be asked to run tests, switch profiles, or build a configuration.
When to use it
Use it when you work on 1C projects in VS Code or Cursor and want the agent to run 1C: Platform Tools commands directly, for example to check environment state, run tests, switch launch profiles, or build a configuration.
Requirements
Desktop only; runs as a local Node.js process via the npm package mcp-1c-platform-tools. Requires the 1C: Platform Tools extension with IPC enabled, and an open 1C project folder containing packagedef. The ONEC_IPC_PORT environment variable is required; ONEC_IPC_TOKEN is optional and taken from the extension settings. VS Code registers the server automatically; Cursor needs a project .cursor/mcp.json file.
Before you install
The server connects to a local IPC endpoint and can run commands that build configurations and work with databases, so agent actions may change project or database state. The optional ONEC_IPC_TOKEN secret is passed via environment variable; keep it out of shared configuration files. The Cursor configuration contains a version-specific extension path that becomes stale after extension updates and can cause MODULE_NOT_FOUND errors.

Installation

In SourceWeft

  1. Open Mcp 1c Platform Tools in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

1C: Platform Tools MCP

[VS Marketplace] [Open VSX] [OpenYellow] [telegram chat] [Ask Devin]

MCP-сервер даёт агенту VS Code или Cursor доступ к командам расширения 1C: Platform Tools в проектах конфигуратора, 1С:EDT и OneScript: тесты, профили запуска, сборка конфигурации, работа с базой.

Установка

  1. Установите 1C: Platform Tools: Marketplace, Open VSX
  2. Установите 1C: Platform Tools MCP: Marketplace, Open VSX
  3. Откройте проект 1С (папка с packagedef).

Подключение

VS Code. Ничего дополнительно не нужно.

Cursor. В палитре команд или в дереве Инструменты 1С → Навыки для AI выполните Настроить MCP для Cursor. Перезагрузите окно и включите сервер mcp-1c-platform-tools в настройках MCP: новый сервер Cursor добавляет выключенным.

После обновления расширения путь к серверу в этом файле обновляется сам. Путь, который вы прописали сами, не меняется.

Проверка

Напишите агенту «покажи состояние окружения 1С». В ответе будут активный профиль запуска, версия платформы и путь к базе. Дальше можно просить прогон тестов, переключение профиля, сборку конфигурации.

Документация

Установка и подключение, параметры инструментов, что писать агенту. На сайте: MCP-сервер.

Настройка вручную

Нужна, только если конфиг заводится без расширения. Сервер запускают из папки проекта.

json
{  "mcpServers": {    "mcp-1c-platform-tools": {      "command": "node",      "args": ["<путь к каталогу расширения>/out/src/index.js"]    }  }}

Каталог расширения: %USERPROFILE%\.cursor\extensions\yellow-hammer.mcp-1c-platform-tools-<версия>-universal (Windows) или ~/.cursor/extensions/... (macOS, Linux).

Source: README.md at commit 5e8d022

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.5LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts