> ## Documentation Index
> Fetch the complete documentation index at: https://loops.so/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart for agents

> Install the Loops CLI and agent skills so Claude Code, Codex, Cursor, or your coding agent can wire contacts, events, and transactional email into your app.

Give this page to Claude Code, Codex, Cursor, or your own agent when you want
help wiring Loops into your app. Agents can use the Loops CLI and skills to
update your code, read the right docs, and leave credentials in environment
variables.

> [!TIP]
>
> Want to set up Loops yourself? Follow the [Human quickstart](https://loops.so/docs/quickstart.md).

## Install Loops for agents

> [card] Recommended setup
>
> Install the Loops CLI and agent skills with one command.
>
> ```bash theme={"dark"}
> curl -fsSL https://install.loops.so/wizard | sh
> ```

***

Need only one part of the setup?

> [tab] CLI only
>
> ```bash theme={"dark"}
> curl -fsSL https://install.loops.so/cli | sh
> ```

> [tab] Skills only
>
> ```bash theme={"dark"}
> curl -fsSL https://install.loops.so/skills | sh
> ```

Then prompt your agent:

```
Follow https://loops.so/docs/quickstart-agents. Set up Loops in this project.
Use env vars for credentials and show me what changed when you're done.
```

Ask your agent to use the [LMX](https://loops.so/docs/skills.md#lmx) and [email best practices](https://loops.so/docs/skills.md#email-best-practices-skill) skills when you need them.

> [!TIP]
>
> Keep API keys in environment variables. Do not hardcode credentials in prompts,
> scripts, or repository files.

## MCP and agent clients

Most agent tools like ChatGPT, Claude, and Codex can connect directly to Loops through the [Loops MCP server](https://loops.so/docs/mcp-server.md).

For Claude Code, Codex, Cursor, and OpenCode or another agent with terminal access, install the [Loops CLI](https://loops.so/docs/cli.md) and [skills](https://loops.so/docs/skills.md), then ask the agent to follow this page. Keep API keys in environment variables.

## Use cases

* Generate product update emails from recent GitHub releases, merged PRs, or changelog notes.
* Sync new app users to Loops as contacts when they sign up.
* Update contact properties when a user changes plan, role, company, or onboarding status.
* Track product events like `trial_started`, `plan_upgraded`, `invite_sent`, or `onboarding_completed`.
* Send transactional emails for password resets, magic links, invoices, receipts, or team invites.
* Draft or update LMX templates for transactional and product emails.
* Add CLI smoke tests for contact creation, event tracking, and transactional sends.
* Review your email setup with the Loops email best practices skill.

## Go deeper

> [card] [Skills](https://loops.so/docs/skills.md)

> [card] [MCP](https://loops.so/docs/mcp-server.md)

> [card] [CLI](https://loops.so/docs/cli.md)

> [card] [API reference](https://loops.so/docs/api-reference/intro.md)

> [card] [Human quickstart](https://loops.so/docs/quickstart.md)


## Related topics

- [Quickstart](https://loops.so/docs/quickstart.md)
- [Agent skills for Loops](https://loops.so/docs/skills.md)
- [Create and send your first campaign with the API or an agent](https://loops.so/docs/guides/first-campaign-api.md)
- [Loops SDKs](https://loops.so/docs/sdks.md)
- [Events: trigger automated emails with Loops](https://loops.so/docs/events.md)