AgentRQ integrates with Claude Code via the native MCP protocol. One entry in .mcp.json gives Claude access to 6 purpose-built tools for human collaboration — no wrappers, no hacks, no polling loops.
{
"mcpServers": {
"agentrq": {
"type": "http",
"url": "https://WORKSPACE_ID.mcp.agentrq.com/mcp?token=TOKEN"
}
}
}Each tool serves a specific purpose in the Claude ↔ Human collaboration loop.
createTask
Claude's primary way to ask for your input. Creates a task with a title, full context in the body, and optional file attachments. You see it instantly in the dashboard.
updateTaskStatus
Transitions a task through its lifecycle: notstarted → ongoing → completed / rejected. Call immediately when starting work, and when done. Keeps the dashboard accurate.
reply
Sends a message in a task thread — from Claude to you. Use it for progress updates, follow-up questions, or sharing output (with file attachments like diffs or logs).
getWorkspace
Fetches workspace metadata and the mission context you've set. Call at the start of every session to confirm connectivity and load any project-specific instructions.
getTaskMessages
Retrieves the full message history of a task thread — paginated with cursor. Useful when resuming long tasks or reviewing what was decided in a previous turn.
downloadAttachment
Fetches a file you attached in the dashboard. Returns base64-encoded content. Enables true bidirectional file exchange — you can hand Claude a design, config, or dataset mid-session.
The most powerful way to use AgentRQ is to add instructions to your CLAUDE.md — telling Claude exactly when to ask you, what context to include, and what it can proceed with autonomously.
## AgentRQ — Human-in-the-Loop
At the start of every session:
→ Call `getWorkspace` to load mission context.
→ Report what you're connected to.
Before any of these, STOP and call `createTask`:
- Database schema changes or migrations
- Anything that deletes or drops data
- Production deployments or config changes
- External API calls with write side effects
- Spending money (OpenAI, Stripe, etc.)
When creating a task, always include:
- What you've done so far
- Exactly what you need approval for
- The risk if they say yes
- The fallback if they say no
After human replies via channel:
→ Read the message carefully
→ Call `updateTaskStatus("completed")`
→ Continue with their instructions
# Be specific in tasks. Vague asks = slow unblock.No proprietary protocols. No vendor lock-in. AgentRQ uses standard MCP SSE transport — the same protocol powering the Claude ecosystem.