SkillFoxx

1C Debug MCP Server

A Go MCP server for debugging 1C over the HTTP Debug Protocol: breakpoints, step execution and variable inspection

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

Broad access

Why this level

  • evaluate runs arbitrary BSL expressions in the context of a stopped session
  • raw_request sends unchecked XML directly into the dbgs.exe debug protocol
All reasons and checks
Russian stack

liga-1c-command/1c-debug-mcpAuthor:liga-1c-command

Install

Manual install

cd 1c-debug-mcp/go && go build -o dist/1c-debug-mcp.exe ./cmd/1c-debug-mcp/

Builds the binary from Go source, requires Go 1.23+.

Access and checks

How we review

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

  • evaluate runs arbitrary BSL expressions in the context of a stopped session
  • raw_request sends unchecked XML directly into the dbgs.exe debug protocol

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

What it does

The server connects to the 1C debug server (dbgs.exe) and gives an agent the full debugger toolset: attach and detach, setting and clearing breakpoints in configuration, extension and external processing modules, step execution (step-in, step-out, continue, pause), viewing local variables and the call stack, evaluating arbitrary BSL expressions at a breakpoint, and sending raw XML requests to dbgs.exe. Configuration metadata is cached locally for a fast start and invalidated automatically when source files change. Version 2.0 was rewritten in Go and ships as a single dependency-free binary with no Node.js requirement. The main usage example targets the Kiro IDE, but the server speaks standard stdio MCP and works with any compatible client.

Who it is for. For 1C developers who want an agent to set breakpoints and work out code behavior itself instead of manual debugging in the Configurator.

Good fit when

  • You need an agent to reproduce a bug with step execution and show variable values
  • You are debugging a common module, a configuration object or an extension with a running debug server
  • You need a single binary with no Node.js install

Not a fit when

  • You need breakpoint debugging of an external processing (EPF): the 1C protocol does not support it, only pause
  • You do not have a running 1C debug server (dbgs.exe) or 1C:Enterprise 8.3
  • You are not on a Windows environment with access to dbgs.exe

Example request

Set a breakpoint in the ОбщегоНазначения common module at line 42, wait for the stop and show the local variables

MCP

Transport
stdio
Authentication
not required

Environment variables

ONEC_DEBUG_URL required
Address of the 1C debug server (dbgs.exe).
ONEC_INFOBASE_ALIAS required
Infobase alias, DefAlias for a local file base or the server base name.
ONEC_DEBUG_PASSWORD secret
The debug server password, if one is set.
ONEC_CF_PATH
Path to the exported configuration for module auto-resolution.

Limitations

Breakpoints do not work in external processings (EPF): this is a limitation of the 1C protocol itself, not the server. For extensions, extensionName must always be specified explicitly, or auto-resolution only searches the main configuration. The raw_request tool sends an arbitrary XML request to dbgs.exe with no content validation. It requires a running, reachable 1C debug server; without it the server is useless.

How to disable. Remove the 1c-debug block from your client's mcp.json and stop the dbgs.exe debug server if it is no longer needed.

FAQ

Is Node.js required to run it?

No, version 2.0 was rewritten in Go and ships as a single dependency-free binary.

Can an external processing be debugged?

Breakpoints do not work there, but pause and step_in can be used for a step-by-step walkthrough.

Discussion

No questions or reviews yet.

All 1C:Enterprise tools
Russian stack

A single-binary Go MCP server: the agent sees 1C metadata, searches code, runs read-only queries and writes accurate BSL

MCP serverBroad access255
Russian stack

An MCP server that exposes the cloud 1C:Napparnik (1C.ai) assistant and a local BSL Language Server to agents in Cursor and other IDEs

MCP serverExtended access22
Russian stack

Ten MCP servers for 1C development: platform reference, targeted object dump and load, COM, storage, file search and BSL Language Server

MCP serverBroad access1
Russian stack

A Dockerized MCP server that keeps BSL Language Server running and gives the agent code navigation, diagnostics and refactoring for 1C instead of grep search

MCP serverExtended access1

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

Alternatives

Tools by other authors for the same tasks.

README in short

The README lists the server's capabilities, requirements and how to build from Go source, a sample mcp.json config for Kiro with environment variables (debug URL, infobase alias, paths to the configuration, extensions and processings), a table of all MCP tools with parameters and example responses, typical debugging scenarios for a common module, an extension and an external processing, a description of metadata caching, and known limitations around EPF and extensionName.

README badge

Report a problem