1C MCP Symbiosis

A ready-made Cursor setup: a live 1C infobase via LN_MCP plus seven Docker containers of MCP_Distr static analysis for code and BSP search

MCP server

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

  • LN_MCP runs execute_code and execute_query against the live database
  • The MCP_Distr containers open several network ports on the host
All reasons and checks
Russian stack

lordnikos/1c-mcp-symbiosis

Install

Manual install

{
  "mcpServers": {
    "ln-mcp-csp-test": {
      "url": "http://localhost:81/CSP_TEST/hs/mcp/rpc",
      "headers": { "Authorization": "Basic <REPLACE_WITH_YOUR_BASE64_USER:PASSWORD>" }
    },
    "1c-syntax-checker-mcp": { "url": "http://localhost:8002/mcp" },
    "1c-code-checker-mcp": { "url": "http://localhost:8007/mcp" },
    "1c-templates-mcp": { "url": "http://localhost:8004/mcp" },
    "1c-ssl-mcp": { "url": "http://localhost:8008/mcp" },
    "1c-docs-mcp": { "url": "http://localhost:8003/mcp" },
    "1c-code-metadata-mcp": { "url": "http://localhost:8000/mcp" },
    "1c-graph-metadata-mcp": { "url": "http://localhost:8006/mcp" }
  }
}

A shortened version of the repo's cursor/mcp.json, eight LN_MCP and MCP_Distr servers.

This is third-party code. Review the repository files before installing.

What it does

The repository does not include its own MCP server; instead it assembles and documents a combination of two other MCP layers for 1C development in Cursor. LN_MCP connects to a live infobase through a web publication and provides query execution, metadata reads and an extension list. MCP_Distr brings up seven Docker containers: metadata and code search, a syntax helper, platform help, templates, a Neo4j dependency graph, and checks including BSP. The project ships a cursor/mcp.json config for eight servers, an agent behavior rulebook USER-RULES.md, an accumulated fixes log memory.md, and a PowerShell script that checks all servers respond.

Who it is for. For 1C developers on Windows with WSL2 who want to bring up both live database access and configuration static analysis for Cursor in one setup.

Good fit when

  • You need both live infobase data and static analysis of a dumped configuration in one Cursor project at once
  • The team already uses vibecoding1c.ru's MCP_Distr and wants a standard connection config
  • You want a log of accumulated issues and fixes for this MCP server combination

Not a fit when

  • You need just one layer, live data only or static analysis only: connecting it directly is simpler
  • You do not have Windows with WSL2 and Docker Desktop: the setup targets exactly this environment
  • You are not working in Cursor

Example request

Run a query against the live base through LN_MCP, then use MCP_Distr to check where else in the configuration this function is used

Limitations

The setup is not MCP server code itself but configuration and documentation layered on LN_MCP and MCP_Distr from vibecoding1c.ru, so it depends on their availability and versions. It needs Windows 10 or 11 with WSL2, Docker Desktop, and a live infobase web publication. The README's install prerequisites section is brief, with some steps moved into separate docs files.

How to disable. Remove the server entries from cursor/mcp.json and stop the MCP_Distr containers with docker-compose down in the docker/Graph_metadata_search folder.

MCP

Transport
http
Authentication
not required
Environment variables
Environment variables
LN_MCP config (cursor/.dev.env.example)
required
Connection settings for the live infobase web publication.

Security check

  • LN_MCP runs execute_code and execute_query against the live database
  • The MCP_Distr containers open several network ports on the host

README in short

The README draws a two-layer MCP diagram with ports and containers, and lists what the setup includes: a Cursor config, agent rules, a fixes log, env templates, and check and metrics scripts. The install section for a new developer starts with Windows 10 or 11, WSL2 and Docker Desktop prerequisites, with further detail moved into docs/ARCHITECTURE.md and docs/TROUBLESHOOTING.md.

FAQ

Are these two different MCP servers?

Yes, LN_MCP talks to the live base over HTTP JSON-RPC, while MCP_Distr is seven Docker containers for static analysis; they are not connected to each other.

Does it need Docker for both parts?

No, only for MCP_Distr. LN_MCP talks directly to the infobase web publication over localhost.

Editors’ pick

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

PluginMedium riskNo VPN needed292.5KRepository stars
Editors’ pick

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

SkillLow risk271.4KRepository stars
Editors’ pick

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

CLIMedium riskNo VPN needed139.3KRepository stars

Reference MCP servers

Model Context Protocol servers

Official

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

MCP serverMedium risk90.6KRepository stars
Foxx AI1C MCP Symbiosis

I am Foxx AI and I have already vetted this tool. Ask about install, setup or anything else, and I will keep it simple.