SkillFoxx

CodePilot1C for 1C:EDT

CodePilot1C (EDT plugin)

A 1C:EDT plugin with a built-in MCP Host: an agent gets typing, metadata and the EDT model directly, not by parsing XML files

  • 159 ★ on the repository
  • Last commit
  • AGPL-3.0
PluginEditors’ pick

Broad access

Why this level

  • The MCP Host can be configured to auto-allow all mutating tools with no confirmation
  • Access includes a runtime debugger and profiler that can affect configuration execution
All reasons and checks
Russian stack

ondysss/codepilot1c-edtAuthor:ondysss

Install

Manual install

claude mcp add --transport http -s user codepilot1c http://127.0.0.1:8765/mcp

After enabling the MCP Host in the plugin settings or via 1cedt.ini flags.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • The MCP Host can be configured to auto-allow all mutating tools with no confirmation
  • Access includes a runtime debugger and profiler that can affect configuration execution

This is third-party code. Review the repository files before installing.

What it does

CodePilot1C installs as a regular Eclipse RCP/OSGi plugin in 1C:EDT and starts an inbound MCP Host over HTTP on port 8765, with OAuth 2.1 authorization or a fallback Bearer token. Claude Code, Cursor and Codex agents connect to this endpoint and get capabilities the plugin builds through its understanding of the EDT model rather than by textually parsing files: BSL typing, metadata, forms, SKD, roles, diagnostics, a debugger and runtime profiler, running YAxUnit. Separately there is a standalone CLI with an interactive shell (java -jar codepilot-cli.jar shell) that can run through EDT's active LLM provider (connected mode) or its own OpenAI-compatible provider (standalone mode), asks for confirmation on risky and mutating MCP tools, and stores redacted session transcripts locally.

Who it is for. For 1C developers who work in EDT and want an agent to understand the configuration model as precisely as EDT itself does, not approximately from files.

Good fit when

  • Development happens in 1C:EDT and you need agent MCP access to typing, metadata, forms and SKD
  • You need to run YAxUnit tests and the profiler through an agent
  • You want to gate mutating agent actions behind explicit confirmation via the interactive shell

Not a fit when

  • Development happens in the Configurator, not EDT: the plugin is built specifically for EDT
  • You plan to embed or redistribute the plugin's code in a closed product: the AGPL-3.0 license requires source disclosure
  • You lack JDK 17+ to build or run the CLI

Example request

Use CodePilot1C to find every place a deprecated method is called and show them with precise parameter typing

Limitations

The AGPL-3.0 license imposes copyleft requirements on derivatives and network use. The README's example for auto-starting the MCP Host sets defaultMutationDecision=ALLOW and exposedTools=*, which permits all mutating tools with no confirmation if configured that way; a narrower policy is advisable for safe use. Updating the plugin between incompatible versions requires a manual p2 director procedure with backups, and direct reinstallation may fail to resolve due to singleton bundles.

How to disable. Disable the MCP Host in Preferences, 1C Copilot, MCP Host, or remove the plugin via Help, About 1C:EDT, Installation Details, Uninstall.

FAQ

Is a separate LLM API key needed for the CLI?

Not necessarily: connected mode uses the LLM provider already configured in EDT through a broker, without reading its key directly.

Can dangerous agent actions be blocked by default?

Yes, the interactive shell asks for confirmation on risky and mutating tools unless the defaultMutationDecision policy is explicitly set to ALLOW.

How is CodePilot1C different from other 1C:EDT agent setups?

The plugin installs in 1C:EDT as a regular Eclipse plugin and starts an inbound MCP Host over HTTP on port 8765 with OAuth 2.1 or a Bearer token. The agent gets typing, metadata and the EDT model directly rather than parsing XML.

How do I set up 1C EDT with CodePilot1C?

Install the plugin in 1C:EDT, enable the MCP Host on port 8765 and connect Claude Code, Cursor or Codex over HTTP. Instructions are in the install block and the repository. Risk is high because the agent sees your configuration.

Discussion

No questions or reviews yet.

All 1C:Enterprise tools
Russian stack

An OSGi plugin runs an HTTP MCP inside 1C:EDT, giving an agent the live model: metadata, BSL with unsaved edits, debugging and headless infobase updates

MCP serverBroad access9
Russian stack

An MCP server inside 1C:EDT: the agent works with code and metadata through the IDE's semantic model, validators and debugger

PluginBroad access29
Russian stack

A 1C:EDT plugin that gives agents projects, errors, BSL analysis, form screenshots, metadata refactoring and infobase launch over MCP

MCP serverBroad access333

EDT MCP

EDT_MCP

Russian stack

A 1C:EDT plugin that runs an MCP server inside the IDE: projects, modules, metadata, forms, DCS, debugging and infobase deploy

PluginBroad access17
Russian stack

A 1C:EDT plugin that gives agents the live project model over MCP: reading, refactoring, builds, infobase operations and debugging

MCP serverBroad access30
Russian stack

An MCP server for 1C:EDT with its own bridge plugin: 65 tools for metadata, BSL, debugging, forms, extensions and safe database operations

MCP serverExtended access2

README in short

The README describes installation via an update site or an offline ZIP, a detailed procedure for updating between incompatible versions through p2 director with backups and diagnostics, the interactive CLI shell with connected/standalone/auto modes and a confirmation system for mutating tools, building via Maven with Tycho, the inbound MCP Host with OAuth 2.1 and auto-start via 1cedt.ini, configuration examples for Claude Code, Cursor and Codex, and links to Infostart articles on using CodePilot1C and the Qwen Code CLI.

README badge

Report a problem