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
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- Works with form text that the user saves into the project themselves, does not write into a 1C database directly
- The HTTP endpoint has no authorization by default, so network access should be restricted
Install
Manual install
docker compose up -dThe recommended method; the server comes up on port 8011.
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 formatLimitations
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.
MCP
- 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. |
Security check
- Works with form text that the user saves into the project themselves, does not write into a 1C database directly
- The HTTP endpoint has no authorization by default, so network access should be restricted
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.
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.
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