tiny1C
A Claude Code plugin with an MCP server of 1C development rules, where every rule names its source bug and how it is checked
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- The server only serves rule and glossary text, and does not touch the configuration or database
- Runs locally over stdio with no network
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/tiny1cDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
Run one by one in the Claude Code chat
/plugin marketplace add bigsofter/tiny1c
/plugin install 1c@tinycioInstall the plugin: claude plugin marketplace add bigsofter/tiny1C, then claude plugin install 1c@tinycio. Update it with claude plugin update 1c.
Other ways from the author
claude plugin marketplace add bigsofter/tiny1C
claude plugin install 1c@tinycioA Claude Code plugin; the rule set ships with it, updated via claude plugin update 1c.
This is third-party code. Review the repository files before installing.
What it does
tiny1C collects 1C:Enterprise development rules by track: a common platform core, plus separate tracks for the UNF, Accounting, Payroll and ERP configurations. Every rule states its source, a real bug or measurement on a live project with a date, and a check that fails if the rule is broken. Rules and terms live in per-track markdown files, and a machine-readable manifest.json index is built by a script. The mcp/server.py MCP server runs over stdio with no external dependencies and exposes tools to look up a rule by symptom, get its full text, list a category's rules, look up a metadata object, get a pre-edit checklist, and look up a glossary term.
Who it is for. For 1C developers who want an agent to rely on checkable rules from real bugs rather than generic advice.
Good fit when
- You want a set of 1C development rules with an explicit source and check for each one
- You work with UNF, Accounting, Payroll or ERP configurations and want a ready pre-edit checklist
- You need a dependency-free MCP server that runs as a stdio process on any machine
Not a fit when
- You need rules for a configuration the project does not cover yet: the bp, zup and erp tracks exist but are partly empty
- You need actual build code or scripts, not a set of development rules
Example request
Before editing this form, run the tiny1C .form checklist and show which core rules might be brokenLimitations
The bp, zup and erp tracks exist but currently have few or no rules; the authors are explicit that they do not invent rules without their own project on that configuration. Of 36 rules, about 19 are checked manually by a person only, since the manual check kind has no automated equivalent. It requires Python 3.8 or newer; no network or hosting is needed.
How to disable. Remove the plugin with claude plugin uninstall 1c@tinycio, or delete the tiny1c server entry from .mcp.json if you added it manually.
Security check
- The server only serves rule and glossary text, and does not touch the configuration or database
- Runs locally over stdio with no network
README in short
The README explains the project's core difference: every rule has its own source and its own check, with no rules that are just generally good to know. It gives a table of tracks with rule and term counts, three connection methods (a Claude Code plugin, a git clone with a path in mcp.json, other MCP clients via INSTALL.md), a table of server tools, a YAML rule format with source and check fields, and a section on adding your own rule via scripts/new-rule.py.
FAQ
Does the server need hosting or internet access?
No, it runs over stdio as a regular local process with no external dependencies or network.
What if rules for my configuration are not written yet?
The track will exist but stay empty: the project does not invent rules without a real bug from its own project on that configuration.
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