1c-templates-mcp
An MCP server with hybrid search over 2262 community BSL code templates and a CRUD web interface built on Monaco Editor
- 31 ★ on the repository
- Last commit
Broad access
Why this level
- MCP tools add, update and delete templates in the SQLite store
- The MCP endpoint and web UI are open without auth on the chosen port
- Embeddings can be computed through an external OpenAI-compatible API
Install
- Works in
- Services
Manual install
cd deploy && docker compose up -dInstall from the ready desko77/1c-templates-mcp Docker Hub image, the recommended method.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- MCP tools add, update and delete templates in the SQLite store
- The MCP endpoint and web UI are open without auth on the chosen port
- Embeddings can be computed through an external OpenAI-compatible API
This is third-party code. Review the repository files before installing.
What it does
The server holds a database of ready-made 1C code templates (over 2200 from the community) and gives an agent six MCP tools: hybrid semantic and full-text search, a paginated list, fetching a template by id, adding, updating and deleting. Data is stored in SQLite as the source of truth and indexed in ChromaDB for vector search; embeddings can come from an OpenAI-compatible API (LM Studio, Ollama) or be computed locally with a SentenceTransformer model, with automatic fallback if the API is unavailable. A full web interface lets you edit templates with BSL highlighting via Monaco Editor. A separate, sizable companion reference for the 1C:ZUP 3.1 API lives in docs/rules and can be attached to an agent as extra context.
Who it is for. For 1C developers who want an agent to reuse vetted code templates and find them by meaning rather than by exact name.
Good fit when
- You need a large ready BSL template database for common tasks, not an empty collection
- You want to search for a template by the meaning of a Russian-language question
- You work with 1C:ZUP and want to attach an agent the companion HR API reference
Not a fit when
- You do not want to run a Docker stack with ChromaDB and an embedding model
- Exact name search is enough without semantics
- You need to edit a template directly in the database without a later export to seed_templates.jsonl: skipping that step loses edits on rebuild
Example request
Find the average earnings calculation template for ZUP and show the code with its descriptionMCP
- Transport
- http
- Authentication
- not required
Environment variables
EMBEDDING_PROVIDER- Embedding provider: auto, local or openai.
OPENAI_API_BASE- URL of the OpenAI-compatible embeddings API, for example a local LM Studio instance.
OPENAI_API_KEYsecret- Key for the OpenAI-compatible API, not needed for local LM Studio by default.
Limitations
There is no license file in the repository. Edits made through the web interface live only in the Docker volume runtime database and are lost on docker compose up --build or volume removal unless exported to seed_templates.jsonl beforehand. The RoSBERTa model for better Russian-language quality needs a GPU or 5-10 minutes of CPU indexing. The GPU profile requires the nvidia-container-toolkit to be installed.
How to disable. Stop the container with docker compose down and remove the server from your MCP client config.
FAQ
Is an external embedding service required?
No, by default the auto mode tries an OpenAI-compatible API and falls back to a local model if it is unavailable.
How do you avoid losing a template added via the web UI?
Export the runtime database to seed_templates.jsonl with the export_to_jsonl.py script before rebuilding the image or removing the volume.
How is 1c-templates-mcp different from searching 1C code templates across sites?
The server stores a base of over 2200 community BSL templates and gives the agent six MCP tools: hybrid semantic and full-text search, a paginated list and template retrieval. It has a CRUD interface on Monaco Editor.
How do I run 1c-templates-mcp and keep the templates I add?
Run in Docker: cd deploy && docker compose up -d. Templates added through the web interface live in a Docker volume, do not delete it and back it up. It connects to Claude Code and Cursor.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise tools1C Templates MCP server
MCP сервер шаблонов 1С
An MCP server for storing and searching your own BSL code templates, with a web editor and syntax highlighting
Semantic search over 1C platform help
1c-sntx-sem
An MCP server for Cursor and Claude Desktop with hybrid embeddings and BM25 search over 1C platform help, the query language and the standard subsystems library
A single-binary Go MCP server: the agent sees 1C metadata, searches code, runs read-only queries and writes accurate BSL
A read-only MCP service for hybrid 1C BSL code search: BM25 plus vector search, deduplication and reranking
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
An MCP server for searching the 1C platform syntax reference: global functions, object methods and properties via Elasticsearch
README in short
The README describes installing from a ready Docker image or building from source with cpu and gpu profiles, a table of six MCP tools, web interface routes, a full list of config variables, an architecture diagram (FastAPI, SQLite, ChromaDB, embeddings), three embedding provider modes, the process of adding a template via JSONL or the web UI with a data-loss warning, and a separate section on the 1C:ZUP companion reference with setup instructions for Claude Code and Cursor.