1c-mcp-tools: the application layer of 1C MCP
1c-mcp-tools
A 1C extension with processing-report containers for MCP tools, the application layer where transport and aggregation live in separate components
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- The built-in tools read configuration metadata
- The architecture is designed for arbitrary tool containers a developer can add themselves, including potentially write-capable ones
Install
Manual install
Attach the extension from src/1c_ext to the infobase, deploy the web-transport-addin transport and the v8-session-manager aggregator separately per their own docs, then add your own mcp_-prefixed tool containers to the mcp_КонтейнерыИнструментов subsystem following the example in src/1c_ext/agents.md.
This is third-party code. Review the repository files before installing.
What it does
The repository contains only the XML export of a 1C extension with subsystems for hosting MCP tools, resources and prompts: container processing reports describe and run tools through the exported ДобавитьИнструменты and ВыполнитьИнструмент methods. Currently the extension ships list_metadata_objects, get_metadata_structure and a 1csyntax reference resource, plus a legacy HTTP endpoint, mcp_APIBackend, left over from the original implementation. The extension itself doesn't provide transport: the README explicitly states that the Python proxy, Docker infrastructure and a ready .cfe were removed from this repository, and publishing and aggregating the MCP surface is left to separate architecture components (web-transport-addin, wt-mcp-adapter, v8-session-manager).
Who it is for. For 1C developers who already have a transport and MCP session-manager stack for 1C and want a ready application layer to host their own tool containers.
Good fit when
- You already have transport (web-transport-addin) and a session aggregator (v8-session-manager) and want an application layer with sample tool containers
- You want an example of how to structure your own MCP tools inside a 1C extension by subsystem
- You just need a basic metadata reading tool, list_metadata_objects and get_metadata_structure
Not a fit when
- You need a self-contained, immediately working MCP server: the repository explicitly states it's no longer a standalone proxy server or transport layer
- You don't have access to the rest of the architecture's components (web-transport-addin, wt-mcp-adapter, v8-session-manager), some of which may not be published separately
- You need Docker infrastructure, a ready .cfe or MCP client config examples: the README explicitly lists these as removed from the repository
Example request
Show the structure of the Nomenclature catalog metadata object via the get_metadata_structure toolLimitations
The repository contains only the extension's sources, with no build, transport or client settings, and doesn't run as an MCP server on its own. The project technically started as a fork of RooLee10/1c-mcp-tools, based on vladimir-kharin/1c_mcp, but the README explicitly states significant functionality is already detached from the original implementation and compatibility with upstream isn't planned. The legacy mcp_APIBackend endpoint is left over from the original implementation and isn't the project's target architecture.
How to disable. Disable or remove the extension with the MCP containers in the infobase.
MCP
- Transport
- http
- Authentication
- not required
Security check
- The built-in tools read configuration metadata
- The architecture is designed for arbitrary tool containers a developer can add themselves, including potentially write-capable ones
README in short
The Russian README explains the repository's place in a broader 1C MCP architecture alongside v8-runner, web-transport-addin, wt-mcp-adapter and v8-session-manager, lists the extension's key objects and subsystems, describes the target model for adding new tool containers with a BSL code example, gives the project's origin as a fork of RooLee10/1c-mcp-tools from vladimir-kharin/1c_mcp with a note that functionality has already diverged, and separately lists what's no longer in the repository (the proxy, Docker, the cfe, client settings, batch scripts). MIT license.
FAQ
Can this repository be used as a standalone MCP server?
No, the README states the Python proxy, Docker image and ready .cfe were removed; transport and aggregation live in other architecture components.
How do you add your own tool?
Create a processing report prefixed mcp_, include it in the mcp_КонтейнерыИнструментов subsystem, and implement the ДобавитьИнструменты and ВыполнитьИнструмент methods in the manager module.
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