SkillFoxx

AshybulakStroy MCP 1C Bridge

A policy-gated read-only MCP server for 1C Accounting for Kazakhstan data via OData: stock, payments, receivables

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

Extended access

Why this level

  • Reads financial data: payments, stock and counterparties' receivables
  • Recommends but does not technically enforce a separate read-only 1C OData user
All reasons and checks
Russian stack

ashybulakstroy/ashybulakstroy-mcp-1c-bridgeAuthor:ashybulakstroy

Install

Manual install

python -m venv .venv && pip install -e . && cp .env.example .env

Install dependencies and prepare .env with the OData endpoint.

Access and checks

How we review

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

  • Reads financial data: payments, stock and counterparties' receivables
  • Recommends but does not technically enforce a separate read-only 1C OData user

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

What it does

The server talks to published OData entities of 1C Accounting for Kazakhstan 3.0 and gives the agent read-only tools: metadata search and description, stock and low-stock items, incoming and outgoing payment reports, top customers and suppliers, overdue debtors, and reconciliation of the fetched data against the text of an official 1C report. Every tool call goes through a policy decision engine from config/policy.yaml: unknown and forbidden tools are blocked, risk levels L3 and L4 are always blocked, and every call is written to an audit/audit.jsonl log.

Who it is for. For accountants and business owners on 1C Accounting for Kazakhstan who need a safe read-only report on stock and money through an agent.

Good fit when

  • You want to ask the agent who was paid or who has not paid an invoice, for a period
  • You need to check stock without manually building a report
  • You need a transparent access policy with a log of every call

Not a fit when

  • You need to post or change a document: the server only reads data
  • You need standard Russian 1C Accounting without the Kazakhstan adaptation

Example request

Show who has not paid an invoice within 3 days, and the top customers by incoming payments for April

MCP

Transport
stdio
Authentication
not required

Environment variables

ONEC_ODATA_URL required
OData endpoint of 1C Accounting for Kazakhstan.
ONEC_USERNAME required
1C OData user, ideally with a read-only role.
ONEC_PASSWORD required, secret
Password of the OData user.

Limitations

Built for 1C Accounting for Kazakhstan 3.0 and its standard OData interface; there is no separate adapter for the Russian edition. Stock and money reports are built by OData heuristics and should be checked against official 1C reports. Overdue and typical payment terms use a managerial FIFO method, not an official accounting register. The project carries a lot of internal development documentation, a sign of an early, not fully settled state.

How to disable. Remove the ashybulakstroy-1c server from your MCP client configuration and stop the process.

FAQ

Can the server post or delete a document?

No, all write and posting operations are forbidden by policy at the Phase 1 Secure MVP level, including post_document_validated.

What does Secure Mode do in practice?

Every tool call is checked against an allowlist and risk level in policy.yaml, unknown calls are denied, and the result passes an output filter before returning to the agent.

Discussion

No questions or reviews yet.

All 1C:Enterprise tools
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 access47
Russian stack

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

MCP serverBroad access13
Russian stack

A strictly read-only MCP server on a 1C HTTP service: 39 tools for metadata, queries, accounting and reports on any configuration

MCP serverExtended access

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 access4
Russian stack

An MCP server for 1C-Fresh over standard OData: invoices, sales, counterparties, working around known 1C-Fresh OData quirks and the 22 percent VAT

MCP serverBroad access1

README in short

The README describes the product's role as a read-only Secure Mode bridge to 1C Accounting for Kazakhstan, explains an L0-L4 risk model, a capability registry, the policy format in config/policy.yaml, an append-only audit log, and an output filter that masks IIN and bank account numbers. It lists money scenarios for payments and receivables, and reconciliation of stock against the text of an official 1C report.

README badge

Report a problem