MCP Loadouts

Curated MCP server stacks for specific roles and workflows. Each loadout ships with a one-click JSON config for Claude Desktop, Cursor and Windsurf — no more setting up the same five servers from scratch every time.

Featured loadouts

All loadouts (15)

FAQ — MCP Loadouts

  • What is an MCP loadout?

    A loadout is a curated set of MCP servers configured to work together for a specific role or workflow — like Postgres developer or solo founder. Instead of installing servers one by one, you copy a single JSON config that wires the whole stack into Claude Desktop, Cursor or Windsurf.

  • How is this different from a flat MCP directory?

    Most directories list servers individually. Loadouts ship as ready-to-use combinations: each one is a tested stack with a copy-paste config, real-world scenarios, and notes on what each server contributes. You spend less time configuring and more time using your agent.

  • Do these loadouts work with Cursor and Windsurf?

    Yes — every loadout includes configs for Claude Desktop, Cursor and Windsurf. The MCP protocol is identical across these clients; only the config file path differs.

  • Can I submit my own loadout?

    Yes. Email the team via the Submit page with your stack, the role it targets, and a few example prompts. We review every submission before publishing.

  • Are loadouts free to use?

    Yes — Loadout itself is free to browse. Most listed MCP servers are open-source. A few use paid APIs (Stripe, SendGrid, Linear) where the underlying SaaS has its own pricing.