Answer what only the running infobase knows — does a query parse, what it returns on real data, does a BSL fragment run, what the event log recorded — via the 1c-data-mcp service on the infobase. Read-only by default; any mutation needs explicit user consent.
Facts about 1C metadata objects — passport, typed attributes, tabular-part columns, forms, predefined items, objects by category or Russian description — from the graph and code-metadata MCP. Use before code or metadata that depends on an object's structure, and to find objects by synonym.
A reference guide for 1C platform syntax, built-in capabilities, reusable business libraries, project standards, file formats, and configuration documentation. 1C is a platform for building business applications.
Search reusable 1C code templates with the task text and adapt a fitting result. Use when the selected 1C workflow needs a template; memory-only work enters through project-memory.md.
A validation workflow for changed 1C files, including code modules and metadata descriptions. It checks code through language and logic tools, reviews style and platform rules, and checks metadata XML against its schema, which is a formal structure definition.
Sync delta specs from an OpenSpec change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change. Also use when the user says "openspec sync" or "opsx sync".
Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Also use when the user says "openspec update change" or "opsx update". If the user…
A handoff process for making changes to 1C systems through a human rather than directly editing source files. It uses a Configurator package or a reviewable difference, especially when the system is vendor-locked, binary, or available only through MCP.
Create, maintain and run reusable tests of 1C business logic using the project's verified framework or runner. Optional: the model chooses when persistent regression coverage adds value beyond a focused result check.
Create or maintain reusable UI regression tests for a 1C web client, runnable without an AI agent. Optional: choose when repeatable coverage is useful; ordinary interactive UI checks remain with 1c-tester.
UI checks in the 1C thin client through QA MCP (1c-qa, qa / ui): session, observe → act → assert, platform behaviour, unknown outcomes, journal and verdicts. Main UI route when connected and TOOLQA allows it; the web client is the fallback.
★not rated 489▲
+8
changed 10d agoA72 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: