1C:Enterprise

1C:Enterprise (OData)

This connector reads a 1C:Enterprise 8.3 infobase through the standard OData interface (/odata/standard.odata) that the 1C platform itself publishes on your web server. It works with every configuration built on the platform: 1С:Бухгалтерия предприятия, Управление торговлей, 1С:ERP, Комплексная автоматизация, УНФ, Розница, ЗУП and custom ones, on your own server or with a 1C hosting provider that enables OData. The names of catalogs, documents, registers and fields come from the infobase's own metadata, so they are the ones your configuration uses (usually Russian). Read-only: the connector never creates, changes, posts or deletes anything.

Setup (about 30 minutes, needs your 1C administrator)

1. Publish the infobase on a web server (Apache or IIS with the platform's web server extension modules, platform 8.3.5 or newer). In the Designer: Администрирование > Публикация на веб-сервере (Administration > Publish to web server), give the publication a name in Latin letters, tick Публиковать стандартный интерфейс OData (Publish standard OData interface) and publish. With a 1C hosting provider (1cFresh, cloud rental), ask the provider to enable OData for your infobase.
2. Choose what OData may show. Out of the box the interface exposes no objects. In typical configurations open Администрирование > Синхронизация данных > Настройки стандартного интерфейса OData (or Все функции > Обработки > Настройка стандартного интерфейса OData) and add the catalogs, documents and registers the assistant may read. In other configurations a developer calls УстановитьСоставСтандартногоИнтерфейсаOData().
3. Create a dedicated 1C user for the connector with read-only roles for those objects and the right to use the standard OData interface (the settings form in step 2 can create this user). Its rights are the real boundary: 1C checks them on every call.
4. Check in a browser: open <publication address>/odata/standard.odata/?$format=json and sign in with that user. A JSON list of objects means OData works; an empty list means step 2 is missing.
5. Fill in ONEC_BASE_URL (the publication address without /odata, e.g. https://1c.example.com/trade), ONEC_USER and ONEC_PASSWORD. Cyrillic user names work.

Network: AnythingMCP Cloud reaches only addresses on the public internet, so publish over HTTPS on a public host. For a server inside your network, self-host AnythingMCP there (or connect it through a VPN) and add the host to SSRF_ALLOWED_HOSTS.

How to work

1. onec_enterprise_guide explains names, filters, registers and pitfalls at no cost.
2. onec_enterprise_describe_service lists every published object (entity set) with its keys; onec_enterprise_describe_entity lists its fields and types.
3. onec_enterprise_query reads a catalog, document or tabular section with filter, orderby, select, top and skip, checks field names against the metadata first and reports the total. Use it for lists.
4. onec_enterprise_get_entity reads one object by Ref_Key, with its tabular sections inline.
5. onec_enterprise_get takes an OData path with the query written out, for what the query tool cannot address: the virtual tables of registers (Balance, Turnovers, BalanceAndTurnovers, SliceLast, SliceFirst) and navigation from one object, e.g. a document's Товары.

Object names: Catalog_Номенклатура, Document_РеализацияТоваровУслуг, its tabular section Document_РеализацияТоваровУслуг_Товары, InformationRegister_КурсыВалют, AccumulationRegister_ТоварыНаСкладах, AccountingRegister_Хозрасчетный, ChartOfAccounts_Хозрасчетный, Constant_..., DocumentJournal_.... Every catalog and document row has Ref_Key (a GUID), DeletionMark, and documents also Number, Date and Posted. A reference field Контрагент appears as Контрагент_Key holding the GUID of the referenced object.

Pitfalls: always pass $top and $select on large catalogs and registers. Count only posted documents (Posted eq true) and leave out rows marked for deletion. Dates have no time zone: they are the infobase's local time. Amounts are in the document's currency (see ВалютаДокумента_Key) unless the field says otherwise.