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

# Setup

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

## Docs

- [Building an agent](https://docs.merge.dev/merge-agent-handler/setup/building-an-agent.md): End-to-end setup for an agent inside your product: API keys, Tool Packs, Registered Users, Link, and the MCP call from your backend.
- [Agent quickstart](https://docs.merge.dev/merge-agent-handler/setup/agent-quickstart.md): You have no Merge account, no API key, and nobody around to sign up for one. One unauthenticated request creates an organization, an API key, a tool pack, and a registered user, so an AI agent can start calling tools immediately. A human can claim the organization later.
- [Agent Handler for Employees](https://docs.merge.dev/merge-agent-handler/setup/agent-handler-for-employees.md): How to set up Agent Handler for employees: IT configures which tools each role can access, and employees connect their AI client to a single MCP URL and authenticate through SSO.
- [Enforce the endpoint through client policy](https://docs.merge.dev/merge-agent-handler/setup/client-policy.md): How to push https://ah-api.merge.dev/mcp to every employee through Claude Code managed MCP, Codex managed configuration, and the admin consoles of Cursor, Windsurf, Copilot, and Gemini CLI, and what each client can enforce.
- [Local development](https://docs.merge.dev/merge-agent-handler/setup/local-development.md): How to install the Merge CLI, authenticate, and connect Agent Handler to your local coding agent.