1C: Platform Tools MCP
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
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
Install 1C: Platform Tools: Marketplace, Open VSX
Install 1C: Platform Tools MCP: Marketplace, Open VSX
Open a 1C project (folder with
packagedef).
Related MCP server: xbsl-mcp
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:
Command Palette (F1) →
1C: Platform Tools MCP: Configure MCP for Cursor, or in the 1C Tools tree → AI Skills → Configure MCP for Cursor.Reload the window.
Enable the
mcp-1c-platform-toolsserver 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
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.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Build, run, debug, test and ship Chrome, Firefox, Edge and Safari extensions from your AI agent.
Backend platform for AI agents: one agentstack.execute tool runs batched steps over +700 actions (hosting, storage, auth, payments, CRM, app builder).
Build, validate, test-run and publish AIOS workflows from Claude Code, Codex, Cursor or VS Code.
Automate 1,000+ services from any MCP-compatible AI agent: build Applets, run actions and queries.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with 1C:Enterprise databases through natural language, providing metadata retrieval, configuration analysis, and code generation.9-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to lint, search documentation, and perform metadata scaffolding for 1C:Element projects.5,798 PyPI3MIT
- AlicenseNot gradedqualityBmaintenanceEnables LLM agents to explore and search a 1C:Enterprise configuration codebase, including metadata objects, module procedures, call graphs, and semantic similarity search.4MIT
- AlicenseCqualityBmaintenanceEnables AI agents to interactively drive 1C:Enterprise UI through the testing client, including opening forms, clicking buttons, filling fields, and capturing evidence.1296MIT