SkillFoxx

Type a name, a task or a service

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

MCP serverMedium riskRussian stack

1c-neurofish/onec-client-mcp-devkitAuthor: 1c-neurofish

Install

v8-runner tools download client-mcp --sources

The method from the v8-runner README: downloads the extension sources from the latest release. Without --sources a ready cfe goes to build/tools.

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 tools

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.

MCP

Transport
http
Authentication
not required

Security check

  • Opens a network port in the 1C client
  • Tools run BSL code in the user's session

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.

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.

Editors’ pick

A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review

PluginMedium risk286.8K
Editors’ pick

Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture

SkillLow risk262.2K
Editors’ pick

GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation

CLIMedium risk136.8K

Reference MCP servers

Model Context Protocol servers

Editors’ pick

Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything

MCP serverMedium risk90.3K