AgentRQ MCP
A self-hosted task manager for human and agent collaboration through MCP
- 1,191 ★ on the repository
- Last commit
- AGPL-3.0
Extended access
Why this level
- The agent creates and changes tasks in the workspace through MCP
- Requires a deployed network service with access tokens
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/agentrqDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent creates and changes tasks in the workspace through MCP
- Requires a deployed network service with access tokens
This is third-party code. Review the repository files before installing.
What it does
AgentRQ is a shared workspace where a human and AI agents run tasks together. Through MCP the agent sees the workspace state: it pulls assigned tasks, updates statuses, requests permission for important actions and replies to the human, all synced across devices. It has a task board and kanban, scheduling and recurring task launches, named events that spawn new tasks, and workflows as a node graph. It connects to Claude through a project .mcp.json with the workspace URL and token. The product is open-source and self-hosted, including via Docker.
Who it is for. For teams and developers who want to assign tasks to agents and track their work in one place.
Good fit when
- You want to give the agent tasks and see their status on a board
- You want a human in the loop for the agent's important actions
- You need schedules, recurring tasks and events that trigger work
Not a fit when
- You do not need a separate task manager on top of the agent
- You cannot deploy and maintain a self-hosted service
Example request
Pull my assigned tasks from AgentRQ and mark the finished one as doneMCP
- Transport
- http
- Authentication
- API key
Limitations
It is a self-hosted platform you deploy and keep running, with a Docker image and a separate guide for production. The agent connects over MCP through a URL with the workspace token. Setup assumes working with the project config and permissions.
How to disable. Remove the agentrq server from the project's .mcp.json and stop the deployed service.
FAQ
How does the agent see tasks?
Through MCP the agent reads the workspace state, pulls tasks, updates statuses and replies to the human.
Can I self-host it?
Yes, the project is open-source and self-hosted, with a ready Docker image for production.
Discussion
No questions or reviews yet.
Related
MCP serversA task manager for AI-driven development: breaks a PRD into dependent tasks and guides the agent through them via MCP or CLI
The official Taskade MCP and plugin: an agent manages workspace projects, tasks, automations and AI agents.
A self-hosted issue tracker and wiki on Cloudflare with MCP: 126 tools, issue leases and file claims for several agents
Teamwork.com tasks, Desk tickets, Spaces pages and chats for an agent: a hosted server with role profiles and a read-only mode
The MCP endpoint of a Salt workspace on your server: an agent creates pages, databases and comments with a person rights.
A free task manager with issues, sprints and docs and a built-in MCP server with about sixty tools.
README in short
The README describes AgentRQ as an MCP-based human and agent collaboration platform: the agent sees the workspace state, pulls tasks, changes statuses, requests permissions and replies. It has a board and kanban, scheduling, recurring tasks, named events and node-graph workflows. Connecting to Claude goes through .mcp.json with a URL and token, and pre-approving the needed tools is suggested for important actions. The project is self-hosted, including via Docker. Apache-2.0 licensed.