SkillFoxx

v8-session-manager: 1C client MCP session manager

v8-session-manager

A Rust binary that accepts WebSocket connections from several 1C clients and exposes a single MCP endpoint for AI agents

  • 10 ★ on the repository
  • Last commit
  • AGPL-3.0
MCP server

Extended access

Why this level

  • Opens network ports for WS and MCP HTTP
  • Proxies tool calls that run BSL code inside a 1C session
All reasons and checks
Russian stack

1c-neurofish/v8-session-managerAuthor:1c-neurofish

Install

Manual install

cargo build --release

Build from source, the binary lands in target/release.

Access and checks

How we review

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

  • Opens network ports for WS and MCP HTTP
  • Proxies tool calls that run BSL code inside a 1C session

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

What it does

The service acts as a broker between several running 1C clients and an AI agent. 1C clients started with mcpMode=ws connect to the manager over WebSocket and publish their MCP tools, while the agent sees them all on one MCP HTTP endpoint through a shared tools/list. Each session gets a FIFO call queue so the agent's parallel requests don't get reordered on the 1C side, plus soft-reconnect by client id when a connection drops and automatic cleanup of idle sessions. The manager does not start 1C clients itself; that is done by an external orchestrator or the onec-client-mcp-devkit BSL extension. The manager's only built-in tool, session_list, shows active sessions.

Who it is for. For 1C developers already using onec-client-mcp-devkit who want to give an agent access to several running 1C clients through one entry point.

Good fit when

  • Several 1C sessions run at once (a test session, a different account, several databases) and you need one MCP address for the agent
  • You need a guarantee that the agent's parallel calls to one 1C session run one at a time
  • A 1C client may reconnect and you need the session and its published tools preserved

Not a fit when

  • Only one 1C client runs and a broker adds no value
  • There is no BSL extension on the 1C side to publish tools through session.register
  • You need a ready binary without building from source: releases exist via GitHub Actions, but the README's install path assumes a cargo build

Example request

List the active 1C sessions via session_list and call the right tool in the Test database session

MCP

Transport
http
Authentication
not required

Environment variables

V8SM_CONFIG
Path to the YAML config, an alternative to the --config flag.

Limitations

The manager is useless on its own without 1C clients publishing tools over WS, meaning without onec-client-mcp-devkit or a similar extension. The project is written in Rust and needs a cargo build --release. The tool publication format changed between versions (the v2 naming contract from 2026-05-09 dropped kind-based prefixes), so older integrations may break. Bearer-token auth for MCP HTTP is optional and disabled by default.

How to disable. Stop the systemd service (systemctl disable --now v8-session-manager) or kill the binary process and remove it from your MCP client configuration.

FAQ

Does the manager start 1C clients itself?

No, it only accepts their connections. Starting 1C clients with the right launch parameters is left to an external orchestrator or extension.

What happens if two clients publish a tool with the same name?

If the input schema matches, calls are round-robined between the sessions. If the schemas differ, the tool is hidden from the list until the conflict is resolved.

Discussion

No questions or reviews yet.

All 1C:Enterprise tools
Russian stack

A Docker gateway with one address instead of several MCP connections: 1C data, BSL navigation, ITS search via 1C:Napparnik, and a web dashboard

MCP serverBroad access5
Russian stack

A native component that runs a full MCP server inside 1C: tools, resources and prompts are written in BSL, while a DLL handles the protocol

MCP serverBroad access43
Russian stack

A 1C extension that runs an MCP server inside the 1C:Enterprise client and lets you write your own tools in BSL

MCP serverExtended access71
Russian stack

A platform of three MCP servers for reading, writing and intelligence operations on 1C:Enterprise configurations and infobases

MCP serverBroad access
Russian stack

A Go MCP gateway between an agent and a 1C HTTP service: references, sales, stock, cash and settlement reporting across several databases

MCP serverExtended access5
Russian stack

A 1C extension that runs an MCP server inside the infobase: metadata tools out of the box and custom tools in BSL

MCP serverBroad access574

README in short

The README describes a Rust binary with two transports: WebSocket for 1C clients on port 4000 and MCP HTTP for agents on port 4001, both running over a shared session registry. It covers an architecture diagram, a feature list (per-session FIFO, soft-reconnect, idle sweeper, tool deduplication), build and systemd install instructions, a table of 1C client /C launch parameters and a table of v8project.yaml config settings. It separately explains the v2 naming contract for tool publication and the required session registration fields. The project is noted as a fork split off from v8-runner, licensed AGPL-3.0.

README badge

Report a problem