Skip to main content
Inviolet integrates with Claude in three places: the Anthropic SDK (server-side agents), Claude Desktop (employee assistants), and Claude for Work via the Model Context Protocol (MCP) endpoint Inviolet hosts. Same grant issuance across all three.

Why it matters

Claude tool calls are the dominant traffic shape for most early adopters. Wrapping the Anthropic SDK takes one line and gives you intent extraction + audit log + (optionally) policy enforcement on every messages.create call.

1. Wrap the Anthropic SDK (server-side)

This uses the evaluate path (intent.evaluate) — a lightweight pre-call check. For structural, credential-brokered enforcement where the agent never holds the real credential, mint a mandate and guard the call with @inviolet/agent-sdk-core — see the Quickstart.

2. Claude Desktop via MCP

Claude Desktop speaks MCP. Inviolet hosts an MCP server at https://gateway.inviolet.ai/mcp exposing read-only tools (intentions.list, approvals.list, intent.evaluate). Add this to Claude Desktop’s claude_desktop_config.json:

3. Verify

Open the decision feed at app.inviolet.ai/decision-feed. Make a tool call from the Anthropic SDK or ask Claude Desktop a question that uses the MCP tool. The event appears within seconds with the matched intention, the intent class, and the issued (or withheld) grant.