Integrations

Connect Pavri where agents are built, run, and investigated.

The launch integration story is detail-first: each entry should state status, function, validation evidence, and limitations rather than relying on a logo wall.

Pavri integrates through framework paths (LangGraph / LangChain, CrewAI, OpenAI Agents SDK, Anthropic Claude Agent SDK, Google Agent Development Kit, Microsoft AutoGen / Agent Framework, Generic Adapter), coding-agent endpoint coverage across macOS, Windows, Linux, Local MCP Broker routes, and downstream security and response workflows.

Framework integration paths

Use the canonical seven integration-path names consistently.

This page is substantive and indexable because it includes named integration paths, functions, status language, and limitations.

LangGraph / LangChain

Function: identity, policy, telemetry, decision records, and session evidence through a framework-native path.

Status: available with release-specific requirements

CrewAI

Function: identity, policy, telemetry, decision records, and session evidence through a framework-native path.

Status: available with release-specific requirements

OpenAI Agents SDK

Function: identity, policy, telemetry, decision records, and session evidence through a framework-native path.

Status: available with release-specific requirements

Anthropic Claude Agent SDK

Function: identity, policy, telemetry, decision records, and session evidence through a framework-native path.

Status: available with release-specific requirements

Google Agent Development Kit

Function: identity, policy, telemetry, decision records, and session evidence through a framework-native path.

Status: available with release-specific requirements

Microsoft AutoGen / Agent Framework

Function: identity, policy, telemetry, decision records, and session evidence through a framework-native path.

Status: available with release-specific requirements

Generic Adapter

Function: identity, policy, telemetry, decision records, and session evidence through a framework-native path.

Status: available with release-specific requirements
Endpoint and response ecosystem

Coding assistants, MCP, identity, SIEM, response, and MDM connect to different parts of the workflow.

Assistant examples include Claude Code, Cursor, Windsurf, GitHub Copilot agent mode and VS Code agentic workflows, Gemini CLI, Aider, Claude Desktop, and JetBrains AI Assistant. Validation and limitations are maintained in coverage detail.

MCP

Inventory MCP servers and tools; route configured tool calls through Pavri's Local MCP Broker when enabled.

Approval only for broker-routed configured calls

SIEM and response

Send detection and decision context to downstream ticketing, notification, containment, and investigation workflows.

Security workflow integration

MDM and endpoint rollout

Enroll managed developer endpoints and deploy endpoint-sensor components according to OS-specific requirements.

macOS / Windows / Linux
Next step

Need a specific integration path?

Share the framework, assistant, MCP client, operating system, or response workflow you need validated.