Connect an AI client

Remote MCP endpoint

https://rulegap.cloud/mcp

Add this URL as a remote MCP server in an OAuth-capable client. The client discovers RuleGap’s protected-resource metadata, registers with the authorization server when supported, and opens a RuleGap consent screen. RuleGap never asks you to paste an access token into the client.

Authorization flow

1. Sign in to your existing RuleGap account.
2. Review the client name, return host, identity scopes, and RuleGap capabilities on the consent screen.
3. Authorize the connection. Access remains limited to workspaces your user can already access.
4. Revoke the client at any time from Workspace Settings.

Available capabilities

Read

List accessible workspaces and repositories; inspect exact-commit snapshots, Constitution rules, findings with evidence, scan status, coverage, comparisons, and proofs. Builder and higher plans include MCP read access.

Analyze

Estimate scans without a charge. Pro and higher plans can start a scan only after explicit confirmation of the Logic Credit charge and provider disclosure. Proof execution requires a supported plan and explicit isolated-execution authorization.

Review

Team and higher plans can record an explicitly confirmed rule or finding decision. Consequential calls require idempotency keys so a client retry cannot repeat the mutation.

Safety model

OAuth access tokens are short-lived, signed with an asymmetric key, bound to the RuleGap MCP audience, and marked for MCP use. Supabase row-level security enforces user membership. Plan capabilities are checked again for every tool call. GitHub, Stripe, model-provider, and Supabase service credentials are never returned to the client.

Troubleshooting

If authorization fails, remove the stale client connection and reconnect. If a plan-gated tool is unavailable, confirm the active workspace plan. A retried mutation may tell you to read the target resource first; this is an intentional guard against duplicate changes.