Build tool-calling agents in a visual studio, run them against your MCP servers, and decide what every tool call may do: policies, approvals, signed audit bundles and a release gate. It all runs on your own infrastructure.
Runs in your browser, no sign-up. Recorded runs; nothing leaves your browser.
See it running
The real studio, with recorded runs.
The demo is the L2M studio itself, built against recorded runs. Open it and click around: nothing is faked by hand, and no model, server or tracker is called.
One MCP registry for every server your agents call, and an MCP gateway that serves their tools to outside clients. L2M probes each server, tracks its tools and what they cost, and enforces who may call what, for agents and clients alike.
Registry and onboarding. Health probes, tool schema snapshots with breaking-change diffs, a playground, and import from MCP client config files.
Telemetry and policy. Calls, p95 latency, errors, tokens and cost per tool. Allow and deny rules by project, role, server and tool, plus a "no write tools" switch.
Gateway. Serve workflows and registered tools to other MCP clients, with per-client tokens and the same policies.
Credentials. OAuth 2.1 for remote servers, or each user's own delegated account.
Testing. Record MCP calls into cassettes and replay them; l2m mcp check fails CI on breaking changes or blocked tools.
Runtime safety. Stdio servers in sandboxed containers, rate limits, concurrency caps and a circuit breaker.
Pause a run on a person. Approval gates, human approvals, write tools an agent wants to call and versions waiting to be published all land in one Approvals inbox.
Every finished run gets a manifest of models, tool calls, prompts and approvals. Export it as an Ed25519-signed bundle with secrets scrubbed, and check it offline with l2m audit verify.
Label where each step's data came from and what it contains. Sort every model, server and URL into local, private, approved-vendor or public, and block, redact or ask for approval when sensitive data would go too far.
Approvals: decide paused runs, and edit fields before approving.
Ship safely
CI for agents.
Treat a prompt or tool change like a code change: replay it against known-good runs before it reaches production.
Golden runs and sets. Save good runs, group them, and replay a draft or a saved version against them.
Scorers. JSON equality and schema, text similarity, tool sequence, status, budget and an LLM judge.
Release gate on publish. A version reaches production only after its replay job passes the gate's policy; an override needs a written reason and is audited.
Production capture. Sample real runs with personal data masked, and promote the useful ones into a golden set.
A CLI for your pipeline. Run replays, write JUnit results and publish from CI.
ci.sh
# replay the draft against a golden set; non-zero exit when it failsl2m replay run --set faq-golden --draft --junit replay.xml
# publish a version through the release gatel2m release publish wf-faq --version 4
A release gate blocking v4: 0 of 3 golden cases passed.
Self-hosted foundations
Yours to run. Nothing hosted by us.
L2M is an open-source agent runtime (MIT) that runs only on your infrastructure. There is no hosted edition and no call-home: the product sends no analytics anywhere.
Session sign-in, API keys, TOTP MFA, and SSO through SAML or LDAP (optional packages). Admin, builder, operator and viewer roles, projects and custom roles.
AES-256-GCM at rest, master-key rotation through export and import, and external managers: HashiCorp Vault built in; AWS, Google Cloud and Azure with their SDK installed. Configs carry secret references, never values.
Bearer or HMAC-SHA256 with a replay window and optional idempotency keys, plus signature checks for Stripe, GitHub, Slack, Telegram and Discord triggers.
SQLite by default; Postgres support in progress. Docker images for amd64 and arm64, Docker Compose and a Helm chart.
Everything is optional. A simple workflow runs with no extra configuration. Approvals, release gates, data labels and destinations, production capture and sandboxing stay off until you turn them on.
Get running
From clone to a working MCP agent.
No model key is needed to start: the MCP Agent Quickstart template uses the built-in echo model and an in-process mock MCP server. Swap in real models and servers when you're ready.