mcp-1c-tools

Name: mcp-1c-tools
Author: comol

388stars86forks

How to install mcp-1c-tools?

comol/ai_rules_1c/mcp-1c-tools

$npx -y skills add comol/ai_rules_1c --skill mcp-1c-tools

Installs into the current project.

Summary

Catalog of MCP servers for 1C development — search, code navigation, metadata, code review, docs, ITS, templates. Use whenever a 1C task requires calling tools from any 1c-*-mcp / 1C-*-mcp server. Each server has its own detail file under docs/ — load it when you are about to c

Files · 1

View on GitHub

SKILL.md

1	# MCP tools for 1C — dispatcher
2
3	This skill is the single source of truth for the project's MCP server catalog, task→tool mapping, fallback order, and project-index search retries. Detailed per-tool descriptions for each server live in separate files under `docs/`. Load a specific `docs/<server>.md` when you are about to call tools from that server and want to tune parameters; the server must be actually available in the current session (its tools are exposed in the tool schema; the mere presence of an entry in `mcp-servers.json` does not count as availability).
4
5	## What is mandatory vs. conditional
6
7	- Mandatory for risk-bearing 1C work. If a relevant server is exposed, call the fitting MCP tool for BSL / metadata edits or review, metadata XML, forms, integrations, refactoring, performance, runtime errors, platform API checks, impact analysis, syntax / quality validation, and project-memory operations.
8	- Conditional for external knowledge. Use platform docs, БСП / SSL, and ITS MCP tools when the task depends on versioned platform behavior, reusable БСП APIs, or standards compliance. Do not call them for generic prose cleanup or rule-file editing unless such a fact is actually needed.
9	- Not required for Markdown / rules / documentation-only work. For rule files, README, commands documentation, and similar prose-only edits, validate structure, links, paths, and internal consistency instead of calling 1C project MCP tools.
10	- Mandatory before parameter-rich calls. Read `docs/<server>.md` before the first call in the session to every parameter-rich tool listed below, and re-read it when switching tools on that server. A genuinely simple one-shot lookup with obvious arguments may skip the detail file only when it is not in the parameter-rich list.
11
12	### Parameter-rich tools — read the doc first
13
14	For these tools default parameters are usually suboptimal; consult the server's `docs/<server>.md` before the first call in the session and adjust the parameters to the task:
15
16	- `1c-graph-metadata-mcp`: `search_code` (`search_type`, `detail_level`), `search_metadata` (JSON templates), `search_metadata_by_description` (`alpha`, `use_fuzzy`), `trace_impact` (`direction`, `depth`, `relationship_types`), `trace_call_chain` (`direction`, `depth`), `get_object_dossier` (`sections`), `business_search` (`include_structure`, `filter_type`).
17	- `1c-code-metadata-mcp`: `metadatasearch` (`object_type`, `names_only`), `get_method_call_hierarchy` (`direction`, `depth`), `graph_dependencies` (`direction`), `bsl_scope_members` (`member_type`).
18
19	If `docs/<server>.md` conflicts with the descriptor exposed by the current environment, the environment descriptor wins.
20
21	## When to use this skill
22
23	- Before writing code / a query / metadata XML — pick the MCP tool that best fits the task (template search, metadata check, syntax validation, code review).
24	- For impact analysis and code navigation — decide which server to use first (`graph` → `code-metadata` → `Grep` — see Fallback chain below).
25	- For ITS standards (`its_help` → `fetch_its`) and platform documentation (`docinfo` / `docsearch`).
26	- For code templates and project memory (`templatesearch`, `remember`, `recall`).
27
28	> Short obligation rules and verification budgets live in `AGENTS.md → MCP Tool Calling` (sections A, B, C). This skill owns the MCP catalog, routing, and fallback details.
29
30	## Server catalog
31
32	\| Server (id) \| Purpose \| Details \|
33	\|---\|---\|---\|
34	\| 1c-graph-metadata-mcp \| Graph metadata (Neo4j / Cypher): structural object passport, impact analysis, call graph, usage search, business semantic search \| [`docs/1c-graph-metadata-mcp.md`](docs/1c-graph-metadata-mcp.md) \|
35	\| 1c-code-metadata-mcp \| Metadata and BSL code search, navigation (modules, procedures, functions, call hierarchy), forms, XSD schemas, validation \| [`docs/1c-code-metadata-mcp.md`](docs/1c-code-metadata-mcp.md) \|
36	\| 1c-templates-mcp \| Code template library + project vector memory (`remember` / `recall`) \| [`docs/1c-templates-mcp.md`](docs/1c-templates-mcp.md) \|
37	\| 1c-ssl-mcp \| Standard Subsystems Library (БСП / SSL) search \| [`docs/1c-ssl-mcp.md`](docs/1c-ssl-mcp.md) \|
38	\| 1C-docs-mcp \| 1C platform documentation (search by description / by exact name) \| [`docs/1C-docs-mcp.md`](docs/1C-docs-mcp.md) \|
39	\| 1c-code-check-mcp \| 1С:Напарник — code review, technical check, AI rewrite/modify, ITS documentation \| [`docs/1c-code-check-mcp.md`](docs/1c-code-check-mcp.md) \|
40	\| 1c-syntax-checker-mcp \| BSL syntax and style via BSL Language Server: `syntaxcheck` (code as text) and

People who liked this also viewed

6 picks

Type

mcp-1c-tools

388stars86forks

View on GitHub

How to install mcp-1c-tools?

comol/ai_rules_1c/mcp-1c-tools

$npx -y skills add comol/ai_rules_1c --skill mcp-1c-tools

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# MCP tools for 1C — dispatcher
2
3	This skill is the single source of truth for the project's MCP server catalog, task→tool mapping, fallback order, and project-index search retries. Detailed per-tool descriptions for each server live in separate files under `docs/`. Load a specific `docs/<server>.md` when you are about to call tools from that server and want to tune parameters; the server must be actually available in the current session (its tools are exposed in the tool schema; the mere presence of an entry in `mcp-servers.json` does not count as availability).
4
5	## What is mandatory vs. conditional
6
7	- Mandatory for risk-bearing 1C work. If a relevant server is exposed, call the fitting MCP tool for BSL / metadata edits or review, metadata XML, forms, integrations, refactoring, performance, runtime errors, platform API checks, impact analysis, syntax / quality validation, and project-memory operations.
8	- Conditional for external knowledge. Use platform docs, БСП / SSL, and ITS MCP tools when the task depends on versioned platform behavior, reusable БСП APIs, or standards compliance. Do not call them for generic prose cleanup or rule-file editing unless such a fact is actually needed.
9	- Not required for Markdown / rules / documentation-only work. For rule files, README, commands documentation, and similar prose-only edits, validate structure, links, paths, and internal consistency instead of calling 1C project MCP tools.
10	- Mandatory before parameter-rich calls. Read `docs/<server>.md` before the first call in the session to every parameter-rich tool listed below, and re-read it when switching tools on that server. A genuinely simple one-shot lookup with obvious arguments may skip the detail file only when it is not in the parameter-rich list.
11
12	### Parameter-rich tools — read the doc first
13
14	For these tools default parameters are usually suboptimal; consult the server's `docs/<server>.md` before the first call in the session and adjust the parameters to the task:
15
16	- `1c-graph-metadata-mcp`: `search_code` (`search_type`, `detail_level`), `search_metadata` (JSON templates), `search_metadata_by_description` (`alpha`, `use_fuzzy`), `trace_impact` (`direction`, `depth`, `relationship_types`), `trace_call_chain` (`direction`, `depth`), `get_object_dossier` (`sections`), `business_search` (`include_structure`, `filter_type`).
17	- `1c-code-metadata-mcp`: `metadatasearch` (`object_type`, `names_only`), `get_method_call_hierarchy` (`direction`, `depth`), `graph_dependencies` (`direction`), `bsl_scope_members` (`member_type`).
18
19	If `docs/<server>.md` conflicts with the descriptor exposed by the current environment, the environment descriptor wins.
20
21	## When to use this skill
22
23	- Before writing code / a query / metadata XML — pick the MCP tool that best fits the task (template search, metadata check, syntax validation, code review).
24	- For impact analysis and code navigation — decide which server to use first (`graph` → `code-metadata` → `Grep` — see Fallback chain below).
25	- For ITS standards (`its_help` → `fetch_its`) and platform documentation (`docinfo` / `docsearch`).
26	- For code templates and project memory (`templatesearch`, `remember`, `recall`).
27
28	> Short obligation rules and verification budgets live in `AGENTS.md → MCP Tool Calling` (sections A, B, C). This skill owns the MCP catalog, routing, and fallback details.
29
30	## Server catalog
31
32	\| Server (id) \| Purpose \| Details \|
33	\|---\|---\|---\|
34	\| 1c-graph-metadata-mcp \| Graph metadata (Neo4j / Cypher): structural object passport, impact analysis, call graph, usage search, business semantic search \| [`docs/1c-graph-metadata-mcp.md`](docs/1c-graph-metadata-mcp.md) \|
35	\| 1c-code-metadata-mcp \| Metadata and BSL code search, navigation (modules, procedures, functions, call hierarchy), forms, XSD schemas, validation \| [`docs/1c-code-metadata-mcp.md`](docs/1c-code-metadata-mcp.md) \|
36	\| 1c-templates-mcp \| Code template library + project vector memory (`remember` / `recall`) \| [`docs/1c-templates-mcp.md`](docs/1c-templates-mcp.md) \|
37	\| 1c-ssl-mcp \| Standard Subsystems Library (БСП / SSL) search \| [`docs/1c-ssl-mcp.md`](docs/1c-ssl-mcp.md) \|
38	\| 1C-docs-mcp \| 1C platform documentation (search by description / by exact name) \| [`docs/1C-docs-mcp.md`](docs/1C-docs-mcp.md) \|
39	\| 1c-code-check-mcp \| 1С:Напарник — code review, technical check, AI rewrite/modify, ITS documentation \| [`docs/1c-code-check-mcp.md`](docs/1c-code-check-mcp.md) \|
40	\| 1c-syntax-checker-mcp \| BSL syntax and style via BSL Language Server: `syntaxcheck` (code as text) and

People who liked this also viewed

6 picks

Type