1C metadata MCP server
1C_MCP_metadata
An MCP server over a 1C extension's HTTP service that exposes configuration metadata, searches objects and validates query syntax
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- The tools only read the metadata structure and validate query syntax, there is no write access
- The HTTP service is published without documented authentication, so access should be restricted at the publication level
Install
Manual install
{
"mcpServers": {
"1c-metadata": {
"command": "powershell",
"args": [
"-ExecutionPolicy", "Bypass",
"-NoProfile",
"-WindowStyle", "Hidden",
"-File",
"C:\\mcp-1c\\mcp-1c-powershell.ps1",
"-BaseUrl",
"http://localhost/kirill/hs/mcpmetadata"
]
}
}
}Example from the README, replace the path and -BaseUrl with your own.
This is third-party code. Review the repository files before installing.
What it does
The project has a 1C extension with an MCPmeta_MCPСервис HTTP service and a PowerShell script that wraps calls to that service in MCP over stdio. The agent gets the configuration's metadata structure filtered by object type, detailed info about a specific object, object search by name, synonym and comment across catalogs, documents, registers, reports, processing objects and other types, plus 1C query-language syntax validation with an error description. SSE mode was not implemented due to technical difficulties, so the connection goes through a stdio wrapper.
Who it is for. For 1C developers who need to quickly give an AI agent a specific configuration's metadata structure without a manual export.
Good fit when
- You want an agent to search metadata objects by name or synonym directly in the live infobase
- You need to validate an agent-generated query's syntax before running it
- You need the detailed structure of a specific catalog, document or register
Not a fit when
- You need SSE or network HTTP transport without PowerShell: this is not implemented in the current version
- The script path contains Cyrillic characters: the README explicitly asks to avoid them
Example request
Find all metadata objects related to Nomenclature and show the Nomenclature catalog's structureLimitations
No pushes for over a year, and no license is specified. The extension must be installed into the configuration by hand and the MCPmeta_MCPСервис HTTP service published, and the bridge to MCP only works through the PowerShell script over stdio. The README says nothing about the HTTP service's access rights or authentication.
How to disable. Remove the server from the MCP client config, disable the MCPmeta extension in the 1C infobase and unpublish the HTTP service.
MCP
- Transport
- stdio
- Authentication
- not required
Security check
- The tools only read the metadata structure and validate query syntax, there is no write access
- The HTTP service is published without documented authentication, so access should be restricted at the publication level
README in short
The README describes an MCP server implementation for 1C:Enterprise with an extension that publishes an HTTP service and a PowerShell script for stdio mode. Four tools are listed: getting the metadata structure, detailed object info, object search and query validation. It gives an example mcpServers config with a powershell command and -BaseUrl parameters.
FAQ
Why PowerShell instead of direct HTTP or SSE?
The author notes that implementing SSE in the current form is problematic, so a PowerShell script bridges to stdio by calling the extension's HTTP methods.
Which metadata object types are supported?
Catalogs, documents, information and accumulation registers, reports, data processors, characteristic type plans, chart of accounts, exchange plans, business processes and tasks.
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