SkillFoxx

Unified 1C MCP gateway with a dashboard

onec-mcp-universal

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

  • 5 ★ on the repository
  • Last commit
  • MIT
MCP server

Broad access

Why this level

  • The write_bsl tool writes BSL code straight into the project
  • Gives access to the data, code and event log of connected 1C infobases, worth starting with a test infobase
All reasons and checks
Russian stack

voregnev/onec-mcp-universalAuthor:voregnev

Install

Manual install

cp .env.example .env && ./setup.sh

Initial setup on Linux or Windows before starting the containers.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • The write_bsl tool writes BSL code straight into the project
  • Gives access to the data, code and event log of connected 1C infobases, worth starting with a test infobase

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

What it does

The gateway combines 47 MCP tools and one resource under a single address, http://localhost:8080/mcp, instead of several separate connections. Each AI assistant session works with its own active infobase independently through per-session routing on the Mcp-Session-Id header. The tools cover database queries, code execution, metadata, the event log, permissions, BSL navigation and full-text search, writing BSL modules with reindexing, ITS search via the 1C:Napparnik API, personal data anonymization under Russia's 152-FZ, metadata caching and query profiling. An MCPToolkit.epf processing in the 1C client connects an infobase to the gateway with one button, there is a web dashboard for status and settings, and 72 skills for Claude Code.

Who it is for. For 1C developers who want one MCP gateway for several infobases and AI assistants instead of a separate connection for each pair.

Good fit when

  • You need several 1C infobases connected to different AI assistant sessions at once
  • You need to write BSL code straight from the agent with automatic reindexing
  • You need personal data anonymization when working with a production infobase

Not a fit when

  • You need one simple integration without Docker and a web dashboard
  • You are not ready to run several containers: the gateway, the toolkit proxy, platform-context, bsl-lsp

Example request

Use onec-mcp-universal to find every document with a posting error from yesterday and show the event log

MCP

Transport
http
Authentication
not required

Limitations

Needs Docker 24+ and Docker Compose v2, on Ubuntu 22.04+ or Windows 10/11 with Docker Desktop. Some images are external (roctup/1c-mcp-toolkit-proxy, alkoleft/mcp-bsl-platform-context), and their development is not controlled by this repository's author. The BSL code-writing tool lets the agent change modules in the project, worth accounting for when setting up access.

How to disable. Stop the containers with docker compose down and remove the gateway entry from your MCP client config.

FAQ

Can several infobases be connected at once?

Yes, per-session routing keeps AI assistant sessions on different infobases independently.

How is personal data masked?

The enable_anonymization and disable_anonymization tools mask names, tax IDs, insurance numbers, phone numbers and emails with a stable hash mapping.

Discussion

No questions or reviews yet.

All 1C:Enterprise tools
Russian stack

A Docker gateway with 40-plus MCP tools for 1C, one address, a settings dashboard and a set of 1C skills for Claude Code

MCP serverBroad access
Russian stack

A Docker server with a read-only core and pluggable modules: metadata, code, forms and relations of several 1C configurations through one MCP contract

MCP serverExtended access12
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

Five independent Docker-based MCP servers: a Neo4j metadata and call graph, static BSL analysis, platform syntax help, a query builder and 1C coding standards

MCP serverExtended access
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
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

README in short

The README describes the architecture in detail: the onec-mcp-gw Python gateway, static and per-database dynamic backends, anonymization, metadata caching, profiling, BSL search and 1C:Napparnik client modules. It gives a table of 47 tools by category, Docker requirements, Linux and Windows instructions, connecting Claude Code, Cursor and Windsurf, working with several infobases, and running the gateway remotely on a 1C server.

README badge

Report a problem