# 1c-odata-mcp [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/evilbruce666/1c-odata-mcp  
**GitHub Stars:** 35  
**npm Downloads (last month):** 1281  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/1c-odata-mcp-2

## Description
MCP-сервер для 1С:Предприятие через OData: данные 1С на естественном языке из любого MCP-клиента (Claude, Cursor, VS Code, локальные модели). Утренняя сводка, дебиторка по срокам, проверка закрытия месяца, акт сверки, карточка счёта, ОСВ; готовые сценарии. Чтение по умолчанию, запись с предпросмотром. | MCP server for 1C via OData.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "1c-odata-mcp": {
    "command": "npx",
    "args": ["-y","1c-odata-mcp"]
  }
}
```

## Documentation

## What 1c-odata-mcp does

1c-odata-mcp exposes 1C:Enterprise data through MCP, using the database's published OData endpoint rather than COM or direct SQL access. It is intended for natural-language work with accounting, sales, inventory, payments, documents, and related reference data.

The server includes workflows for management, sales, and accounting tasks. These include cash and debt summaries, overdue receivables and payables, unpaid customer invoices, reconciliation data by counterparty, account ledger cards, trial balances, accounting postings, sales, taxes, warehouse balances, and document history. It can also inspect month-end closing issues, including unposted documents, red balances, selected account balances, depreciation, and invoices.

With write access explicitly enabled, the server can prepare or modify records and documents. Supported actions include creating counterparties, invoices, receipts, sales, returns, warehouse movements, payments, cash orders, invoices, and service acts. Changes use a preview and confirmation flow before execution.

## How it works

The server runs locally on the user's computer and sends requests to a 1C database through OData. Any 1C deployment can use the same connector—cloud-hosted, SQL-backed, or file-based—provided the database is published through OData and the required access is available.

MCP clients can select the appropriate capability from a natural-language request. The server hides technical OData entity sets, Cyrillic object names, and GUID-based references behind higher-level operations. Ready-made scenarios cover recurring requests such as morning reporting, debtor aging, reconciliation, and month-end review.

## Setup and configuration

Start the local connector with:

```bash
npx -y 1c-odata-mcp
```

The 1C database must have OData published. For hosted installations, the provider or hosting administrator may need to enable it. For server or file-based installations, the database is published through a web server, with access permissions configured for the base when necessary.

Connect the local process to an MCP client such as Claude Desktop, Claude Code, ChatGPT through Codex, Cursor, VS Code, JetBrains, or LM Studio. The repository includes installation guidance for client configuration, OData publication, connection setup, verification, and common errors.

## Tools and capabilities

- Query cash balances, bank accounts, cash desks, money in transit, sales, payments, and taxes.
- Group receivables and payables by payment terms, showing overdue days, documents, and expected payment information.
- Review counterparties, contracts, documents, inventory balances, and database objects.
- Generate reconciliation data with opening and closing balances, document lines, and contract totals.
- Inspect account movements, correspondence, balances after each movement, trial balances, and postings.
- Check month-end status and trace selected issues back to documents.
- Create, copy, edit, post, or mark documents for deletion when write mode is enabled and the action is confirmed.

## Limitations and notes

OData is a prerequisite. Without a published OData interface, the connector cannot operate; it does not use COM and does not connect directly to SQL. The server is read-only by default, and write operations should only be enabled for explicit user requests after reviewing the preview.

Aging calculations use the payment term recorded in the contract. If that term is absent, the result uses the document age and asks for a general payment period. Reconciliation output supplies data for an act rather than a printed reconciliation form.

The connector supports multiple information bases and organizations. When used with a local model, the data can remain within the local network because the MCP process communicates with the local model and the organization's 1C endpoint.

_Full upstream README: https://allmcps.com/mcp/1c-odata-mcp-2/readme_