---
title: "Amp ACP Setup | AgentRQ Docs"
url: https://agentrq.com/docs/agents/amp
description: "Amp ACP setup: run the Amp coding agent over the Agent Client Protocol and connect it to AgentRQ for human-in-the-loop task management."
---

[Docs](https://agentrq.com/docs/) / Agents / Integrations

Integrations

# Amp ACP Setup

Amp ACP setup: run the Amp coding agent over the Agent Client Protocol and connect it to AgentRQ for human-in-the-loop task management.

[Amp](https://github.com/tao12345666333/amp-acp) is a community-built ACP wrapper around Amp, the frontier coding agent. It speaks the Agent Client Protocol (ACP), so it runs behind AgentRQ's gateway with no custom integration code.

Wondering which other coding agents support ACP? See the [ACP support table](https://agentrq.com/blog/which-coding-agents-support-acp-agent-client-protocol) for 33 agents.

Want Amp to use websites too? [Connect Amp to WebMCP](https://agentrq.com/docs/webmcp/amp) shows how it can call a site's WebMCP tools in your own Chrome.

## Does Amp Support ACP?

Yes. Amp publishes an ACP server to the [ACP registry](https://github.com/agentclientprotocol/registry) as `amp-acp`, so AgentRQ's gateway can fetch and run it by name — there is nothing to install by hand.

## What Connecting via ACP Gets You

Once Amp is bridged through AgentRQ's [ACP Gateway](https://agentrq.com/docs/connect-acp-agent), every task it works on shows up on your AgentRQ [task board](https://agentrq.com/features/task-board) in real time. You can approve risky commands, reply with extra context, or reassign work — from the dashboard or Slack — without touching the terminal Amp is running in.

## Connect Amp

Copy the `.mcp.json` for your workspace from **Settings → Setup** in the AgentRQ app, save it in your project root, then run both commands from that directory.

Log in (the first run also downloads the agent):

bash

```bash
npx @agentrq/acp-gateway@latest --login --agent amp-acp
```

Start the bridge, and leave it running — it picks up tasks as you assign them:

bash

```bash
npx @agentrq/acp-gateway@latest --agent amp-acp
```

Amp ships as a prebuilt binary, which the gateway downloads, checks and caches per agent, version and platform.

## Choosing a Model

Ask Amp which models it supports, then start it on one of them:

bash

```bash
npx @agentrq/acp-gateway@latest --list-models --agent amp-acp
npx @agentrq/acp-gateway@latest --model <model-id> --agent amp-acp
```

Omit `--model` to take whatever the agent defaults to. The gateway applies the model as each session opens and reports it back to AgentRQ, so the workspace shows which model actually ran.

## FAQ

**Does Amp work with AgentRQ?**

Yes — Amp speaks the Agent Client Protocol (ACP), so it connects to AgentRQ through the open-source [ACP Gateway](https://agentrq.com/docs/connect-acp-agent) with no custom integration code.

**How do I connect Amp to AgentRQ?**

Save your workspace's `.mcp.json` in your project root, log in with `npx @agentrq/acp-gateway@latest --login --agent amp-acp`, then start the bridge with the same command minus `--login`.

**What is the Agent Client Protocol (ACP)?**

ACP is an open, editor-agnostic protocol that lets any coding agent talk to any client over a standard JSON-RPC interface. AgentRQ's gateway implements the client side of ACP, so any ACP-compatible agent — including Amp — can use AgentRQ as its human-in-the-loop task manager.

## References

- → [Which coding agents support ACP?](https://agentrq.com/blog/which-coding-agents-support-acp-agent-client-protocol)
- → [Amp documentation](https://github.com/tao12345666333/amp-acp)
- → [Agent Client Protocol specification](https://agentclientprotocol.com)
- → [AgentRQ ACP Gateway guide](https://agentrq.com/docs/connect-acp-agent)
- → [Connect Amp to WebMCP](https://agentrq.com/docs/webmcp/amp)