1c-lsp-mcp-skill

---
name: 1c-lsp
description: "Use when developing, reviewing, or debugging 1C:Enterprise 8.3 / BSL code in a repository connected to the local `lsp-skill` service and you need semantic navigation through `bsl-language-server`. Covers `symbols`, `definition`, `references`, `incoming-calls`, `outgoing-calls`, and `workspace-symbols` for configured 1C projects. Prefer this skill over plain text search when you need symbol-aware answers about procedures, functions, variables, common modules, forms, object modules, and cross-file usage in 1C (`1С`) projects."
---

# 1c-lsp

Use the local `lsp-skill` CLI as the primary semantic navigation tool while working on 1C code.

Treat it as a thin wrapper over `bsl-language-server` and LSP. Use it first for symbol-aware navigation, then open the real source files to inspect surrounding code before editing behavior.

## How It Connects

The CLI discovers `PROJECT_ID` from a `.env` file in the current directory or a parent directory, and discovers the server address from `runtime.json`.

If the project is not ready (starting, stopped, error), commands will return an error — handle it when it happens instead of checking upfront. You can run `lsp-skill status` to inspect project state if needed for troubleshooting.

## Output Format

Navigation commands read `use_toon_format` from `lsp-skill` config.

- `false` keeps pretty JSON.
- `true` switches to compact TOON with aliases such as `range -> range_sl/range_sc/range_el/range_ec`, `selectionRange -> selection_range_*`, `location -> location_*`, `targetUri -> target_uri`, `containerName -> container_name`, and inlined `from_*` / `to_*`.

Example:

```text
references[2]{range_ec,range_el,range_sc,range_sl,uri}:
  5,1,0,1,"file:///a.bsl"
  9,2,4,2,"file:///b.bsl"
```

## Use Safe Coordinates And Paths

Each project has two root paths:

- **`root_path`** — the BSL root where `bsl-language-server` indexes code (e.g. `d:\projects\myproject\1c-src`).
- **`project_root_path`** — the root of the entire project where LLM agents and CLI run from (e.g. `d:\projects\myproject`).

Pass `file_path` **relative to `project_root_path`**. The server resolves the path and verifies it falls inside `root_path` automatically.

- Do not use absolute paths. The server rejects absolute or escaping paths.
- Preserve the exact directory names, including Cyrillic segments.
- Convert editor coordinates carefully: LSP `line` and `character` are zero-based.
- Re-check the exact symbol position before calling `definition` or `references`. Off-by-one mistakes are common when converting from editors or code review comments.