BSP Documentation MCP
An MCP server for Codex with semantic search over 1C's Standard Subsystems Library documentation
- 3 ★ on the repository
- Last commit
Extended access
Why this level
- Runs a Python server via PowerShell and searches local BSP documentation
- Each query text goes to OpenRouter with your key to get an embedding
Install
- Works in
- Services
Manual install
powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\install.ps1Run inside the cloned or unpacked repository on Windows. The installer copies the server to %USERPROFILE%\.codex\mcp\bsp-docs-mcp and creates a Python environment.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Runs a Python server via PowerShell and searches local BSP documentation
- Each query text goes to OpenRouter with your key to get an embedding
This is third-party code. Review the repository files before installing.
What it does
The server looks up recommended methods in the 1C Standard Subsystems Library (BSP) documentation by meaning rather than exact word match. It ships with the 3.1.11 documentation and a ready SQLite FTS5 index, so no rebuild is needed. The agent first detects the project's BSP version from ParentConfigurations.bin, then searches a section and reads it in full. Turning a text query into a vector calls out to OpenRouter's embedding model.
Who it is for. For 1C developers who build on BSP and want Codex to find the right documented API on its own.
Good fit when
- You need to find a recommended BSP method by task description rather than exact name
- Codex is working on a 1C configuration built on BSP 3.1.x
- You need to detect a project's BSP version from its configuration file
Not a fit when
- You are not on Windows: the installer and instructions target Windows 10/11 only
- You have no OpenRouter key and do not want an external account just for docs search
- You need BSP documentation outside the 3.1 family
Example request
Detect this project's BSP version and find the recommended API for long-running operationsMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
OPENROUTER_API_KEYrequired, secret- OpenRouter key used to embed the search query
Limitations
Setup and instructions target Windows only, and you need Python 3.12 plus an OpenRouter key to vectorize new queries. No license file is present. The bundled index covers only the BSP 3.1 family; other versions need their own docs and index. It is a small project maintained by a single author.
How to disable. Remove the mcp_servers.bsp_docs block from %USERPROFILE%\.codex\config.toml and delete the %USERPROFILE%\.codex\mcp\bsp-docs-mcp folder.
FAQ
Do I need to build the index myself?
No, the index for BSP 3.1.11 ships with the project. OpenRouter is only needed to vectorize a new search query.
Does it work without Windows?
The README and install.ps1 target Windows 10/11 only, and no other setup path is documented.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsA Kotlin MCP server that indexes a Standard Subsystems Library export and answers the agent with exact procedure signatures, file path and line
An MCP server with full-text search over local 1C:Element documentation, including your own markdown and PDF files
An MCP server for Claude Code: full-text search over multiple 1C XML+BSL configuration exports in a local SQLite FTS5 database
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 stdio MCP server that indexes a 1C structure XML export and code into SQLite and gives an agent search over objects and procedures
A SQLite code index with MCP tools for search, call graphs and metadata, including 1C dumps from Designer and EDT
README in short
The Russian README walks through setup via install.ps1 or manually: cloning, a Python virtual environment, the OPENROUTER_API_KEY variable and a Codex config block. It documents four MCP tools: BSP version detection, search, section reading and a list of installed versions. It explains OpenRouter token cost for index building versus search, and tells the agent to ask for the BSP version instead of guessing it.