Open-source AI agent control plane and software factory: govern every tool and model call.
io.github.preloop/preloop MCP Server
The io.github.preloop/preloop MCP server provides an open-source AI agent control plane and software factory focused on governing tool and model calls. Its purpose is described as coordinating how tools and models are used during agent execution through centralized control.
๐ ๏ธ Key Features
Open-source AI agent control plane
Software factory capability
Governs every tool and model call
๐ Use Cases
Coordinating AI agent executions by centralizing control of tool usage
Standardizing how model calls are governed within an agent workflow
โก Developer Benefits
Clear governance over tools and model calls for AI agents
โ ๏ธ Limitations
No additional implementation details, tooling, or constraints were provided in the available source data
The open-source AI agent control plane and software factory.
Preloop is one self-hostable service that sits between your AI agents and everything they reach, and runs agents for you when work arrives. Every tool call and every model call is governed, attributed and visible, whether a person started the agent or a ticket did. You see gateway spend by model, agent, session, API key and flow, and cap it with budgets. Imported Copilot usage is displayed separately as vendor-reported data.
It has two halves, and the same policies, budgets and session timeline apply to both:
Control plane. An MCP firewall that allows, denies or holds any tool call for human approval; an AI model gateway with budgets and attribution; policy-as-code in YAML and CEL; one runtime timeline per session.
Software factory. Flows run agents, in hosted containers or on your own runners, when GitHub, GitLab, Bitbucket Cloud, Jira, a webhook or a CI job fires. Presets review pull requests, implement issues, triage tickets, scan for vulnerabilities and collect evidence packs. A human can steer a running agent from the console, phone or watch, and the work lands as pull requests you can review.
Both halves are multi-user: invite colleagues and organize teams in Preloop (OSS). Each user can connect devices, runners and agents. Preloop (OSS) has no roles or access controls between users of an account; those are in Preloop Cloud and Preloop Enterprise.
Who it is for:
Platform and security teams that need agents governed before they reach production systems.
Engineering teams running coding agents that want to see the cost and keep an audit trail.
Teams that want tickets and events turned into bounded agent work they can review.
MCP clients connect to /mcp. See the tested MCP protocol matrix for modern discovery, legacy initialization, and SDK migration details.
Works with Claude Code, Codex CLI, OpenCode, Pi, Deepseek Harness, Hermes, OpenClaw, Cursor, Gemini CLI, Devin, Copilot CLI, and any MCP-compatible agent.
Your first five minutes
bash
# 1. Install the CLI (macOS / Linux / WSL)
curl -fsSL https://preloop.ai/install/cli | sh
# Windows, native (PowerShell): irm https://preloop.ai/install/cli.ps1 | iex# Details: docs/windows-cli.md# 2. Connect it to a control plane
preloop signup # Preloop Cloud (fastest), or
preloop login --url http://localhost:3000 # your self-hosted instance# 3. Bring local agents under governance
preloop agents discover
preloop agents discover finds local agent configs and reports what each adapter supports. preloop agents onboard configures them: calls routed through the managed MCP entry reach the MCP Firewall, supported model routes use the Gateway. To talk to a running agent, install the runtime plugin with preloop agents install-plugin (or preloop claude for Claude Code). Full walkthrough: onboard local agents.
Watch it work
Onboarding, the MCP firewall, human approvals, and cutting session cost. Recorded against a real stack, no slideware.
One loop, end to end: an issue event arrives from GitHub, GitLab, Bitbucket Cloud or Jira. A flow starts an agent in a hosted container or on your own runner. Every tool call it makes passes the same firewall and approvals as your own agents, and every model call is charged to the flow's budget. The agent opens a pull request; the Pull Request Reviewer reviews it; review or CI feedback resumes the implementation on the same branch, and the result is a pull request you can review. You can steer the run with an operator note at any point, and the whole run is one timeline.
Delivery Report: a weekly report with proposals for human decisions and project reruns. See what landed, what the available evidence supports against stated criteria, and which gaps deserve investigation
Security audit presets: SBOM verify, exploit check, release audit. They collect machine evidence for CRA- and EU AI Act-style reviews. That is not a conformity assessment, certification, or legal advice.
Check a sample call before saving with Test this rule or Simulate in the console. Ship it with preloop policy apply <file> (validate / diff / export also exist).
Restricted CI identity: a machine identity bound to one project and one flow for CI jobs, with an optional read-only native GitHub App clone mode and separate result publication. Guide.
Account kill switch: blocks gateway and tool traffic and stops managed flow runs, with audited recovery. Guide.
Durable audit delivery: opt-in transactional intents for approvals, policy decisions and tool outcomes, with restart replay and backlog alerts. Operations guide.
Session search: keyword search by default, semantic as an opt-in, every search audited. Saved searches.
DORA exports: the AI-agent slice of the ICT inventory and incident record. Guide.
OTLP export: off by default; emits OpenTelemetry GenAI spans. Guide.
Chat: Slack, Mattermost, and Discord for questions, approval votes and operator notes. Chat connections.
Event-driven employees: managed agents doing bounded tasks from tracker and error events. Guide.
The CLI is a client. It talks to a control plane: Preloop Cloud or a stack you run.
Cloud (fastest)
bash
curl -fsSL https://preloop.ai/install/cli | sh
preloop signup
preloop agents discover
Self-host (Docker Compose, data stays on your machine)
bash
curl -fsSL https://preloop.ai/install/oss | sh
curl -fsSL https://preloop.ai/install/cli | sh
preloop login --url http://localhost:3000
preloop agents discover
Console: http://localhost:3000. CLI login commands: CLI authentication. TLS, SMTP, upgrades and Kubernetes: Install the OSS stack, Helm chart helm/preloop, compatibility policy. Docker Compose and Helm are the supported install surfaces; this repository does not ship Terraform modules. The local upgrade acceptance harness verifies release-to-candidate migrations, data and credentials in disposable Compose and kind stacks.
Credential storage upgrades keep the existing encryption key and run as a normal rolling upgrade; read the credential storage upgrade guide before upgrading an existing installation.
Production self-host: SECRET_KEY is required or the app refuses to start, and the Helm chart refuses to install while environment.jwtSecret is empty or a placeholder (see helm/preloop/README.md). The development docker-compose.yml ships development-only credential defaults; override them with a .env file (start from .env.example). Telemetry is a daily pseudonymous version check-in; set PRELOOP_DISABLE_TELEMETRY=true to disable. Event list: SECURITY.md.
Open-source alternative to AWS Bedrock AgentCore
Same core jobs (runtime, gateway, identity, observability, policy), vendor-neutral and self-hostable. Full comparison: preloop.ai/vs/aws-agentcore.
Preloop
AWS Bedrock AgentCore
Open source (Apache 2.0)
Yes
No
Self-hostable (VPC / on-prem)
Yes
No
Policy-as-code (YAML + CEL)
Yes
Limited
MCP-native tool governance
Yes
Partial
Human approvals (mobile, Slack, webhook)
Yes
Limited
Onboard existing local agents (preloop agents discover)
Unqualified Preloop is this repository (Apache 2.0, self-hosted). Preloop Cloud is the hosted service at preloop.ai. Preloop Enterprise is the commercial self-hosted edition. Cloud and Enterprise include support plans. Cloud billing owners can compare usage from the previous three completed months in Account settings before requesting a plan-change quote.
Your data: self-hosted, nothing leaves your network except the optional daily version check. On Preloop Cloud, sessions are stored only to give you search, audit trails, cost reports and policy enforcement; they are not used to train models and are not sold or shared. Details: Security & Privacy.
Governance itself is open source: every model provider, flows, private runners, session search, operator notes, the audit trail, single-approver workflows and budgets scoped to the account, a flow, an API key or a managed agent. What is commercial is the organizational layer on top:
Feature
Preloop (OSS)
Preloop Cloud / Preloop Enterprise
Audit collection, query API, and console
Yes
Yes
Audit hash chain and verification, retention, legal holds, signed exports (Settings > Records)
Yes
Yes
Multiple users, invitations, teams and team membership
Yes
Yes
Membership offboarding with personal credential revocation and retained account automation
Yes
Yes
Per-user devices, runners and agents; basic approvals and usage views
Yes
Yes
Isolation between accounts
Yes
Yes
Roles, owner protection, RBAC/ABAC, resource access rules and sharing
No
Yes
Subaccounts, pooled billing, fleet findings
No
Yes
Authenticator-app two-factor sign-in, recovery codes and passkeys
Yes
Yes
Single sign-on (OIDC, SAML), verified domains, IdP group mapping, SSO enforcement with owner break-glass
No
Yes
Governance reviews, advanced reporting
No
Yes
Budgets scoped to a user or a team, budget notification routing
No
Yes
Multi-approver routing, quorum, escalations
No
Yes
Preloop (OSS) supports multiple users on one account, with no access controls between them: every user of an account can do everything in that account, including inviting and removing colleagues and managing teams. Accounts stay isolated from each other. Public signup, if enabled, creates a separate account. All access control (roles, owner protection, RBAC/ABAC) is in Preloop Cloud and Preloop Enterprise.