Settings

Configure your organisation, access control, policies, and workflow templates.

Agent Frameworks

SDKs and instrumentation methods available for connecting agents to Prefactor.

LangChainConfigured

prefactor-langchain v0.4.2

Auto-detection enabled — chains, tools, and callbacks captured automatically.

5 agents· GA-001, UA-001, UA-002, GA-003, UA-004

API (Direct)Configured

prefactor-python v0.3.1

Supported providers: OpenAI, Anthropic, Google, Azure OpenAI.

2 agents· GA-002, UA-003

Custom FrameworkAvailable

prefactor-python v0.3.1

Manual instrumentation via pf.log_event().

0 agents

Connected MCP servers that agents call at runtime. Prefactor's proxy captures all traffic automatically.

Server	URL	Status	Agents
Slack-MCP	mcp.slack.acme.com	Active	GA-001, UA-001
Canva-MCP	mcp.canva.acme.com	Unsanctioned	GA-001, UA-001, UA-002
GitHub-MCP	mcp.github.acme.com	Active	GA-002
Finance-MCP	mcp.finance.acme.com	Active	GA-003, UA-004
Notion-MCP	mcp.notion.acme.com	Active	UA-004

Non-MCP integrations: alerting, CI/CD, ticketing, and identity providers.

GitHubConnected

Gate Reports (commits, PRs, deployments)

Repos: acme/claims-processor, acme/chatgpt-copilot, acme/langchain-bot, acme/finance-bot

Auth: GitHub App (org-level)

SlackConnected

Workflow notifications, risk alerts, sign-off requests

Channels: #prefactor-alerts, #ai-governance

Auth: Bot token

JiraNot connected

Auto-create tickets from risk findings, link workflows to issues

PagerDutyNot connected

Escalation routing, on-call assignment for agent incidents

Azure AD / OktaNot connected

Single sign-on, user provisioning (SCIM)