1c-bsp-context
A Kotlin MCP server that indexes a Standard Subsystems Library export and answers the agent with exact procedure signatures, file path and line
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- Only reads the local SSL export and does not connect to any infobase
Install
Manual install
./gradlew bootJar && java -jar build/libs/mcp-bsp-context-0.1.0.jar --mode stdio --bsp-path /path/to/ssl-edt-exportLocal build and stdio launch.
This is third-party code. Review the repository files before installing.
What it does
The server parses an EDT-format export of the SSL configuration (XML and .bsl) and builds an in-memory index of common modules, procedures and subsystems. The agent gets six tools: search by procedure and subsystem, a full procedure card with parameters and a call example, a module overview with its exported procedures, a lightweight procedure list without source code, a subsystem overview, and a ready code snippet with placeholder parameters. Every answer points to the file path and line number, and fields missing from the docblock are explicitly marked as undocumented rather than guessed.
Who it is for. For 1C developers who work with SSL often and want the agent to stop inventing signatures for common procedures.
Good fit when
- The agent needs to call SSL functions with exact parameters
- You need a verifiable answer pointing to the source file and line
- You need an SSL subsystem overview before extending it
Not a fit when
- You have no local EDT export of SSL: the server does not download or store the library itself
- You need analysis of your own configuration code, not the standard SSL
Example request
Find the SSL procedure for checking required attribute fill-in and show a call exampleLimitations
The repository does not include SSL itself: the user must supply their own export and is responsible for its licensing terms. Needs Java 17 and a local EDT-format export. The index lives only in the process memory.
How to disable. Stop the server process or remove it from your MCP client configuration.
MCP
- Transport
- stdio, sse
- Authentication
- not required
| Environment variables | |
|---|---|
| BSP_SOURCE_PATH required | Path to the local EDT export of SSL, inside the container or on disk. |
| SSE_ADDRESS | Listen address for SSE mode in Docker, usually 0.0.0.0. |
Security check
- Only reads the local SSL export and does not connect to any infobase
README in short
The README describes indexing around 800 modules and 20,000 SSL procedures in under two seconds, a Kotlin, Spring Boot and Spring AI stack, local stdio or SSE launch plus Docker, a table of six MCP tools, and connection examples for Cascade, Kilo Code and Claude Desktop. It notes the MIT license covers only the server code, not SSL itself.
FAQ
Does the server ship with SSL included?
No, the repository has no SSL source; you supply your own EDT-format export.
Can the response be shortened?
Yes, the compact=true parameter on get_bsp_procedure_info drops the source code and example, keeping the description and parameter types.
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