1C: Platform Tools MCP

The MCP server gives the Cursor or VS Code agent access to the commands of the 1C: Platform Tools extension: tests, launch profiles, configuration build, database operations.

Installation

1. Install 1C: Platform Tools: Marketplace, Open VSX

2. Install 1C: Platform Tools MCP: Marketplace, Open VSX

3. Open a 1C project (folder with packagedef).

Related MCP server: bas-mcp-server

Connection

VS Code requires nothing more: the extension registers the MCP server itself.

Cursor does not support the VS Code MCP server provider, so the server is connected via the project's .cursor/mcp.json. The extension creates and updates the file:

1. Command Palette (F1) → 1C: Platform Tools MCP: Configure MCP for Cursor, or in the 1C Tools tree → AI Skills → Configure MCP for Cursor.

2. Reload the window.

3. Enable the mcp-1c-platform-tools server in the MCP settings: Cursor adds a new server disabled.

The command writes the server path and IPC parameters; other servers in the file are preserved. The path contains the extension version, so after an update the entry becomes outdated and the server fails with MODULE_NOT_FOUND. The extension fixes this on startup: it updates the path if it points to a different installation of the same extension. A manually written path (e.g., to a build from source) remains as is.

Verification

Tell the agent 'show the 1C environment status'. The response will include the active launch profile, platform version, and database path. Then you can ask for test runs, profile switching, configuration build.

Documentation

• What to tell the agent

• Tool parameters

Manual configuration

Only needed if the config is set up without the extension. The 1c-platform-tools.ipc.enabled setting must be enabled, the ONEC_IPC_* values are taken from 1c-platform-tools.ipc.*:

{
  "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": ""
      }
    }
  }
}

Extension directory: %USERPROFILE%\.cursor\extensions\yellow-hammer.mcp-1c-platform-tools-<версия>-universal (Windows) or ~/.cursor/extensions/... (macOS, Linux). After each extension update, such a path will have to be edited manually.

The global config (%USERPROFILE%\.cursor\mcp.json) works the same way, but the extension does not update it: for multiple projects, the project file is more reliable.