1C managed forms MCP server
1c-formsserver
An MCP with 18 tools for generating, validating and converting 1C managed forms between the Configurator, Managed and EDT formats
- 9 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- A local HTTP server generates, converts and validates 1C form files
- Does not write to the 1C database, the endpoint has no auth by default
Install
- Works in
- Services
Manual install
docker compose up -dThe recommended method; the server comes up on port 8011.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- A local HTTP server generates, converts and validates 1C form files
- Does not write to the 1C database, the endpoint has no auth by default
This is third-party code. Review the repository files before installing.
What it does
The server understands three 1C form description formats: the Configurator's Form.xml, Managed, and EDT's Form.form, detects the format automatically from the namespace, and converts between them while preserving semantics, including DataPath and type mapping. It can generate a standard form from a template (a catalog item, a document, a data processor), from an arbitrary JSON spec, or straight from an object's metadata when an external EDT MCP is connected. Validation checks id uniqueness, DataPath-to-attribute binding, and structure specific to each format. A separate example database searches similar forms by text or by vector, and the EDT integration adds fetching an object's attributes and a screenshot of the form from the WYSIWYG editor.
Who it is for. For 1C developers who want to generate and move managed forms between the Configurator and EDT without hand-editing XML.
Good fit when
- You need to quickly generate a standard catalog or document form from a description
- You need to move a form between the Configurator and EDT while keeping its structure
- You need to validate a form before saving it into the project, including EDT-specific checks
Not a fit when
- You want to auto-generate a form straight from object metadata: that requires a separately running EDT MCP
- The form has custom form logic (event handlers) that the generator does not reproduce
- You need a form screenshot without a running EDT WYSIWYG editor
Example request
Generate a form for the CustomerOrder document with header fields Date, Number, Counterparty and a Goods table in the EDT formatMCP
- Transport
- http, sse
- Authentication
- not required
Environment variables
EDT_ENABLED- Enables integration with an external EDT MCP Server, false by default.
EDT_MCP_URL- Address of the EDT MCP server, defaults to http://localhost:9999/sse.
Limitations
The EDT integration (fetching object metadata, generating from metadata, form screenshots) needs a separately running EDT MCP Server and EDT_ENABLED=true; without it, only template or spec-based generation and conversion are available. Vector search over example forms is an optional sentence-transformers dependency, installed separately with the [search] extra. Converting between managed and edt goes through an intermediate logform format rather than directly.
How to disable. Stop the container with docker compose down or the python -m mcp_forms process, and remove the 1c-forms entry from your MCP client settings.
FAQ
Does anything need to be called before generating the first form?
Yes, the README requires calling get_form_prompt at the start of a session, otherwise the model doesn't know the valid Form.xml tags.
Can managed be converted directly to edt?
No, the README notes the managed-to-edt route goes through an intermediate logform format.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsA Docker server with a read-only core and pluggable modules: metadata, code, forms and relations of several 1C configurations through one MCP contract
A toolset for 1C: visual preview of forms and templates like in the Configurator, plus an MCP server for an agent to edit forms and build templates from Excel
A 1C-extension MCP server with 93 tools for reading, writing, posting and administering ERP, Trade Management, UPP and Accounting
An MCP server for 1C:EDT with its own bridge plugin: 65 tools for metadata, BSL, debugging, forms, extensions and safe database operations
An MCP server and portable admin tool for analyzing an exported 1C XML configuration: object listing, metadata structure, code search
A native component that runs a full MCP server inside 1C: tools, resources and prompts are written in BSL, while a DLL handles the protocol
README in short
The README describes a FastMCP server with 18 tools grouped into generation, validation, conversion, schema and reference, example search, and EDT integration. It gives a comparison table of the three form formats, example parameters for each tool, four typical usage scenarios, a configuration table of environment variables, the project structure, and a dependency list including the optional search extra. It notes 91 tests. MIT license.