Skip to main content

​
Quick Install

Requires Pi 0.99.0+. See the CLI command reference for more options.
That’s it! You’re all set. Start using Zenable’s conformance checking in Pi. This installs both the MCP server and a managed extension that runs automatic conformance checks. Use zenable install pi --project for a project installation. If sign-in was deferred, run pi mcp login zenable.
Existing users: rerun installation at the same scope to add native MCP support and replace Zenable’s old CLI guidance. Your rules and other MCP servers are preserved.
The below is a minimal example. Consider using the quick install command to handle this automatically.

​
Global

Merge the following into ~/.pi/agent/mcp.json. If PI_CODING_AGENT_DIR is set, use mcp.json in that directory instead.

​
Project

Place the same configuration in .pi/mcp.json at your repository root.Run pi mcp login zenable to authenticate. Pi uses Codemode by default; see Pi’s MCP documentation for other options.
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.
Pi’s extension API provides automatic checks alongside MCP. The managed extension lives at ~/.pi/agent/extensions/zenable.ts globally (honoring PI_CODING_AGENT_DIR), or .pi/extensions/zenable.ts for project installs.zenable install and zenable sync manage this file. Add your own extensions as separate files alongside it, and install Zenable’s extension at only one scope to avoid duplicate checks. For an MCP-only manual setup, add checks with zenable install hook pi (or --project).