EDT MCP Setup Plugin for Codex
A local Codex plugin that installs EDT-MCP into 1C:EDT on Windows and sets up a ready MCP connection on localhost
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- Runs a PowerShell script that edits EDT settings files
- Enables a network MCP endpoint on localhost with no built-in authentication in EDT-MCP
Install
Manual install
codex plugin marketplace add free-archer/edt-mcp-plagin
codex plugin add edt-mcp-plagin@edt-mcp-plaginStandard plugin install for Codex.
This is third-party code. Review the repository files before installing.
What it does
The plugin is not an MCP server itself; it automates connecting the third-party EDT-MCP server (the DitriXNew project) to the 1C:EDT development environment on Windows. On the agent's command it runs a PowerShell script that finds the installed 1cedt.exe, installs EDT-MCP via p2 director, adds the nativeFormBufferedLayoutRender flag to 1cedt.ini, and optionally enables MCP auto-start on a chosen port. The plugin also ships a .mcp.json with the ready http://localhost:8765/mcp address and two Codex skills for installing and reconfiguring it.
Who it is for. For 1C developers on Windows who use Codex and want to connect EDT-MCP to their EDT with one phrase instead of manual setup.
Good fit when
- Codex runs on Windows with 1C:EDT installed and you need to bring up EDT-MCP quickly
- You need to change the port or token of an already configured EDT-MCP without hand-editing files
- You want ready Codex skills with step-by-step install and diagnostics
Not a fit when
- You are not on Codex or not on Windows: the plugin targets this exact pair
- You need EDT-MCP itself: its logic lives in DitriXNew/EDT-MCP, this repo only wires up the connection
Example request
Install EDT-MCP into my EDT and set it to auto-start on port 8766Limitations
Works only on Windows and only with Codex, and does not fit other agents or OSes. The plugin does not edit the global ~/.codex/config.toml and does not guess the EDT workspace path, which must be passed explicitly. It depends on the external EDT-MCP project, so its setup script can go stale if that API changes.
How to disable. Remove the plugin with codex plugin remove edt-mcp-plagin@edt-mcp-plagin and codex plugin marketplace remove edt-mcp-plagin.
Security check
- Runs a PowerShell script that edits EDT settings files
- Enables a network MCP endpoint on localhost with no built-in authentication in EDT-MCP
README in short
The README describes a local Codex plugin for Windows that simplifies connecting EDT-MCP: it ships a ready .mcp.json on localhost:8765, adds install and reconfigure skills, and includes a PowerShell script that finds 1cedt.exe, installs EDT-MCP via p2 director, edits 1cedt.ini, and can set up auto-start with a chosen port and token. It also states what the plugin does not do: it does not touch Codex's global config or guess the workspace.
FAQ
Is the plugin itself an MCP server?
No, it installs and configures the third-party EDT-MCP by DitriXNew, providing only the .mcp.json and install skills.
Does it work on macOS or Linux?
No, the PowerShell script and all logic target Windows only.
Related
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Skills for real engineers by Matt Pocock
Skills For Real Engineers
Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
Reference MCP servers
Model Context Protocol servers
Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything