mcp-1c-platform-tools

Based on the available evidence, this is best judged as an MCP integration layer for 1C development, not a general AI coding product and not a standalone IDE. A more accurate analogy is a bridge between 1C: Platform Tools and agents running in VS Code or Cursor, exposing 1C-side capabilities through IPC.

In practical terms, the GitHub repository explicitly positions it as an MCP server for the 1C: Platform Tools extension, targeting Visual Studio Code / Cursor agents. That supports a narrow but credible conclusion: it is meant to connect agent workflows into the 1C toolchain. It does not, from current evidence, prove strong out-of-the-box code generation, debugging, or enterprise delivery capabilities. The repo supports positioning; usability still lacks broader hands-on validation.

On cost and adoption friction, the evidence only supports calling it open source. There is no official pricing, hosted offering, or API fee information in the sources, so total cost cannot be claimed. Conservatively, the main cost is integration effort: understanding 1C: Platform Tools, MCP, VS Code/Cursor agent setups, and IPC-based wiring.