Skills and engine

The router and 12 specialists

mcwrench is one always-on hub plus eleven focused specialists. You never name the specialist. The minecraft-server-router skill engages on any server-admin topic and hands off to the right one based on what you describe. Each skill is gamemode-agnostic and plugin-agnostic, and defers exact config keys to the docs-learner rather than guessing.

The docs-learner

When mcwrench is not confidently current about a plugin's config keys, permission nodes, or commands, it runs learn-plugin-docs first and answers from the fetched reference instead of guessing. The learner routes each plugin to the cheapest authoritative source, condenses the result, and caches it.

Source routing

The host of a URL (or the result of a name search) selects an adapter. The aim is the cheapest channel that returns clean markdown. The learner also probes /llms.txt and /llms-full.txt for docs sites.

Resolution and output

A bare URL maps straight to its host adapter. A bare name searches Modrinth, then Hangar. An owner/repo shorthand goes to the GitHub README adapter. The fetched markdown is condensed into a structured reference and written to the cache:

• ▸skills/_cache/<slug>/REFERENCE.md holds the condensed reference (with source_url and fetched_at).
• ▸skills/_cache/<slug>/RAW.md holds the full fetched markdown.
• ▸The _cache/ tree is git-ignored. Re-running within the TTL reuses the cache and skips the network.

Library and durability

64 popular plugins ship pre-fetched in the committed skills/learn-plugin-docs/library/ directory, alongside a name and alias registry.json. Common lookups (LuckPerms, EssentialsX, ViaVersion, WorldGuard, and the rest) resolve with zero network.

Resolution order

• ▸Library first. A registry name or a matching <slug>.md file in library/ is served immediately, no fetch.
• ▸Then the local _cache/ if a fresh REFERENCE.md exists.
• ▸Then the registry URL for a known name (fetching the canonical docs URL, not a bare-name search, which avoids picking the wrong project).
• ▸Then a Modrinth then Hangar search for anything unknown.

Flags and durability

Conflict and profile checks

Two read-only helpers keep an installed plugin set sane and let later answers stop re-asking the basics.

check-conflicts.mjs

Reads the plugin set (from <root>/plugins/*.jar, an explicit --list, or the server profile via --profile) and flags well-established overlaps and gaps:

• ▸Mutually exclusive plugins, such as two skyblock engines, two claim systems, or ItemsAdder alongside Oraxen.
• ▸Missing dependencies, such as Vault without an economy plugin, or LibsDisguises without ProtocolLib.
• ▸Proxy and Folia mismatches between the software and the network setup.

It is conservative by design and only reports established overlaps and deps. Verify with learn-plugin-docs before removing anything.

scan-server-tree.mjs --write-profile

Manifests a server tree and, with --write-profile, saves the server profile to skills/_cache/server-profile.json (software, version, host, RAM, gamemode, proxy, online-mode, plugins, worlds, chat formatter). Every skill reads it first and tailors answers to known facts.

Script reference

The helper scripts run on stock Node 18 or newer, with no install for the common paths. In Claude Code and Antigravity, ${CLAUDE_PLUGIN_ROOT} resolves to the plugin root; from a clone, paths are relative to the repo root.