1C over OData: read-only MCP server

onec-odata-mcp

An npx MCP server that gives Claude read access to a 1C database via standard OData, no Excel exports or hand-built URLs

  • 0 ★ on the repository
  • Last commit
  • MIT
MCP server

Extended access

Why this level

  • Reads 1C data only by default, but writes can be enabled via the ONEC_WRITABLE flag
  • The 1C user password is passed via the MCP client's environment variables
All reasons and checks
Russian stack

pyrfor/onec-odata-mcp

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/onec-odata-mcp

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Reads 1C data only by default, but writes can be enabled via the ONEC_WRITABLE flag
  • The 1C user password is passed via the MCP client's environment variables

This is third-party code. Review the repository files before installing.

What it does

The server connects to a 1C infobase's standard OData interface and turns natural-language questions into queries against catalogs and documents. It works with any configuration that has OData enabled: Accounting, ERP, Trade Management, or custom solutions. Access is read-only by default, with writes enabled explicitly via ONEC_WRITABLE. It caches metadata with a configurable TTL and supports an ONEC_DATABASE hint for the infobase name when there are several.

Who it is for. For 1C developers and analysts who want quick read access to 1C data from Claude without building a custom MCP server from scratch.

Good fit when

  • The configuration already has the standard OData interface published
  • You need fast structured access to catalogs and documents instead of Excel exports
  • A ready npm package without building from source is enough

Not a fit when

  • OData is not published in the infobase and cannot be published
  • You need writes: the server reads only by default, and write mode is enabled separately and not tested for every scenario

Example request

Show all sales documents from last week over 100,000 rubles via 1C OData

MCP

Transport
stdio
Authentication
not required

Environment variables

ONEC_BASE_URL required
URL of the published 1C OData interface.
ONEC_USERNAME required
1C user login for OData.
ONEC_PASSWORD required, secret
1C user password for OData.
ONEC_DATABASE
A hint for the infobase name when there are several.
ONEC_METADATA_CACHE_TTL_MS
Metadata cache TTL in milliseconds, one hour by default.
ONEC_WRITABLE
Enables writes to the infobase; the server is read-only by default.

Limitations

It needs 1C's standard OData interface published, plus a user login and password. The README notes a screenshot or video of the five-minute setup has not been added yet, and some examples are marked TODO. Writes are enabled with the ONEC_WRITABLE flag and need a careful check of the rights of the user the server runs as.

How to disable. Remove the server with claude mcp remove onec-odata, or delete the onec-odata entry from claude_desktop_config.json.

FAQ

Do I need to install anything locally?

No, npx fetches the package on first run; building from source is needed only for development.

Can it write to the infobase?

Not by default, the server is read-only. Writes are enabled via the ONEC_WRITABLE variable.

Discussion

No questions or reviews yet.

1C OData MCP server

1C OData MCP Server

Russian stack

A small Python MCP server that wraps standard 1C Управление предприятием OData read operations into three tools

MCP serverBroad access

1C OData MCP with a JSON cache

MCP сервер для работы с OData 1C

Russian stack

A Python MCP server over 1C OData: reads and changes catalogs and documents, saving everything to JSON files for local analysis without repeat queries

MCP serverBroad access4Repository stars
Russian stack

MCP server for 1C:Enterprise data over OData: receivables, sales, stock and cash, plus document creation and posting behind a separate flag

MCP serverBroad access46Repository stars
Russian stack

A Go MCP gateway between an agent and a 1C HTTP service: references, sales, stock, cash and settlement reporting across several databases

MCP serverExtended access5Repository stars
Russian stack

MCP server for 1C:Enterprise databases over standard OData: catalogs, documents, registers and accounting with no configuration extension

MCP serverBroad access13Repository stars
Russian stack

A PyPI-published read-only MCP server for standard 1C:Enterprise OData 8.3.5+: schema, filtered queries, record lookup by Ref_Key

MCP serverBroad access

README in short

The README states its goal upfront: connect 1C to Claude in five minutes via standard OData instead of manual URLs and Excel exports. It gives two connection methods: the claude mcp add command and manual setup in claude_desktop_config.json, with required ONEC_BASE_URL, ONEC_USERNAME, ONEC_PASSWORD variables and optional ONEC_DATABASE, ONEC_METADATA_CACHE_TTL_MS, ONEC_WRITABLE.

README badge

Report a problem