Compliance checks inside your AI editor

Poliogo ships a first-party MCP server for Cursor, Claude Code and Windsurf. Your agent scans the workspace, generates documents, installs the pages and checks for drift — without you ever opening a dashboard.

Start free — no credit card See pricing

scan_stack

Fingerprint the open workspace

generate_docs

Write the documents into your repo

install_pages

Serve them as routes in your framework

check_compliance

Diff the workspace against your last snapshot

explain_clause

Why a clause exists, with file and line

inject_rules

Keep your agent's rule files current

Cursor

Claude Code

Windsurf

Connect it to your editor

One command, run once per project. It registers the server and its six tools with whichever editor you're in — no config files to hand-edit.

Cursor

$ npx poliogo-mcp init --editor cursor

Claude Code

$ npx poliogo-mcp init --editor claude-code

Windsurf

$ npx poliogo-mcp init --editor windsurf

What your agent can do with it

Ask "is my app compliant?" in your editor and get a gap report built from your actual code.

One command to install

For AI editors

npx poliogo-mcp init registers the server with Cursor, Claude Code or Windsurf. Every tool also has a CLI subcommand, so CI reaches the same code path an editor does.

Scans locally, sends only the fingerprint

Private

The server runs on your machine and reads the workspace there. What leaves is the extracted list of detected services — never your source code.

Documents written into your repo

generate_docs writes the files into legal/, and install_pages serves them as real routes in your framework and mounts the consent banner.

Drift checks on demand

check_compliance diffs the current workspace against your last approved snapshot and names exactly what changed — new service, new endpoint, new data field.

explain_clause, with receipts

Ask why a clause exists and get the plain-language reason, the detected service that put it there, and the file and line it was proved from.

Your agent stays informed

inject_rules maintains a fenced compliance block in CLAUDE.md, AGENTS.md and .cursorrules, so your own coding agent flags compliance-relevant changes as you build.

How it works

npx poliogo-mcp init

Registers the server in your editor. One command, once per project.

Ask your agent

"Check if my app is compliant" — the agent calls check_compliance and reports the gaps.

"Fix it"

generate_docs and install_pages write the documents and routes into your repo. You review the diff like any other change.

Put compliance in the build loop

MCP Server is included from the Starter plan.

Start free — no credit card

Poliogo is an automated code analysis and document display tool, not a law firm. Poliogo does not provide legal advice, representation, or guarantees of statutory compliance, ADA/WCAG certification, or legal immunity. Visual banners and generated documents are advisory tools and do not substitute for professional legal review.