Log inSubmit server
1c Odata MCP logo

1c Odata MCP

Connects 1C:Enterprise data to MCP clients over OData for accounting queries, reports, and preview-gated document actions.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install 1c Odata MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "1c-odata-mcp-2": {
      "command": "npx",
      "args": [
        "-y",
        "1c-odata-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

1c-odata-mcp MCP server connects 1C:Enterprise databases to MCP clients through the standard OData interface. It turns natural-language requests into accounting queries such as cash summaries, receivables aging, month-end checks, account cards, reconciliation statements, trial balances, and postings. Read operations are the default; document creation and other changes require explicit enablement, a preview, and confirmation. Use it when a 1C database has OData published and needs access from Claude, Cursor, VS Code, local models, or another MCP client.

Use cases

  • Review month-end closing issues before reporting
  • Find overdue receivables and payables by aging
  • Prepare reconciliation data for a counterparty
  • Inspect account movements, postings, and document history

Key features

  • 1C:Enterprise access through OData
  • Natural-language accounting queries
  • Cash, debt, sales, tax, and inventory reporting
  • Month-end closing and document-level checks
  • Reconciliation statements and account cards
  • Preview-gated write operations

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 6d ago via OSV.dev · 1c-odata-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars35Stargazers on the source repository.
npm downloads1.3kPackage downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.

How 1c Odata MCP works

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:

Terminal
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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about 1c Odata MCP

1c-odata-mcp is an MCP server that connects 1C:Enterprise databases to MCP clients through OData. Its main tools cover cash and debt summaries, accounting reports, month-end checks, reconciliation data, account movements, document searches, and preview-gated creation or modification of 1C documents.

Install it as a local process with `npx -y 1c-odata-mcp`, then configure an MCP client to launch it. The 1C database must have OData published, and the client connection must be given access to that endpoint.

Yes, 1c-odata-mcp works with Cursor. It also supports MCP clients including Claude Desktop, Claude Code, VS Code, JetBrains, ChatGPT through Codex, and local-model clients such as LM Studio.

It requires a published OData interface for the 1C database. The connector can work with cloud, SQL-backed, or local file-based deployments, but it does not use COM or connect directly to the SQL database.

Related MCP servers

All in Finance & Fintech All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG Preview1c Odata MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/1c-odata-mcp-2?style=directory)](https://allmcps.com/mcp/1c-odata-mcp-2)
HTML Embed
<a href="https://allmcps.com/mcp/1c-odata-mcp-2"><img src="https://allmcps.com/api/badge/1c-odata-mcp-2?style=directory" alt="1c Odata MCP on AllMCPs" /></a>