mcp-1c test-base server
mcp-1c
A 1C extension with two HTTP endpoints (query and exec) plus a Python MCP wrapper for Claude Code, built for a test base only
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- exec runs arbitrary BSL code with no restriction at the extension level
- The author explicitly warns not to publish this on a production base
Install
Manual install
Load the extension from 1с-расширение/ into the test base via the designer, grant the user the мсп_ОсновнаяРоль role, publish the мсп_HTTP HTTP service on the web server, then connect Claude Code to the server in mcp-server/ per its README.
This is third-party code. Review the repository files before installing.
What it does
The extension publishes an HTTP service with two methods: query runs a BSL query and returns the result set, exec runs arbitrary BSL code via Выполнить() and optionally returns the value of a given expression. A Python MCP server wraps these two endpoints into 1c_query and 1c_exec tools for Claude Code. Access is protected by Basic auth under a 1C user with a limited role, but exec itself has no whitelist or read-only restriction at the extension level: the guard rail is entirely that the service is published only on a test web server, never on production.
Who it is for. For 1C developers who need quick HTTP access for an agent to a test base for queries and one-off scripts.
Good fit when
- You need a quick query against a test 1C base without setting up COM or a direct connection
- You need to run one-off BSL code for debugging through an agent on an isolated test stand
Not a fit when
- There is even a small chance the extension could reach a production base: the author explicitly says not to publish it there
- You need code-level restrictions: no whitelist or read-only mode is implemented
Example request
Run the query ВЫБРАТЬ 1 КАК Один on the test base and check the connectionLimitations
The author states plainly: the extension was designed for a test base, do not publish it to production, there is no safety guarantee at the extension level. exec runs arbitrary BSL with no restriction; the only safeguard is the isolation of the test web server and role-based Basic auth. On Windows in Git Bash, Cyrillic in -d breaks; the request body must be passed via a UTF-8 file.
How to disable. Unpublish the мсп_HTTP HTTP service on the web server and remove the extension from the test base via the designer.
MCP
- Transport
- stdio
- Authentication
- not required
Security check
- exec runs arbitrary BSL code with no restriction at the extension level
- The author explicitly warns not to publish this on a production base
README in short
The README warns upfront: the extension was designed for a test base, do not publish it to production, there is no safety guarantee at the extension level. It then covers installing the extension in the Designer, granting the role, publishing the HTTP service, and a working bash calling recipe that works around Windows Cyrillic encoding issues, plus a link to mcp-server/README.md for use from Claude.
FAQ
Are there restrictions on code inside exec?
No, there is no whitelist or read-only restriction at the extension level, so the service relies entirely on the isolation of the test setup.
Why does Cyrillic break in bash?
Windows converts CLI arguments to the local encoding, so the request body and Basic auth login must be prepared via a UTF-8 file and a precomputed base64 string.
Related
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Skills for real engineers by Matt Pocock
Skills For Real Engineers
Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
Reference MCP servers
Model Context Protocol servers
Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything