BetaAvailable to invited Crit accounts.

Use Crit from your AI app.

Request audits and read findings in Claude Code, Codex or Cursor.

Connect your app.

Run this in your terminal to add Crit across your Claude Code projects.

Terminal
claude mcp add --transport http --scope user crit https://crit.keya.studio/api/mcp

Finish in your browser.

In Claude Code, run /mcp and choose Crit to authenticate. Sign in with your existing Crit account, review the permissions and connect.

Check the connection

Run claude mcp get crit to inspect the configuration. In Claude Code, /mcp shows the connection status.

Claude Code’s setup documentation

No extra package, API key or client secret needed.

Run an audit.

Share a public URL or a screenshot you approve sending to Crit, with this request:

Use Crit to review this website or screen. Ask me its discovery questions and give me the approval link before starting the full audit.

  1. Answer the discovery questions.

    Choose up to two options per question to explain the audience and what you want to learn.

  2. Review and approve in Crit.

    Open the approval link and check the URLs, files, context and answers before approving.

  3. Read the findings in your app.

    Audits can take several minutes. Ask for progress, then priorities, evidence and recommendations. Open the saved report for the complete audit.

Common questions.

Can Crit review localhost or a signed-in app?

The hosted server cannot open your localhost or inherit your browser session. Share approved screenshots of those screens instead. Do not send passwords or browser cookies.

What can I send?

Send up to 5 public URLs and 7 files: PNG, JPEG, WebP, PDF, Markdown or text. Inline files can total up to 3 MiB.

What if I run out of credits?

Open Crit to purchase more. The connection cannot make a purchase, and a full audit will not silently turn into a quick read. Saved results remain available at zero balance.

What if my app disconnects or times out?

Ask it to check the same audit id. An approved audit can continue in the background. Retrying with the same request key or reading the saved result does not start or charge another audit.

Who sees the material and findings?

Crit and its AI provider process the material you submit. Returned findings are visible to your connected app and may be processed by its provider. Connecting does not opt your audits into training or product-learning datasets.

How do I disconnect an app?

Open Connected apps in Crit and disconnect it. Connections also expire after 30 days. Disconnecting stops further access and new audit starts. An audit already running may still finish and use its credit.

Manage connected apps