1C Metacode MCP Server
A Neo4j graph of 1C configuration metadata and code with MCP tools, a web console and a built-in search agent
- 111 ★ on the repository
- Last commit
- AGPL-3.0
Extended access
Why this level
- Starts Neo4j and an HTTP server whose MCP endpoint has no built-in auth
- Can send code and metadata to an external embeddings or LLM provider
Install
- Works in
- Services
Manual install
docker compose up -dBefore starting, prepare .env and docker-compose.yml from the examples and place the dump under data/prj1.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Starts Neo4j and an HTTP server whose MCP endpoint has no built-in auth
- Can send code and metadata to an external embeddings or LLM provider
This is third-party code. Review the repository files before installing.
What it does
The server loads configuration metadata into Neo4j from a configuration report or XML dump, along with extensions, forms, roles, event subscriptions and predefined values. From modules it takes routine signatures and bodies, builds a call graph and offers full-text, vector and hybrid code search. Objects are linked through attributes, document register movements and access rights, and LLM summaries can be generated per object. Agents reach this over MCP and people through a web console; data reloads incrementally on a schedule.
Who it is for. For 1C teams maintaining large configurations with extensions who want to give an agent a full map of relationships.
Good fit when
- You need to see which objects a change to an attribute or register affects
- The configuration has several extensions and you need to compare their objects with the base
- You need to find routines by meaning, not only by name
Not a fit when
- You cannot run Docker with Neo4j on a machine or server
- Plain search over the dump is enough without a graph database
Example request
Use 1c-metacode to find all documents that post to the counterparty settlements register and their posting handlersMCP
- Transport
- http, sse
- Authentication
- not required
Environment variables
NEO4J_PASSWORDrequired, secret- Password for the neo4j user
PROJECT_NAMErequired- Project name matching the data folder
WEB_CONSOLE_ENABLED- Enables the web console
MCP_USE_SSE- Switches the transport to SSE
Limitations
Requires Docker, Docker Compose and free ports for Neo4j and the server. Semantic search and object summaries need an embeddings or LLM provider, meaning keys and possibly a cloud API whose availability from Russia depends on the provider. AGPL-3.0 licensed.
How to disable. Remove the 1c-metacode block from the client MCP config and stop the containers with docker compose down.
FAQ
Where does metadata come from?
From the text configuration report or directly from the XML dump; code comes from the XML dump.
Can it hold several infobases?
Yes, it supports multiple projects, each made of a base configuration plus extensions, with search filtered per project.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsLoads a 1C configuration XML export into Neo4j and gives read-only MCP access to metadata, BSL routines and rights via text and full-text search
An MCP server and portable admin tool for analyzing an exported 1C XML configuration: object listing, metadata structure, code search
1C configuration graph MCP server
1C Configuration MCP Server
An MCP server builds a metadata and call graph from a 1C configuration's XML and BSL export, with optional semantic search via an external embedder and Qdrant
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
A local knowledge graph of a 1C configuration for an agent: Memgraph and ONNX embeddings with no cloud, for bases with hundreds of thousands of routines
A stdio MCP server that indexes a 1C structure XML export and code into SQLite and gives an agent search over objects and procedures
README in short
The README lists what gets loaded and the graph model with a node and relationship diagram. It runs through Docker Compose with Neo4j, exposing Neo4j Browser, an MCP server over streamable HTTP or SSE, and a token-protected web console. The tool reference, search modes, extensions and the built-in agent are documented separately in docs/. AGPL-3.0 licensed.