Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.zenable.io/llms.txt

Use this file to discover all available pages before exploring further.

​
Quick Install

zenable install opencode
See the CLI command reference for more options.
That’s it! You’re all set. Start using Zenable’s conformance checking in OpenCode. This installs both the MCP server (in opencode.json) and a managed plugin (in your OpenCode plugin/ directory) that runs Zenable’s conformance checks throughout your coding session.
The below is a minimal example. Consider using the quick install command to handle this automatically.
OpenCode stores MCP servers under the top-level mcp key with "type": "remote" for streamable-HTTP servers. See OpenCode’s MCP docs for the full schema.

​
Global

Place the following in ~/.config/opencode/opencode.json:
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "zenable": {
      "type": "remote",
      "url": "https://mcp.zenable.app/"
    }
  }
}

​
Project

Place the same configuration in opencode.json at your repository root.
We only recommend this manual approach if you can’t use zenable install. Otherwise, zenable install is much safer and can handle configuration upgrades over time, handles merges with existing configs, performs backups and logging in case of issues, and more.
OpenCode’s documented extensibility surface is the plugin system. zenable install opencode writes a managed plugin file (at ~/.config/opencode/plugin/zenable.ts for global installs or .opencode/plugin/zenable.ts for project installs) that integrates Zenable’s governance, guardrails, and observability across your coding sessions.The plugin file is fully managed — every zenable install / zenable sync rewrites it. If you want to add your own OpenCode plugins, drop a separate file alongside it; OpenCode loads every *.ts / *.js under the plugin directory.