$ loading_
Access 1C REST APIs via OData for records, documents, registers, and reports.
This MCP tool is described as connecting to 1C:Enterprise REST/OData 3.0 APIs, with no explicit high-risk red flags shown in the provided materials. However, it does execute local code and access external business APIs, and its low community adoption and unknown maintenance status warrant cautious, least-privilege use.
The materials and metadata indicate no required secrets or environment variables; no platform-level token requirement is shown. If the actual 1C service uses authentication, any account/password risk would depend on deployment-specific configuration rather than this package description itself.
Its stated purpose is to access 1C:Enterprise via REST/OData 3.0, so routine network egress to an external 1C service is expected. No fixed remote host is listed in the materials, suggesting the target endpoint is likely user-configured; users should verify it does not connect to untrusted business systems.
The system flags this package as executes-code, meaning it runs local service/code on the host. This is a normal MCP capability, and the provided materials do not show requests for unusual system privileges or unrelated high-risk operations.
Per the description, it can access 1C business objects such as directories, documents, registers, and reports, which may include sensitive enterprise data. There is no stated need for broad local file read/write access, but the visible scope of 1C data should still be tightly limited by server-side account permissions.
Positive factors include being open source, auditable, and MIT-licensed. However, it comes from a third-party registry, has 0 stars, unknown maintenance status, and very limited published materials, which reduces confidence and verifiability. These factors support a caution rating rather than a high-risk one.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "@theyahia/1c-rest-mcp" yet — see the docs or source repo.
Use the 1C REST MCP tool to connect to the OData 3.0 endpoint, fetch the first 20 records from the customer directory, and return customer name, code, and last updated time in a table.
A table of customer directory records with fields like name, code, and last updated time.
Use this MCP tool to read sales documents within a specified date range, extract document number, customer, amount, and status, and sort them by amount descending.
A sales document list sorted by amount, ready for reconciliation and analysis.
Through the 1C OData interface, read inventory register data and call the related report to summarize current stock quantities by warehouse.
A concise summary of stock levels by warehouse along with relevant report results.
Connect AI agents to 1C:Enterprise data through MCP and REST APIs.
Search 1C Enterprise configuration docs in natural language to find key objects.
Let AI call any REST API and extract concise typed results.
Expose OData and REST APIs as MCP tools for SAP backend operations.
Turn existing APIs and databases into MCP tools for direct AI use.
Operate Redmine projects, issues, and workflows directly from MCP clients.