AI Finansist: MCP server for 1C

mcp_1c (AI Финансист)

An MCP server, a 1C OData client and a local language model bundled with a Gradio chat for questions about 1C data and uploaded PDFs

  • 0 ★ on the repository
  • Last commit
MCP server

Broad access

Why this level

  • The OData client can create, update and delete 1C database records, not just read them
  • The 1C login and password are stored in .env in plain text
All reasons and checks
Russian stack

alexpcrus/mcp_1c

Install

Manual install

docker compose up --build

Before starting, fill .env with the 1C OData address, login and password, and bring up vLLM separately.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • The OData client can create, update and delete 1C database records, not just read them
  • The 1C login and password are stored in .env in plain text

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

What it does

The project brings up a four-part stack via docker compose: a vLLM server running the Salesforce xLAM model for tool-call parsing, an MCP server with 1C tools built on the OData protocol, an orchestrator that ties the model's output to MCP calls, and a Gradio web chat. The OData client can read, create, update and delete data in a 1C database through the standard standard.odata interface. The chat also accepts PDF uploads, whose text the pdf_parser module extracts and feeds into the conversation alongside the 1C data.

Who it is for. For 1C developers who want their own local chat with access to 1C data over OData, without cloud LLM providers.

Good fit when

  • You want a fully local stack: your own model, your own MCP server, your own chat, no external APIs
  • Your 1C data is reachable through the standard standard.odata interface
  • You want to combine questions about PDF documents and 1C data in one chat

Not a fit when

  • You lack the hardware to run the local Salesforce xLAM-2-32b model through vLLM
  • You need an MCP server for Claude Code or Cursor, not a separate web chat
  • Your 1C database does not expose OData, or exposes it on a non-standard path

Example request

Show the stock balance from the 1C catalog and compare it with the table from the uploaded PDF price list

MCP

Transport
http
Authentication
not required

Environment variables

MCP_1C_BASE required
Address of the 1C OData database, e.g. http://host/TEST19/odata/standard.odata
ONEC_USERNAME required
1C user login for the OData connection
ONEC_PASSWORD required, secret
1C user password, stored in .env in plain text

Limitations

No updates for over a year, and the README does not document the MCP tool architecture; documentation is limited to project layout and environment variables. It needs a separately running vLLM server with the Salesforce xLAM-2-32b model, a real GPU load. The 1C database login and password go into .env in plain text. The MCP transport and auth are not documented in the README; check mcp_server.py source for exact settings.

How to disable. Stop the stack with docker compose down and remove the project's containers.

FAQ

Does it need access to cloud LLMs?

No, the README describes running the local Salesforce xLAM-2-32b model through vLLM on your own hardware.

Can this be used as a regular MCP server for Claude Code?

The README does not describe that; the project is built as a self-contained Gradio web chat, not an MCP server for an external client.

Discussion

No questions or reviews yet.

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 access47Repository stars

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 databases over standard OData: catalogs, documents, registers and accounting with no configuration extension

MCP serverBroad access13Repository stars
Russian stack

A Python proxy between an MCP client and a 1C HTTP service: reads metadata, object structure and predefined data, with optional OAuth2

MCP serverExtended access9Repository 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

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

README in short

The README gives the project layout: docker-compose.yml, gradio_app.py for the chat, orchestrator.py as the agent between the LLM and MCP, mcp_server.py, odata_client.py and pdf_parser.py. It describes running vLLM with the Salesforce xLAM-2-32b model on port 8000, a sample .env with MCP and 1C OData addresses, login and password, and the final docker compose up --build launch with the Gradio UI and MCP server addresses.

README badge

Report a problem