agent-board

Agent Board is a MCP-enabled multi-agent task orchestration server designed to manage work across AI agents in a Kanban-style board. It exposes a REST API and a set of MCP tools that agents can use to interact with tasks, comments, and workflow state transitions. The server enforces DAG dependencies, auto-retries failed tasks, supports task chaining, and maintains a complete audit trail. It also integrates with OpenClaw for triggering agent wakeups and supports HMAC-SHA256 signing for outbound webhooks, ensuring secure inter-agent communications. To get started, run the server and access the dashboard or REST API to create tasks, define templates, and configure webhooks and authentication as needed. The MCP tooling allows agents to perform actions such as reading task threads, posting comments, and retrieving full task context through dedicated MCP tools, enabling seamless agent-to-agent collaboration without bespoke orchestration code.

Prerequisites:

• Git
• Node.js (14+ or compatible) and npm
• Optional: Docker if you prefer containerized deployment

Install steps:

1. Clone the repository git clone https://github.com/quentintou/agent-board.git cd agent-board

2. Install dependencies npm install

3. Build the project (if a build step is required by the project) npm run build

4. Run the MCP server npm start

5. Access the server

   • Dashboard: http://localhost:3456
   • REST API: http://localhost:3456/api

Environment configuration (optional but common):

• AGENTBOARD_API_KEYS: Comma-separated key:agentId pairs for API authentication (e.g., sk-abc123:agent1,sk-def456:agent2)
• OPENCLAW_HOOK_URL: OpenClaw webhook URL for agent notifications (default: http://localhost:18789/hooks/agent)
• OPENCLAW_HOOK_TOKEN: Bearer token for OpenClaw webhook calls
• AGENTBOARD_WEBHOOK_SECRET: Secret for HMAC-SHA256 webhook signing (enables signature headers)
• TEMPLATES_DIR: Custom templates directory (default: ./templates)

Tips and common considerations:

• If you enable AGENTBOARD_WEBHOOK_SECRET, outbound webhooks will include X-AgentBoard-Signature headers for verification by recipients.
• Ensure OPENCLAW_HOOK_URL is accessible from the Agent Board host when integrating with OpenClaw.
• Use AGENTBOARD_API_KEYS to restrict access; when omitted, authentication may be disabled per backward compatibility.
• The MCP tooling (e.g., board_list_comments, board_add_comment, board_get_task_thread) enables MCP-based interactions without HTTP calls.
• Review the default ports and data directories (e.g., port 3456 and data directory) and customize via command-line flags or environment configuration as needed.