Human-in-the-Loop Task Manager for AI Agents
Docs / Agents / Integrations
Integrations

Connect Cursor to AgentRQ

Connect Cursor's CLI agent to AgentRQ over the Agent Client Protocol (ACP) for human-in-the-loop task management.

Cursor is a popular AI-native code editor whose CLI agent can run in Agent Client Protocol (ACP) mode, so it can be bridged to AgentRQ with no custom integration code.

Does Cursor Support ACP?

Yes. Cursor's CLI binary (agent) has a built-in acp subcommand that starts it as an ACP server over stdio.

What Connecting via ACP Gets You

Once Cursor's CLI agent is bridged through AgentRQ's ACP Gateway, every task it works on shows up on your AgentRQ 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 Cursor is running in.

Connect Cursor

Wrap Cursor's ACP mode with AgentRQ's gateway:

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

Then point it at your workspace with a .mcp.json in your project root:

json 
{
  "mcpServers": {
    "agentrq": {
      "type": "http",
      "url": "https://WORKSPACE_ID.mcp.agentrq.com/mcp?token=TOKEN"
    }
  }
}

See the ACP Gateway guide for the full setup walkthrough, including where to find your Workspace ID and token.

FAQ

Does Cursor work with AgentRQ?

Yes — Cursor's CLI agent speaks the Agent Client Protocol (ACP), so it connects to AgentRQ through the open-source ACP Gateway with no custom integration code.

How do I connect Cursor to AgentRQ?

Run npx @agentrq/acp-gateway@latest -- agent acp from your project root, with a .mcp.json pointing at your AgentRQ workspace.

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 Cursor — can use AgentRQ as its human-in-the-loop task manager.

References