MCP Connector for UPP 1.3
MCP Connector для УПП 1.3
A 1C subsystem for UPP 1.3: an HTTP service with stock, sales, cash and production reports for an external MCP gateway, with verifiable filters
- 0 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The HTTP service exposes financial data: stock, cash, cost, receivables and payables
- Access is governed by a key and scope in the accounts catalog; a role permission mistake widens visible data
Install
- Works in
- Services
Manual install
Merge your UPP 1.3 for Ukraine configuration with the export from ruslan-hut/upp-mcp-connector in the Configurator, create a role from the minimal permission set in the README, set up MCP_УчетныеЗаписи entries with access keys, publish the MCP HTTP service and point your external Go gateway at its address.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The HTTP service exposes financial data: stock, cash, cost, receivables and payables
- Access is governed by a key and scope in the accounts catalog; a role permission mistake widens visible data
This is third-party code. Review the repository files before installing.
What it does
The repo contains not a full configuration but an export of the MCPConnector subsystem: eight metadata objects, an MCP HTTP service as the single entry point, common modules with report business logic, JSON packing and utilities, an accounts catalog with access keys, and a scope permissions enum. The service serves stock, sales, cash, receivables/payables, specification and production reports, each shaped as columns/rows/totals with a list of applied_filters. The key principle: a filter is either applied or the request is rejected with a 400 error; there is no silent ignoring of a filter, nor silently turning an unresolved identifier into an empty result. The actual MCP protocol on the LLM client side is handled by a separate Go gateway, not included in this repo; this is only the 1C side of the integration.
Who it is for. For 1C developers implementing UPP 1.3 for Ukraine who are building an LLM integration through their own MCP gateway and want a ready example of an HTTP layer with carefully handled filters.
Good fit when
- You run a UPP 1.3 for Ukraine database and need an example HTTP layer for integrating with an MCP gateway
- You want an example of 1C reports honestly rejecting an unsatisfiable filter instead of returning a wrong result
- You need a breakdown of where in UPP to source data for stock, sales, cash and production reports
Not a fit when
- You do not run UPP 1.3 for Ukraine: the subsystem references its standard objects and registers and is not self-sufficient
- You need the whole MCP protocol ready-made: the separate Go gateway between the LLM and 1C is not included in this repo
- Your base runs the Russian edition of UPP or another configuration: the register choices are made for this specific Ukrainian accounting setup
Example request
Show inventory stock by warehouse including reserves for the current monthMCP
- Transport
- http
- Authentication
- API key
Limitations
This is not a standalone product but a subsystem export for a specific UPP 1.3 for Ukraine implementation: it needs the actual standard UPP configuration with its objects and registers, a licensed vendor product not included in the repo. The access role is not part of the export and must be created manually from the documented minimal permission set. The account form's handlers are attached as a separate snippet because ordinary forms export as an unreadable binary Form.bin. The MCP protocol itself and the bridge to the LLM client are handled by a separate Go gateway outside this repo. The author explicitly calls the project reference material for their own base, not a universal recipe.
How to disable. Disable or remove the MCPConnector subsystem and its objects in the Configurator, and unpublish the MCP HTTP service.
FAQ
Does it fit the Russian edition of UPP?
The project is built for a specific UPP 1.3 for Ukraine implementation, and its register choices and report logic reflect that accounting setup; they need re-checking for a different edition.
Is this repo enough for the integration to work?
No, you also need the licensed UPP configuration itself, a separately created access role, and an external Go gateway that handles the MCP protocol and is not included in the repo.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsMCP server inside 1C
1c_mcp
A 1C extension that runs an MCP server inside the infobase: metadata tools out of the box and custom tools in BSL
A strictly read-only MCP server on a 1C HTTP service: 39 tools for metadata, queries, accounting and reports on any configuration
MCP server for 1C:Enterprise databases over standard OData: catalogs, documents, registers and accounting with no configuration extension
1C metadata MCP server
1C_MCP_metadata
An MCP server over a 1C extension's HTTP service that exposes configuration metadata, searches objects and validates query syntax
Unified 1C MCP gateway with a dashboard
onec-mcp-universal
A Docker gateway with one address instead of several MCP connections: 1C data, BSL navigation, ITS search via 1C:Napparnik, and a web dashboard
A 1C-extension MCP server with 93 tools for reading, writing, posting and administering ERP, Trade Management, UPP and Accounting
README in short
The README describes the subsystem's composition in detail, the HTTP contract with health, auth/verify, resolve and reports methods, the honest-filter-handling principle, and a data source table for each report explaining why that specific register was chosen. Separate sections give step-by-step installation, the minimal role permission set by object, a note on the external Go gateway outside the repo, and platform specifics: 8.2.13 compatibility mode, Russian BSL identifiers, Cyrillic paths in git. MIT license, though the author stresses the reference nature of the publication.