Agent integration

Your agents work inside your rules.

Connect Clavero to Claude via MCP. Every session loads your investment areas, guiding principles, and recent decisions. Before the agent implements anything non-trivial, it checks the proposal against your compliance rules. Violations are caught before code is written — not after.

Claude · Clavero MCP connected

Engineer: Build a feature that auto-completes onboarding for returning users.

Claude:Let me check this against your team’s product principles.

⛔ This conflicts with a hard boundary:

“Never complete setup on behalf of the user.”

The concern is that auto-completion removes user agency, which is core to activation quality.

Alternative: pre-fill setup from their previous session but require one click to confirm. Same speed benefit, maintains agency. Want me to go that direction instead?

One command, full direction

Install the MCP server and every Claude session gets your investment areas, guiding principles, beliefs, and decisions as context. The agent doesn’t just build — it builds within the space you’ve defined.

$ claude mcp add clavero

Connected. 3 areas · 12 principles loaded.

Compliance, not just context

The agent has a clavero_check_compliance tool. Before implementing anything non-trivial, it runs the proposal through your rules. Hard violations come back with the reasoning and a suggested alternative. The first line of the wrong feature is never written.

Claude doesn’t ask forgiveness. It proposes the alternative, explains why, and lets you choose. The loop runs before the cost of being wrong starts accruing.

Per-user isolation, enforced by the server

The hosted server at mcp.clavero.aiauthenticates each user’s workspace via OAuth. Every tool call carries a per-user bearer token; the server verifies it on every request and scopes data to the caller’s workspace.

No shared service keys. No workspace bleed. A principle you wrote for your team is visible to your team — and nobody else’s Claude session can read it, check against it, or log a decision into it.

Works everywhere Claude does

Claude Code, claude.ai, Claude Desktop, Claude mobile. The stdio server is published as @clavero/mcp-server on npm for local-first setups; the hosted server handles web and mobile. Same tools, same rules, same reasoning surface.

Connect Claude to Clavero →

No credit card required · 14-day Pro trial