Standalone Rust MCP for 1C help
mcp-1c-help
A lightweight Rust MCP server with HTTP/SSE transport that searches the official 1C:Enterprise 8.3 platform help via SQLite FTS5
- 1 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- A Rust server parses .hbk help files and builds a SQLite FTS5 index
- Runs over HTTP/SSE without auth, keep the port closed
Install
- Works in
- Services
Manual install
cargo build --releaseBuilds from source, requires Rust.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- A Rust server parses .hbk help files and builds a SQLite FTS5 index
- Runs over HTTP/SSE without auth, keep the port closed
This is third-party code. Review the repository files before installing.
What it does
The server parses the platform help HBK containers (general syntax, the query language, the built-in language) and builds a SQLite FTS5 full-text index. It runs over HTTP/SSE transport, so it works with any MCP client supporting it: Claude Desktop, Cursor IDE, Copilot and others. Four tools: search help with a category filter, get a topic's full content by ID, check platform version status and topic count, and force reindexing. The installed platform path is auto-detected or set via an environment variable, and the server port is also configurable through a variable.
Who it is for. For 1C developers who want a lightweight standalone platform help MCP server with HTTP/SSE transport and no Python dependencies.
Good fit when
- You want a 1C help MCP server without installing Python and its dependencies
- Your MCP client supports HTTP/SSE, not just stdio
- You want simple one-call reindexing when the platform is updated
Not a fit when
- Your MCP client supports only stdio, not HTTP/SSE
- You need meaning-based rather than text search over help: this server offers only FTS5
Example request
Search the 1C help for the topic on regular expressions in string functions and show the full textMCP
- Transport
- sse
- Authentication
- not required
Environment variables
ONEC_HELP_PATH- Explicit path to the installed 1C platform when autodetection fails.
MCP_HELP_PORT- The server port, defaulting to 3010.
Limitations
Transport is HTTP/SSE only, stdio is not supported, which matters when choosing an MCP client. Search is purely full-text via FTS5, with no vector embeddings. An installed 1C:Enterprise 8.3 platform is needed for access to the .hbk help files.
How to disable. Stop the mcp-1c-help process and remove the 1c-help entry from your MCP client config.
FAQ
Is stdio supported?
No, only HTTP/SSE, the README lists it as the only transport.
How do I refresh the index after a platform update?
The reindex_1c_help tool forces reindexing without restarting the server.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise tools1C Platform Help MCP Server
Onec Platform Help MCP Server
An MCP and REST server with hybrid search (BM25 plus semantic) over the official 1C:Enterprise platform help
1C built-in language help: a local MCP server
itcoolmcplang1c
A Rust MCP server that gives an agent the 1C built-in language reference from your own platform install, with a knowledge base built and kept entirely local
Ten MCP servers for 1C development: platform reference, targeted object dump and load, COM, storage, file search and BSL Language Server
An MCP server for searching the 1C platform syntax reference: global functions, object methods and properties via Elasticsearch
Gyrfalcon: 1C code navigation MCP
gyrfalcon
A single dependency-free Rust binary with no network calls: indexes a 1C configuration export and answers call-graph and metadata questions in milliseconds
An MCP server and CLI for 1C that build full-text and vector indexes over the platform's .hbk help and parse PascalCase Russian identifiers
README in short
The README gives an architecture diagram: an MCP client talks to the Rust server over HTTP/SSE, with an internal HBK parser for the shcntx_ru, shquery_ru and shlang_ru contexts and a SQLite FTS5 index. It gives the cargo build --release build command, automatic and explicit runs specifying the platform path and port, and a table of four MCP tools with the search_1c_help parameters.