1c-odata-mcp
MCP server for 1C:Enterprise data over OData: receivables, sales, stock and cash, plus document creation and posting behind a separate flag
Install
{
"mcpServers": {
"1c-odata": {
"command": "npx",
"args": ["-y", "1c-odata-mcp"],
"env": {
"ODATA_BASE_URL": "https://<сервер>/<база>/odata/standard.odata/",
"ODATA_USERNAME": "...",
"ODATA_PASSWORD": "..."
}
}
}
}Publish OData and add the needed objects to its composition first. Fully restart Claude Desktop after editing.
This is third-party code. Review the repository files before installing.
What it does
The server connects to any 1C base with the standard OData interface published, whether in the cloud, on a SQL server or as a file base, and hides technical entity names behind clear tools. In read mode the agent searches counterparties and documents and builds receivables from account 62, stock balances, sales, cash flow, taxes paid and settlement history. With writes enabled it creates counterparties, items and contracts, issues invoices, sales, receipts, payment documents and cash orders, copies a document from a sample and posts it. One server serves several bases and legal entities.
Who it is for. For managers, accountants and 1C specialists who want answers from the accounting base and routine documents without coding on the 1C side.
Good fit when
- You want to ask which customers owe the most
- You need monthly acts issued from last month's document
- You need a sales or cash flow slice for a period across several legal entities
Not a fit when
- OData is not published in the base and cannot be enabled
- You need routine closing operations such as month-end close: the server does not create them
Example request
Which customers owe us the most and how much?Limitations
It works only through OData, and objects must be added to the standard interface composition. Analytics and accounting accounts target Enterprise Accounting 3.0. Documents are created unposted and 1C itself generates entries on posting. Large result sets are truncated, and yearly queries on slow bases can take tens of seconds.
How to disable. Delete the 1c-odata block from the MCP client config. To stay read-only, do not set READ_ONLY=false.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| ODATA_BASE_URL required | Standard OData interface URL, trailing slash required |
| ODATA_USERNAME required | 1C infobase user |
| ODATA_PASSWORD required, secret | 1C user password |
| READ_ONLY | false lifts the global write lock |
Security check
- With writes enabled it creates and posts documents in a live accounting base
- Creates payment orders and cash documents
- Requires a 1C user login and password
README in short
The README explains which 1C hosting options fit and what to enable on the base side. It covers read and write capabilities with sample phrases, a sample dialog, a three-step quick start and the full tool list. It separately covers the two write safeguards, multiple bases and legal entities, limitations, internals and FAQ. Step-by-step OData publishing and connection are in docs. MIT license.
FAQ
How do I enable writes?
Two flags: global READ_ONLY=false and ODATA_DB_<NAME>_WRITABLE=true for a specific base. Every write previews first and runs only with confirm=true.
Does the server delete data?
No, it only sets the deletion mark, as 1C itself does.
Related
Stripe's official MCP server, plugins and skills: the agent searches the API and docs, reads and changes account data
The official CCXT MCP server and skills: market data, balances and opt-in trading across crypto exchanges and prediction markets
Skill plugins for analyzing stocks, earnings, options and startups, plus readers for social feeds and market data
Skills and an MCP server for options traders: quotes, technical analysis, Greeks, spreads, scanners and Interactive Brokers portfolio