XORit Labs · Model Context Protocol

XORit MCP for 1C

Ask what a product last sold for, where stock balances are kept, or which module calls a procedure. OpenClaw uses MCP to find the document, accounting object or line of code in your 1C system.

Red lines connect a request to documents and the database
01 / Assistant and database

How it works

A customer wants a price. Where do you start?

Ask in your work chat how much this customer paid for the item last time. MCP connects OpenClaw to your 1C records. Ask for the date, unit price and document behind the sale.

  1. 01

    Ask in chat

    “What did we charge Example Co. for this monitor?”

  2. 02

    Look up the sale

    The assistant matches the customer and model, then checks the most recent sales documents.

  3. 03

    Check the source

    The unit price, date and document number let the salesperson verify the answer in 1C.

01 · For sales teams

From a supplier invoice to a customer draft

“Prepare an invoice for this computer with a 20% markup.” This single-item example excludes VAT and shows what the assistant prepares and what the employee checks.

  1. 01 / Purchase50 000 ₽

    A computer on the supplier invoice. The assistant looks for the matching item in the product catalogue.

  2. 02 / Calculation+20%

    The employee sets the markup. Here it adds ₽10,000 to the purchase price.

  3. 03 / Draft60 000 ₽

    The employee reviews the customer, contract, item and total. Confirmation creates an unposted invoice in 1C.

Find a contract

Give a company name to retrieve its record and contracts. Use its tax ID to distinguish companies with similar names.

Look up a sale price

Ask what a particular item last sold for. The assistant looks up the item and price in sales documents.

Add a counterparty

Before creating a record, the assistant looks for matches. The employee reviews existing entries and the proposed company details.

Two everyday decisions

When a name alone is not enough

Choosing a contract

Two contracts for one customer. Which goes on the invoice?

One customer
Equipment supplyTechnical support

Ask for the contracts held by a specific legal entity using its tax ID. Check the number and date, then select the agreement covering this service or supply.

Checking a price

Did the price go up, or did the customer buy more?

Illustrative example · unit price
March8 000 ₽
June10 000 ₽

Ask for two sales of the same model to this customer. Compare the same unit, currency and VAT basis. Here the unit price rose by ₽2,000.

What to bring to a demo

Pick an item whose price you know and a typical invoice. During the demo, follow the question back to the document and compare the result with your own records.

See it in action ↗

02 · For analysts

“Where does our configuration store stock balances?”

Registers and accounts differ across configurations. MCP searches the connected database’s metadata by meaning, including extensions. Open the matching object to check its structure.

01

Find the object

Search returns candidate objects with their full metadata names.

02

Inspect its structure

The object card shows fields and types. Inspect a register’s dimensions and resources.

03

Trace relationships

See which documents post movements to the register and which objects refer to it.

A dimensional illustration of links between modules
02 / Configuration navigation

BSL · Navigation example

One function. Two call sites.

Document moduleCalculateTotal(…)
Common moduleCalculateTotal(…)
Calculation module.bsl
Function CalculateTotal(Price, Quantity) Export
  Return Price * Quantity;
EndFunction

↳ Jump to definition

Illustrative example: two modules call the same function. MCP helps find its definition and references in an exported configuration.
Code check results

File → line → diagnostic message

03 · For 1C developers

From a module call to the procedure definition

BSL (Built-in Script Language) is the programming language built into 1C:Enterprise. It defines how documents, forms, reports and data processors work: how prices are calculated, fields are filled and actions run when a document is saved or posted. The code lives in configuration and extension modules; exported source files use the .bsl extension.

XORit MCP helps developers explore this code: jump from a call to its procedure, find references and check changes before testing them in 1C. For example, trace a function involved in calculating a document total or find a syntax error in a submitted module.

Navigate 1C code (BSL)

Jump to a definition and find references in an exported configuration or extension. Results include file, line and column.

Check changes

Check a single file or up to 16 modules in a batch. Diagnostics point to the relevant source lines.

Search platform help

Ask how to check whether an extension can be applied. The assistant finds the method and opens its parameter reference for the installed platform version.

Architecture · xorit-1c-mcp

Inside XORit MCP for 1C

You describe a task in chat. MCP checks access and parameters, works with your database and returns the result to the assistant.

XORit / 1C MCPFrom request to result
01

OpenClaw

A task in everyday language

“Find the contract and prepare an invoice”
Employee and AI assistant
02

XORit

1C MCP

The connection to your 1C system

  • User permissions
  • Parameter checks
  • Operation tracking
03

Your 1C system

Business records and configuration

  • Contracts and documents
  • Products and prices
  • Metadata and extensions

Three ways to get the task done

01 / OData

Data and documents

Search, read records and create drafts through the published 1C interface.

02 / Windows worker

Platform tasks

COM and Designer handle queries, exports, checks and prepared updates.

03 / BSL + ONNX

Local analysis

Checks for 1C’s built-in language (BSL), platform help and semantic search run on the MCP server.

Results return to the chat. To change data, MCP first prepares an operation with specific parameters, then executes it at the user’s request.

When data needs to change

  1. Prepare
  2. Review parameters
  3. Execute
  4. Verify the result
Technical stack for administrators

Linux: Python / FastMCP, SQLite, Node.js and the OpenClaw plugin. Windows: PowerShell worker, COMConnector and 1C Designer. Analysis: BSL Language Server, a Java-based analyzer for 1C’s built-in language, and local multilingual-e5-small via ONNX Runtime. MCP uses stdio; OData uses the 1C web publication, worker requests use WinRM, and exported sources are read over SMB. The current integration verifies users through XORit Platform; deployment details are agreed for your infrastructure.

04 · Deployment

How MCP connects to your database

What does a pilot need?

Choose a database and verify its OData publication and 1C account permissions. Available documents and fields depend on the configuration and published entities.

Who can create documents?

Operations depend on the user’s role. The assistant previews the parameters before writing. A confirmed draft has an operation ID for checking the outcome.

What can we try in a demo?

Choose a familiar product, sample invoice or extension module. Follow a question back to its source document, reviewed draft or line of BSL.

Request a call
or contact us

Request a call

    How data is processed · SmartCaptcha data notice

    Your request has been successfully
    sent

    We will contact you shortly,
    to discuss cooperation details

    An error occurred
    while sending the form

    Please try again later
    or contact us directly: