Poliogo

MCP setup, CLI commands, config files and API reference

Everything the tools accept and return: the MCP server and its six tools, the CLI subcommands, the .poliogo config and snapshot files, and the embed and hosted-document APIs.

MCP · CLI · APICopy-paste examplesKept current with releases

What's documented

Reference material — for the step-by-step version, see the Setup Guides.

01

MCP server

npx poliogo-mcp init, editor registration for Cursor, Claude Code and Windsurf, and the six tools: scan_stack, generate_docs, install_pages, check_compliance, explain_clause, inject_rules.

02

CLI commands

Every MCP tool as a subcommand — scan, generate, install, check, explain, rules — so CI and a terminal reach the same code path an editor does.

03

Config files

The .poliogo/snapshot.json drift baseline, the fenced compliance block in CLAUDE.md / AGENTS.md / .cursorrules, and what regeneration does and doesn't touch.

04

Embed & document APIs

The banner embed snippet, the hosted document endpoints, and how published versions propagate to every embedded instance.

05

Connections & permissions

What each connector reads — repo trees, project lists, env var names — what it never reads, and how tokens are held.

06

Webhooks & drift

How pushes trigger rescans, when a PR is opened, and how scan frequency maps to plans: manual on Free, weekly on Starter, daily on Pro Builder, real-time on Agency.

Set it up in your editor

npx poliogo-mcp init — included from the Starter plan.

Start free — no credit card

Poliogo is a compliance management technology platform, not a law firm. Content provided does not constitute legal advice.