MCP 1C Local Bridge: an agent inside an open 1C session
mcp-1c-local-bridge
An MCP server plus a 1C external data processor that lets an agent run queries and code in the user's already open session, with no gateway in between
- 10 ★ on the repository
- Last commit
Broad access
Why this level
- The eval and execute tools run arbitrary 1C code in the user's session with their rights
- Queries and metadata expose the contents of a working database to the agent while the processor form is open
Install
- Works in
- Services
Manual install
git clone https://github.com/ntappw/mcp-1c-local-bridge.git && cd mcp-1c-local-bridge && uv syncClones the repository and installs server dependencies.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The eval and execute tools run arbitrary 1C code in the user's session with their rights
- Queries and metadata expose the contents of a working database to the agent while the processor form is open
This is third-party code. Review the repository files before installing.
What it does
The project is a Python stdio server plus an external data processor, MCPLocalBridge.epf, opened in the 1C:Enterprise client. Exchange runs through JSON files in the user profile folder: the server drops a command, the processor form picks it up every half second, runs it on the 1C server with the user's rights and writes back the answer. An agent gets ten tools: sessions, ping, query, eval, execute, metadata, find, usages, result and cancel. There is result release with confirmation on the form, a command log, switches for database writes and client-side code, and a mode for ordinary forms and old configurations.
Who it is for. 1C developers and analysts on Windows who want an agent working in a live database: queries, metadata review, finding where an object is used.
Good fit when
- An agent has to run 1C queries and read the result in an open database
- You want to explore metadata and find where a configuration object is used
- Data must stay on the developer's machine and each answer release should be confirmable with a button
- You want an agent that checks query output against real database data instead of guessing from descriptions
Not a fit when
- You need access to a server database with no open 1C client: the bridge works only through the open processor
- You are not on Windows: the 1C client needs Windows, though the server can run in WSL
- An agent must not run arbitrary code in a production database with your rights
Example request
List the open 1C sessions and find where the Номенклатура catalog is usedMCP
- Transport
- stdio
- Authentication
- not required
Environment variables
MCP_1C_BRIDGE_DIR- Exchange folder instead of %TEMP%\mcp-1c-local-bridge
Limitations
The bridge works only on Windows with a 1C 8.3 client, the processor targets compatibility mode 8.3.14 and later, and the configuration must allow synchronous calls. The eval and execute tools run arbitrary 1C code with the rights of the user who opened the form, and database writes are enabled by a separate switch on the form. A terminal server needs a shared exchange folder. Ten stars, one author, last commit in November 2026, with an article on Infostart.
How to disable. Close the processor form: the session is removed and commands are no longer accepted. Then remove the server from your MCP client settings.
FAQ
Is a separate server or gateway needed?
No, exchange goes through files in the user profile folder on the same computer, with no intermediate server.
Can the agent change data in the database?
Only if Database write is switched on in the processor form; it is off when the form opens.
Does the bridge work with old configurations?
Yes, in the thin client in managed application mode and in the ordinary application thick client, which has an ordinary form.
Which tools does the agent see?
Ten: sessions, ping, query, eval, execute, metadata, find, usages, result and cancel.
What about a long query?
A command waits up to `timeout`, at most 280 seconds. If it does not finish, it returns an ID and the answer is fetched with the `result` tool.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsAn MCP server built as a 1C external processing that gives Claude access to metadata, queries and the event log of any configuration
A 1C external data processor with MCP and REST API: queries, metadata, event log and code execution without changing the configuration
SessionBridge: a temporary bridge to 1C over RDP
SessionBridge
A temporary MCP bridge to 1C over a client's RDP session with no infobase publishing: export, read and write through a tunnel that closes after the task
A 1C extension that runs an MCP server inside the 1C:Enterprise client and lets you write your own tools in BSL
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 bridge to BSL Language Server: navigation, diagnostics and refactoring of 1C and OneScript code for agents
README in short
The README explains the folder-based exchange scheme, requirements, installation with uv, how the form and log work, confirmed result release, a custom exchange folder, a table of ten tools and ordinary application specifics.