BSP Documentation MCP
An MCP server for Codex with semantic search over 1C's Standard Subsystems Library documentation
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- Only reads and searches local documentation and never changes the 1C database
- The search query text is sent to OpenRouter to get an embedding
Install
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.
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 operationsLimitations
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.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| OPENROUTER_API_KEY required, secret | OpenRouter key used to embed the search query |
Security check
- Only reads and searches local documentation and never changes the 1C database
- The search query text is sent to OpenRouter to get an embedding
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.
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.
Related
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Skills for real engineers by Matt Pocock
Skills For Real Engineers
Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
Reference MCP servers
Model Context Protocol servers
Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything