1c-bsp-context MCP

A Kotlin MCP server that indexes a Standard Subsystems Library export and answers the agent with exact procedure signatures, file path and line

  • 3 ★ on the repository
  • Last commit
  • MIT
MCP server

Extended access

Why this level

  • Runs a Java server that builds an in-memory index of the SSL EDT export
  • Reads local files only and does not connect to an infobase
All reasons and checks
Russian stack

phill752/1c-bsp-context

Install

Manual install

./gradlew bootJar && java -jar build/libs/mcp-bsp-context-0.1.0.jar --mode stdio --bsp-path /path/to/ssl-edt-export

Local build and stdio launch.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Runs a Java server that builds an in-memory index of the SSL EDT export
  • Reads local files only and does not connect to an infobase

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 example

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.

Limitations

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.

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.

Discussion

No questions or reviews yet.

Russian stack

MCP server with the 1C platform reference and validation of BSL code against the real API of a chosen platform version

MCP serverExtended access33Repository stars
Russian stack

An MCP server for Codex with semantic search over 1C's Standard Subsystems Library documentation

MCP serverExtended access3Repository stars
Russian stack

A single-binary Go MCP server: the agent sees 1C metadata, searches code, runs read-only queries and writes accurate BSL

MCP serverBroad access255Repository stars
Russian stack

A local OneScript MCP server for searching a 1C configuration dump right from Cursor

MCP serverExtended access18Repository stars

1C configuration graph MCP server

1C Configuration MCP Server

Russian stack

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

MCP serverExtended access4Repository stars

1C platform reference over MCP

mcp-bsl-platform-context

Russian stack

An MCP server with the 1C syntax assistant reference: search functions, types, methods, properties and constructors from the installed platform

MCP serverExtended access207Repository stars

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.

README badge

Report a problem