SkillFoxx

1C OData skills and bot

1c oData bot

OData and metadata-search skills for AI agents, plus a Telegram and email bot that answers plain-language questions about 1C data

  • 8 ★ on the repository
  • Last commit
  • MIT
Skill

Extended access

Why this level

  • Sends data from the 1C database over Telegram and email, so access to the bot should be restricted
  • The external processing publishes the database's OData interface, widening the API surface
All reasons and checks
Russian stack

gybson63/1c-odata-skillAuthor:gybson63

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add skills/1c-odata-bot

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

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

  • Sends data from the 1C database over Telegram and email, so access to the bot should be restricted
  • The external processing publishes the database's OData interface, widening the API surface

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

What it does

The project offers two ways to get 1C data over the standard OData protocol. For AI agents there are separate skills: odata builds and runs OData queries, 1cconfinfo parses the configuration structure, conf-doc does semantic search over objects and attributes before the query itself, and conf-doc is also exposed as an MCP server for Cursor. Alongside that, a multi-agent bot runs on Telegram and email: a question in Russian passes through a metadata analyst, an OData agent that builds the query and counts records via $count and $expand, and a formatter that presents the answer as a table or chart. A separate external processing report, EnableODataInterface, publishes the needed catalogs, documents and registers to OData right from the Enterprise mode, without the Configurator.

Who it is for. For 1C developers and analysts who want to give colleagues natural-language access to 1C data, and for anyone who wants OData skills for their own AI agent.

Good fit when

  • You want to let staff without 1C access ask for data through Telegram or email in plain language
  • You need reusable OData and metadata-search skills for an agent in Cursor
  • You want to quickly publish 1C objects to OData without opening the Configurator

Not a fit when

  • 1C's OData interface is not published and publishing it is unsafe for your environment
  • You need to write data into 1C: both the skills and the bot are described as reading data through OData, not changing it
  • You cannot connect an external AI provider for the multi-agent pipeline

Example request

How many customer orders were placed this week and for what total, show it as a table

Limitations

The bot and the analyst agent use their own multi-agent AI pipeline, with tokens and cost tracked per session; the specific model provider is set in configuration and not named explicitly in the README. Domain profiles like ЗУП КОРП are built for specific configurations, and others will need their own profile. The EnableODataInterface external processing publishes OData from Enterprise mode, which widens the database's API surface, and deciding which objects to publish is left to the administrator. The email interface works off an allowed-sender list set in the config.

How to disable. Stop the python -m bot process and disable the database's OData interface through the same EnableODataInterface report or in the Configurator.

FAQ

Can the bot change data in 1C?

The README only describes querying data through OData and counting records; write operations are not documented.

Why is conf-doc needed before the OData query itself?

Semantic search over metadata finds the right objects and attributes upfront, which reduces failed OData queries on the first step.

Discussion

No questions or reviews yet.

All 1C:Enterprise tools
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

Telegram bot over a 1C MCP server

Telegram Bot for 1С MCP Integration

Russian stack

A Python bot that answers natural-language questions about 1C data in Telegram, calling a 1C MCP server's tools through a chosen AI model

CLIExtended access
Russian stack

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

WorkflowExtended access13
Russian stack

An npx MCP server that gives Claude read access to a 1C database via standard OData, no Excel exports or hand-built URLs

MCP serverExtended access

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
Russian stack

Ready-made methods for Telegram, Bitrix24, VK, CDEK, Yandex Disk, databases and other APIs in 1C, OneScript and the oint CLI

CLIBroad access693

README in short

The README lists the features: an email interface with HTML replies and attachments, a Telegram bot with an analyst-OData-formatter multi-agent pipeline, conf-doc semantic search, a separate metadata-analyst mode with domain profiles, optional web search through a self-hosted SearXNG as a fallback, a set of skills for AI agents, and an external OData-publishing processing report. It gives a quick start and a documentation link table for each audience: bot user, setup, MCP in Cursor, SearXNG, bot developer. It notes a development process using feature branches and pre-commit.

README badge

Report a problem