The integration surface

Cirvix attaches at protocols rather than products wherever it can. Anything speaking a supported protocol is governed without a dedicated adapter — which is why this list is shorter than you might expect, and covers more than it looks like it does.

Status is stated per row. The product is in private beta and nothing here is marked generally available, because nothing here is. An integration matrix that quietly implies otherwise is the first thing an evaluator checks and the fastest way to lose them.

Coding agents

Registered as an MCP server plus a wrapping proxy. Your workflow does not change.

Integration	Mechanism	Effort	Status
Claude Code	MCP server entry in ~/.claude/settings.json	Config only	Private beta
Cursor	MCP config rewrite; existing servers routed via gateway	Config only	Private beta
Windsurf	Editor MCP config	Config only	In development
Cline	Editor MCP config	Config only	In development
GitHub Copilot agents	Egress proxy + MCP where exposed	Config only	Planned

Frameworks

SDK middleware on the tool-executor boundary. One import; no per-tool changes.

Integration	Mechanism	Effort	Status
LangChain	guard.wrap() on the tool array	One import	Private beta
LangGraph	guard.wrap() on node tools	One import	Private beta
CrewAI	Tool wrapper at crew construction	One import	Private beta
OpenAI Agents SDK	Tool-call interceptor on the client	One import	In development
Vercel AI SDK	Tool middleware	One import	In development
Anthropic SDK (raw tool use)	Interceptor on the messages client	One import	Private beta
Custom / in-house	guard.wrap() at whatever your executor boundary is	One import	Private beta

Protocols

Protocol-level interception, so a new framework on a known protocol is governed on day one.

Integration	Mechanism	Effort	Status
Model Context Protocol (MCP)	Full gateway — registry, pinning, tool scoping	No code changes	Private beta
Anthropic tool use	Request/response interception	No code changes	Private beta
OpenAI function calling	Request/response interception	No code changes	Private beta
A2A (agent-to-agent)	Delegation gateway with scope reduction	No code changes	In development

Deployment targets

Where the control plane runs in production.

Integration	Mechanism	Effort	Status
Docker	Sidecar container + egress proxy	Config only	Private beta
Kubernetes	Helm chart; sidecar or DaemonSet with optional LSM mode	Config only	In development
Terraform	Provider for policies, agents, and identities	Config only	In development
AWS Lambda	Layer + egress proxy	Config only	Planned
CI runners	cirvix/scan action with SARIF; policy gate on pull requests	No code changes	Private beta

Destinations

Where decisions and evidence go.

Integration	Mechanism	Effort	Status
Slack	Approval requests and alerts	Config only	Private beta
Microsoft Teams	Approval requests and alerts	Config only	In development
OpenTelemetry (OTLP)	Traces to any OTLP collector	Config only	Private beta
Splunk / Sentinel / Chronicle	CEF or JSON audit stream	Config only	In development
HashiCorp Vault	Secret handle resolution	Config only	Private beta
AWS / Azure / GCP secret managers	Secret handle resolution	Config only	Private beta
Okta / Entra ID	OIDC for approvers, groups, and roles	Config only	In development

Integrations

Not seeing yours?

If it speaks MCP, OpenAI function calling, or Anthropic tool use, it is already governed. If it does not, tell us what you run.

Start Book an enterprise demo Read the docs

Cirvix AgentControl is in private beta. Pricing is published and plans are not yet chargeable — early access confirms your place and we will tell you before anything bills.