SkillFoxx

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

  • 63 ★ on the repository
  • Last commit
MCP server

Extended access

Why this level

  • Runs a PowerShell bridge that passes agent requests to the HTTP service of a 1C extension
  • Requires installing an extension in the configuration and publishing an HTTP service with no documented authentication
  • The tools only read metadata and check query syntax
All reasons and checks
Russian stack

artesk/1c_mcp_metadataAuthor:artesk

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.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Runs a PowerShell bridge that passes agent requests to the HTTP service of a 1C extension
  • Requires installing an extension in the configuration and publishing an HTTP service with no documented authentication
  • The tools only read metadata and check query syntax

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 structure

MCP

Transport
stdio
Authentication
not required

Limitations

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.

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.

Discussion

No questions or reviews yet.

All 1C:Enterprise tools
Russian stack

A Python proxy between an MCP client and a 1C HTTP service: reads metadata, object structure and predefined data, with optional OAuth2

MCP serverExtended access9
Russian stack

A 1C extension that runs an MCP server inside the infobase: metadata tools out of the box and custom tools in BSL

MCP serverBroad access574
Russian stack

An MCP server and portable admin tool for analyzing an exported 1C XML configuration: object listing, metadata structure, code search

MCP serverExtended access2
Russian stack

A Docker service that indexes a JSON export of 1C configuration metadata and gives an agent fast object search by name and synonym

MCP serverExtended access9
Russian stack

A single-binary Go MCP server: the agent sees 1C metadata, searches code, runs read-only queries and writes accurate BSL

MCP serverBroad access255
Russian stack

A Docker server with a read-only core and pluggable modules: metadata, code, forms and relations of several 1C configurations through one MCP contract

MCP serverExtended access12

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.

README badge

Report a problem