Loadoutz loadoutz docs
Use Cases
Product
Guides
References

Overview

Connect many tools and plug-ins once. Keep one clean connection for every agent.

New here?

Start with the MCP overview, then follow the product path from Catalog to connection.

1) What is MCP? 2) Quickstart 3) Agent setup

What is MCP? -> Agent setup ->

Loadoutz is the control plane for multi-tool agent work. Install and authenticate providers once, bundle the right tools into focused loadouts, then let one stable connection follow your agent across clients without repeating setup.

At 3 tools

Raw MCP config still feels manageable.

At 15 tools

Context and config start repeating across clients.

At 25+ tools

Manual setup turns into tool sprawl and context churn.

Core model

  • Catalog is the install gate. A provider should only reach Library after auth and verification succeed.
  • Library is your ready surface: installed providers, discovered tools, and saved credentials.
  • Loadouts keep the exposed tool surface small so agents do not carry your entire stack into every run.
  • Connections give clients one stable MCP endpoint while Loadoutz handles auth, routing, and runtime policy.

Why agents use this

  • One connection can sit in front of many tools and plug-ins.
  • Focused loadouts reduce prompt/context clutter for the agent.
  • Code mode can compose multiple tool calls in one run when a task needs orchestration.
  • Provider credentials stay server-side; the client only authenticates to Loadoutz.

What gets saved vs exported

Saved in Loadoutz

Workspace configuration, provider auth state, discovered tools, loadouts, and policy scope.

Exported to Client

Only the connection URL and client-side OAuth/session state for the current agent.

Runtime control

Explicit tool exposure, runtime revocation, and multi-tool orchestration policy.

Client compatibility

Loadoutz sits above the editor layer. Use the same managed connection model in Codex, VS Code, OpenCode, OpenClaw, Cursor, Claude Code, and local OSS workflows.

Recommended docs path

  1. 1. Read Quickstart for the product flow.
  2. 2. Read Concepts for Catalog, Library, Loadout, and Connection.
  3. 3. Use Agent setup when connecting a real client.
  4. 4. Use Troubleshooting when provider or runtime state is unclear.

Need help next?

Quickstart Agent setup Troubleshooting Resources