documentation
Muster documentation
Muster runs autonomous security agents against your apps, proves what's actually exploitable, and hands you the fix. These docs cover everything from your first scan to the REST API and MCP server.
How Muster works
You connect an asset (a repo, a web app, or a cloud account) to an organization. Muster maps its attack surface and continuously attacks it the way a real attacker would, across several engines. Confirmed, exploitable issues land as findings with the agent's assessment and a one-line fix. Re-scan on a schedule or from CI, and any fixed issue that later returns comes back flagged as regressed — so nothing silently reappears.
Core concepts
- Organization — a tenant/account. It owns its assets, findings, team, and billing. You can belong to several and switch between them from the header.
- Asset — a thing under protection: a connected repo, a web app/service, or a cloud account. You're billed per asset.
- Finding — a proven, exploitable issue with severity, the exact request, an AI read on impact, and the fix.
- Roles — per organization: owner, admin, member, viewer.
Where to start
New here? Follow Getting started. Building an integration? Jump to the API reference or MCP server.