SkillFoxx

AI x 1C Guide workflow

A guide with working scripts on safely connecting an agent to 1C and Bitrix24: OData, webhooks and a catalog of 14 vetted tools

  • 13 ★ on the repository
  • Last commit
  • MIT
Workflow

Extended access

Why this level

  • Python scripts in scripts/ call 1C:UNF over OData and Bitrix24 through a webhook
  • The examples only read, the guide treats writes as a separate step with its own permissions
All reasons and checks
Russian stack

aleksandr-litvinenko/1c-ai-guideAuthor:Aleksandr Litvinenko

Install

Manual install

python scripts/fresh_odata_example.py

The 1C:Fresh OData client example, run after cloning the repo and configuring your own connection parameters.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Python scripts in scripts/ call 1C:UNF over OData and Bitrix24 through a webhook
  • The examples only read, the guide treats writes as a separate step with its own permissions

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

What it does

The repository walks through four real integrations, marking what was verified in practice and what was not: reading and a test write into 1C:UNF via standard OData, reading Bitrix24 tasks through an incoming webhook, creating leads from a website form via a backend webhook, and reconciling requests across 1C-Connect, Jira and Bitrix24. Each integration comes with a working Python script in scripts/, tests, and a guide in guides/. A separate catalog of 14 projects (MCP servers, Agent Skills, hosted services) in catalog/tools.json is tagged with a verification level: Docs, Artifact, CLI smoke or Live smoke, plus license and key risk. The guide sets out a ten-point security baseline and a four-stage rollout order, from source-only access with no database to data writes with human confirmation.

Who it is for. For 1C developers, integrators and managers deciding how to safely give an agent access to 1C or Bitrix24 without risking production data.

Good fit when

  • You need a step-by-step breakdown of connecting an agent to 1C:Fresh or UNF OData
  • You need to pick an MCP server or Agent Skills for a specific task with an honest risk assessment
  • You need a security baseline checklist before giving an agent access to a production base

Not a fit when

  • You need a ready MCP server, not a guide with examples and a catalog of links to other projects
  • You work with neither 1C nor Bitrix24

Example request

Work out how to safely connect a read-only agent to 1C:Fresh via OData and show an example with my HTTP client

Limitations

The repository itself is not an MCP server or an installable agent tool, but a guide with example scripts and a comparison catalog. Some scenarios (writing to 1C:UNF, part of the Bitrix24 flow) are confirmed in the author's own working code but not publicly reproduced, which the text states honestly. Catalog assessments are based on documentation and the author's local checks, not an independent audit of every project.

How to disable. Simply do not use the example scripts from scripts/; the guide does not install anything into your project automatically.

FAQ

Does the guide guarantee the listed MCP servers are safe?

No, the README states directly it does not declare tools safe or production-ready, only records a verification level.

What is the difference between an MCP server and Agent Skills here?

An MCP server gives an agent tools and protocol access to an external system, while Agent Skills are rules and workflows inside the client itself, often without touching a database at all.

Discussion

No questions or reviews yet.

All 1C:Enterprise tools
Russian stack

A set of skills and recipes so an agent writes correct, secure code for sites on 1C-Bitrix Site Manager

SkillExtended access9

1C AI development environment

1C AI Development Environment

Russian stack

1C development environment with an MCP server offering 10 tools: 11 BSL analyzers, JSON DSL to XML, dependency graph, and EPF build without 1C

MCP serverBroad access18

1C AI sandbox client-server

1c-ai-sandbox-client-server

Russian stack

A devcontainer plus a Hyper-V VM with a 1C server that isolate an AI agent from the host machine so a wrong command cannot touch real files or drives

WorkflowExtended access44
Russian stack

A tiny 1C extension with an HTTP service plus a skill, so an agent writes 1C queries itself and gets database data as TSV

SkillExtended access56
Russian stack

MCP server for 1C:Enterprise databases over standard OData: catalogs, documents, registers and accounting with no configuration extension

MCP serverBroad access13

IIkona (1c-ai-connector)

ИИкона (1c-ai-connector)

Russian stack

A 1C extension with an LLM connector, agent loop, RAG, error monitoring and an MCP server that exposes the infobase to external agents

MCP serverBroad access108

README in short

The README gives a quick-start table by scenario, walks through four integrations noting what was verified live, explains that 1C OData is not read-only by default and how to restrict it, provides a tool-selection table and a 14-project catalog table with verification levels and risks, an architecture diagram, four rollout stages, a security baseline and an FAQ.

README badge

Report a problem