> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.merge.dev/merge-workforce/rollout/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.merge.dev/_mcp/server.

# Roll out to your fleet

> Build once. Connect to every API, tool, and LLM. Ship products and agents to production without owning the integration stack.

## Docs

- [Roll out to your fleet](https://docs.merge.dev/merge-workforce/rollout/overview.md): How the Agent Handler tool rollout and the Gateway model rollout differ, which pages apply to the products you have, and how to verify either one landed.
- [Roll out tools](https://docs.merge.dev/merge-workforce/rollout/tools.md): How to deploy the Workforce MCP endpoint through Claude Code managed MCP, Codex managed configuration, and the admin consoles of Cursor, Windsurf, Copilot, and Gemini CLI, and what each one can and cannot enforce.
- [Roll out models](https://docs.merge.dev/merge-workforce/rollout/models.md): Compare the Workforce desktop client and employee self-setup for rolling Merge Gateway out across a company, with per-client coverage for each supported AI client.
- [Connect employee AI clients](https://docs.merge.dev/merge-workforce/rollout/employee-clients.md): Per-client connection details for employee AI clients: the Workforce MCP endpoint for tools in Claude, Claude Code, Cursor, Windsurf, and VS Code, and the Gateway base URL and key for models.
- [Workforce CLI](https://docs.merge.dev/merge-workforce/rollout/workforce-cli.md): What the `mfw` CLI does, the built-in chat that uses AI Gateway models and Agent Handler tools in one conversation, how mfw login authenticates against your identity provider, the per-device Gateway credential it mints, and when to reach for it instead of the desktop client.