Loadoutz loadoutz

Agent tooling infrastructure

Add more tools. Not more complexity.

One connection across your stack, with loadouts for control and code mode for multi-tool workflows.

Get started How it works

Mental model

Install MCPs → Build loadout → Connect once → Run with agent

AI tool usage is growing. Tool sprawl and context churn should not grow with it.

How it works

Four steps. Then you're done.

No more rebuilding config every time you switch clients, rotate keys, or add another provider to the stack.

01

Install from catalog

Pick from verified providers. OAuth or API key, provider credentials stay server-side, and a provider only lands in Library after auth and verification succeed.

02

Build a loadout

Bundle the exact tools each job needs. Research, build, ops, or a narrow workflow that should not drag the rest of your stack into every run.

03

Make a connection

Get one stable MCP connection. Your agent or client keeps that endpoint while you change what sits behind it.

mcp.json

{
  "mcpServers": {
    "loadoutz": {
      "url": "https://mcp.loadoutz.io/mcp/u/<owner-id>"
    }
  }
}

04

Run multi-tool work

Use direct tool calls when you know the exact tool, or code mode when the agent needs to combine multiple tools and plug-ins in one run.

code mode

> execute_code(...)
< news + docs + prices + search stitched in one run

The session layer

Your agent never needs
to know what changed.

Auth, routing, scoping, and multi-provider composition sit behind one stable connection, so operational changes do not spill into every client config or every agent prompt.

Multi-MCP by default

One connection can sit in front of tools discovered from many providers, so the agent works across a real stack instead of one plug-in at a time.

Credentials stay server-side

Your agent never needs direct provider tokens. Loadoutz stores the provider state and injects auth on proxied calls.

Code mode for real jobs

Use direct calls for simple work, then switch to code mode when the agent needs multi-step orchestration without bloating prompt context.

Scoped exposure per connection

Each connection sees only the tools and loadouts you explicitly allow, enforced in the session layer rather than by convention.

connection · mcp-gateway
https://mcp.loadoutz.io/mcp/u/<owner-id> copy

active loadout

research build deploy

tools

4 of 22 installed

scopes

mcp:tools mcp:resources selected loadouts

code mode

enabled · 4 eligible tools

Multi-tool run

execute_code("search, compare, summarize")

Catalog

Provider categories first.
Then the full catalog.

Start by lane, then pick exact MCPs. The registry is the source of truth for all provider metadata and catalog state.

Showing all provider categories

30 providers currently represented in the live registry.

Airtable

Database

API key

Algolia

Database

API key

Apify

Other

API key

Asana

Other

OAuth

BigQuery

Database

OAuth

Canva

Art & Design

OAuth

Cloudflare Docs

Other

No auth

CoinGecko

Other

API key

Contentful

Productivity

API key

Datadog

Monitoring

API key

DeepWiki

Other

No auth

Exa

Scraping & Search

API key

Firecrawl

Other

API key

GitHub

Other

OAuth

Google Ads

Other

OAuth

Google Analytics 4

Monitoring

OAuth

HubSpot

Productivity

OAuth

Intercom

Productivity

OAuth

Jira

Other

OAuth

Linear

Other

OAuth

Monday

Productivity

OAuth

Notion

Other

OAuth

PostHog

Monitoring

API key

Sentry

Monitoring

OAuth

Slack

Other

OAuth

Stripe

Other

API key

Supabase

Database

API key

Tavily

Other

API key

Vercel

Debugging

API key

Zapier

Execution

API key

Persona loadouts

Curated outcomes are structured as role-specific loadouts, not generic provider bundles.

Founder Briefing

Founder Office

Track revenue, pipeline, product signals, and strategic notes in one pass.

Stripe HubSpot PostHog Notion
Open in app

Delivery Ops

Engineering Delivery Lead

Tie backlog, execution chatter, and source control state into one delivery view.

GitHub Linear Notion Slack
Open in app

Revenue Ops

Revenue Operations

Watch bookings, delivery tasks, and automation handoffs across revenue systems.

Stripe HubSpot Asana Slack Zapier
Open in app

Payments Ops

Payments Operations

Audit payment events, coordinate fixes, and document runbooks in real time.

Stripe Slack Notion Linear
Open in app

Support Desk

Customer Support Lead

Triangulate conversations, account context, and billing history for faster support.

Intercom HubSpot Stripe Slack
Open in app

Connecting your agent

Three paths.
One URL.

Pick the setup path that matches your client. They all end at the same connection model and the same stable runtime endpoint.

01

One click

Adapted clients

Use the deep-link install flow where it exists. Cursor and the VS Code family can add the URL with a more guided setup path.

CursorVS CodeClineRooKilo

02

One command

File-based clients

Run one command and let Loadoutz detect the client, write config, and apply the connection guidance in one pass.

03

Manual URL

Web and manual setups

Copy the connection URL for Claude.ai, Claude Desktop, Codex, OpenCode, or any client that wants a manual MCP snippet.

https://mcp.loadoutz.io/mcp/u/<owner-id>

Client coverage

Works where developers
already work.

The ecosystem is fragmented. Loadoutz sits above those differences so the setup stays legible while the client mix and MCP stack keep changing.

Client agents

Codex, Claude Code, Replit AI

IDEs

VS Code, Cursor, Windsurf

Extensions

GitHub Copilot, Cline, Roo, Kilo, Continue.dev, Gemini Code Assist

Open source

OpenCode, OpenClaw, Aider, local and OSS runners

Web and manual

Claude.ai, Claude Desktop, snippet-based MCP clients

Pricing

Simple.
No surprises.

Available now

Free

$0

/month

Learn the product, install core tools, and prove value without paying first.

  • 1 workspace
  • 2 loadouts
  • Up to 10 enabled tools
  • 2 active connections
  • Code mode included

Available now

Pro

$29

/month

For individual operators who want more code mode, more tools, and less friction.

  • More workspaces and connections
  • Expanded loadout capacity
  • Higher enabled tool headroom
  • More code mode headroom
  • Higher rate limits

Assisted rollout

Enterprise

$250+

/month

For teams that want managed setup, policy control, and operational help.

  • Dedicated onboarding and 1:1 help
  • Custom imports and provider setup
  • Custom rate and usage limits
  • Priority support and escalation path

FAQ

Common questions.

What is MCP? +

MCP is the Model Context Protocol. It gives AI agents and coding tools a structured way to call external tools such as APIs, search systems, docs, and internal services.

What is a connection? +

A connection is a stable MCP endpoint for a specific client or agent. The client connects once, and Loadoutz controls what tools sit behind that URL.

Can one connection use multiple MCPs? +

Yes. Loadoutz can sit in front of tools and plug-ins discovered from multiple providers. Loadouts decide which subset of those tools the current connection exposes.

What is code mode? +

Code mode is the multi-step execution lane. It lets the agent combine several tool calls or small scripts in one run instead of manually orchestrating everything from prompt context.

Does rotating a connection token revoke OAuth? +

No. Rotating connection access invalidates that client path without tearing down the provider OAuth state behind it.

What if I use open-source agents? +

Loadoutz supports standard MCP connection patterns, including manual snippets for clients such as Codex, OpenCode, and generic JSON-based MCP setups.

When MCP gets hectic,
you should not be reconfiguring everything.

More tools. One connection. A calmer operating model for the next wave of agent tooling.

Get started Agent setup