1c-mcp
A TypeScript MCP server that reads 1C data through OData, read-only: entity search, entity cards, related records
- 0 ★ on the repository
- Last commit
Broad access
Why this level
- Reads the 1C database, which usually holds personal data of clients and employees
- Runs a Node.js server that reads objects and related records of a 1C infobase over OData
- Writing to 1C is not supported
A similar tool with a larger community: OneC MCP, 5 ★ on the repository
Install
- Works in
- Services
Manual install
pnpm install && cp .env.example .env && pnpm build && pnpm --filter @carely/1c-mcp startCommands from the README: install dependencies, copy the env config, build and start the server.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Reads the 1C database, which usually holds personal data of clients and employees
- Runs a Node.js server that reads objects and related records of a 1C infobase over OData
- Writing to 1C is not supported
This is third-party code. Review the repository files before installing.
What it does
The server talks to 1C over OData and gives the agent read tools: listing available data sources, describing connection capabilities, searching entities, fetching an entity card and finding related records. It includes a healthcheck and a tool inventory. The author states this is an early version: some business logic from an earlier Python prototype has not been ported yet, and the project layout mirrors two of the author's other MCP servers.
Who it is for. For developers who want an agent to have safe, read-only access to 1C data over OData without any risk of writing to the database.
Good fit when
- You want an agent to read 1C catalogs and documents over OData with no write access
- Your 1C infobase already has an OData publication and you need an MCP bridge to it
- You need a starting point for your own TypeScript MCP on top of 1C
Not a fit when
- You need to write data into 1C: the server only reads
- You need ready business scenarios: the author notes prototype logic is not fully ported yet
- Your 1C infobase has no OData publication
Example request
Find a counterparty by name in 1C and show its related documentsMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
ONEC_INTERFACE_MODE- Set to mock for smoke tests without a real 1C base.
Limitations
The project is at an early stage with no stars and no releases. It is read-only and never changes data in 1C. You need an OData publication configured on the 1C side and the environment variables from .env.example. Some business logic from the author's Python prototype has not been ported yet.
How to disable. Stop the server process and remove it from your MCP client configuration.
FAQ
Can the server change data in 1C?
No, the README states the tools are read-only over OData.
Can I try the server without a real 1C base?
Yes, there is an ONEC_INTERFACE_MODE=mock mode for smoke tests without real 1C credentials.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise tools1C OData MCP with a JSON cache
MCP сервер для работы с OData 1C
A Python MCP server over 1C OData: reads and changes catalogs and documents, saving everything to JSON files for local analysis without repeat queries
1C OData MCP server
1C OData MCP Server
A small Python MCP server that wraps standard 1C Управление предприятием OData read operations into three tools
1C over OData: read-only MCP server
onec-odata-mcp
An npx MCP server that gives Claude read access to a 1C database via standard OData, no Excel exports or hand-built URLs
1C metadata MCP proxy (adapted fork)
1C_MCP_SERVER_OWN
A Python proxy between an MCP client and a 1C HTTP service: reads metadata, object structure and predefined data, with optional OAuth2
MCP server for 1C:Enterprise data over OData: receivables, sales, stock and cash, plus document creation and posting behind a separate flag
A PyPI-published read-only MCP server for standard 1C:Enterprise OData 8.3.5+: schema, filtered queries, record lookup by Ref_Key
README in short
The README describes a TypeScript MCP server for read-only access to 1C ERP over OData, gives pnpm quick-start commands, a mock mode for tests without a real base, and a list of seven tools: inventory, healthcheck, source listing, capability description, entity search, entity card and related-entity search.