1C Client MCP Server
A 1C extension that runs an MCP server inside the 1C:Enterprise client and lets you write your own tools in BSL
- 68 ★ on the repository
- Last commit
- LGPL-3.0
Extended access
Why this level
- Opens a network port in the 1C client
- Tools run BSL code in the user's session
Install
- Works in
- Services
Manual install
v8-runner tools download client-mcp --sourcesThe method from the v8-runner README: downloads the extension sources from the latest release. Without --sources a ready cfe goes to build/tools.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Opens a network port in the 1C client
- Tools run BSL code in the user's session
This is third-party code. Review the repository files before installing.
What it does
The project runs an MCP server in the 1C client via a WebTransport external component and handles JSON-RPC requests. It supports MCP tools, resources and prompts, with a handler registry, logging and a server control form. A tool is registered in BSL: description, input schema and a handler procedure. The server can start from the form or right at client launch with a command-line parameter for port and timeout.
Who it is for. For 1C developers who want to give an agent access to a live client of their configuration through custom tools.
Good fit when
- You need MCP tools written in BSL that run in the 1C client context
- You want an agent to drive a test client while debugging
- You need a base for agent integration with a configuration without an external service
Not a fit when
- You need a ready tool set rather than a framework
- You need stable interfaces for production
Example request
Connect to the 1C client MCP server on port 8080 and list its toolsMCP
- Transport
- http
- Authentication
- not required
Limitations
The project has no stable release, and interfaces and internal APIs may change. It needs 1C:Enterprise and the AddIn.WebTransport.mcp external component. Extension sources are in EDT format. The README does not describe installing the extension into an infobase.
How to disable. Disable or remove the client-mcp extension in the infobase and delete the server from your MCP client config.
FAQ
What port is used by default?
8080 with a 900 timeout. Both are set in the JSON config, and the port can also be passed as mcpPort in the launch string.
How do I add my own tool?
Register it in the registry with a description and parameter schema, then write a handler function. The README shows an addition tool example.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsMCP server inside 1C
1c_mcp
A 1C extension that runs an MCP server inside the infobase: metadata tools out of the box and custom 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
A 1C-extension MCP server with 93 tools for reading, writing, posting and administering ERP, Trade Management, UPP and Accounting
A 1C external data processor with MCP and REST API: queries, metadata, event log and code execution without changing the configuration
A 1C extension built on vladimir-kharin/1c_mcp that adds execution of arbitrary built-in-language code right in the infobase context
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
README in short
The README describes an MCP server running inside the 1C client through an external component and warns there is no stable release. It shows command-line launch parameters, a minimal JSON config, screenshots of the control form and MCP Inspector, and a BSL tool registration example. Architecture and decisions live in separate documents. LGPL-3.0 license.