Use Cases
Product
Guides
References
Concepts
Catalog, library, loadout, connection
Loadoutz uses a small set of objects that stay consistent across UI, runtime, and client setup.
Runtime flow map
Catalog -> Library -> Loadout -> Connection -> Agent
At runtime:
/mcp/u/:owner -> OAuth discovery -> initialize -> tools/list -> tools/callCatalog
Provider discovery and install authority.
- Catalog is where OAuth, API key, PAT, and public MCP installs begin.
- A provider should only reach Library after auth and verification succeed.
- There should be no fake “installed, finish auth later” happy path.
Library / Workspace
Your saved ready surface.
- Contains installed providers, discovered tools, saved credentials, and workspace policy.
- If a provider is visible here, it should already be basically usable.
- One workspace keeps one project/client/team context clean.
Loadout
A focused tool surface for a job.
- A loadout is an explicit allowlist of tools, not a fuzzy tag.
- It keeps the active tool surface small so the agent does not carry your whole stack into every run.
- If your use case needs orchestration, code mode can compose multiple tools from the active loadout in one run.
Connection
One stable MCP endpoint for one agent or client relationship.
- Canonical route:
/mcp/u/:owner. - The client authenticates to Loadoutz once and keeps using the same connection while tools behind it evolve.
- Switching loadouts updates exposed tools without rewriting client config.
ID prefixes
Loadoutz IDs are prefixed so you can identify object type quickly:
ws_workspacelo_loadoutsess_connection session id
Need help next?