@sbl_yvwx/enfusion-mcp

A Bun-native MCP server for Arma Reforger and the Enfusion Workbench. It provides API/wiki search, bounded game archive access, addon scaffolding, validation, and explicit live Workbench control.

This fork intentionally supports only Bun 1.3.14 and the modern MCP 2026-07-28 protocol with server/discover. Legacy initialization is not supported.

Install

bunx @sbl_yvwx/enfusion-mcp

Codex (CLI, desktop app, and IDE extension):

codex mcp add enfusion-mcp -- bunx @sbl_yvwx/enfusion-mcp

Alternatively, add the server to ~/.codex/config.toml for user-wide access or .codex/config.toml in a trusted project:

[mcp_servers.enfusion-mcp]
command = "bunx"
args = ["@sbl_yvwx/enfusion-mcp"]

Restart Codex after editing the configuration, then use codex mcp list or /mcp to verify the connection. See the official Codex MCP documentation for additional configuration options.

Claude Code:

claude mcp add --scope user enfusion-mcp -- bunx @sbl_yvwx/enfusion-mcp

Claude Desktop configuration:

{
  "mcpServers": {
    "enfusion-mcp": {
      "command": "bunx",
      "args": ["@sbl_yvwx/enfusion-mcp"]
    }
  }
}

See installation and configuration for the complete setup.

Safe first use

Offline research and generation tools do not require Workbench. Live wb_* tools never start Workbench or install handlers implicitly.

1. Configure ENFUSION_PROJECT_PATH to the addon root you intend to use.
2. Run wb_diagnose before changing Workbench state.
3. Use wb_prepare without confirmation to preview handler installation, then confirm only with user authorization.
4. Use wb_launch without confirmation to inspect presence. A failed ping does not mean Workbench is stopped.
5. Confirm launch or play/stop transitions only when the user explicitly requests them.
6. Never automate a live script reload. Use wb_validate with action: "scripts", then apply validated script changes with manual Shift+R or a Workbench restart.
7. Run wb_cleanup before publishing an addon containing injected handlers.

Read the Workbench lifecycle guide before automating a live editor.

Capabilities

• Search Enfusion/Arma Reforger APIs, wiki material, and the bundled knowledge base.
• Browse and read bounded loose files and mixed-generation .pak archives.
• Scaffold scripts, prefabs, layouts, menus, scenarios, configs, and game modes.
• Validate and build contained addons.
• Inspect and mutate a connected Workbench through paired TypeScript/Enforce handlers.
• Create verified World Editor layers and place durable entities by stable layer path, with bounded layer/entity output for model context.
• Run a separately authenticated, loopback-only vehicle tuning UI.

The exact registered inventory is generated in the tool reference; it contains no hard-coded tool count.

Runtime and authentication

• Bun 1.3.14 is the only supported runtime/package manager.
• MCP stdio has no bearer-token exchange. Access is controlled by who can configure and start the local MCP process and its environment.
• The separate enfusion-tuner HTTP server is loopback-only, read-only by default, and requires its per-process bearer token for mutations after ENFUSION_TUNING_WRITE=1 is enabled.
• Every addon path is constrained beneath ENFUSION_PROJECT_PATH after realpath resolution.

See security and project workflow and environment reference.

Development

bun install --frozen-lockfile
bun run docs:check
bun run check
bun run typecheck
bun run build
bun test --isolate
bun run pack:check

Repository architecture and contributor invariants are in AGENTS.md. Fork lineage is documented in fork lineage.

Documentation

Start at the documentation index. Maintained guides/reference material are separated from dated design and implementation history.

License

MIT