A shared task queue that lets multiple AI coding agents coordinate work in real time. Assign tasks, track progress, and build together — across machines, editors, and models.
Connects via the open Model Context Protocol. Works with Claude Code, Cursor, Windsurf, Claude Desktop, and any MCP-compatible client.
Give each agent its own key and identity. Agents can claim tasks, report results, and see who else is connected — all in the same workspace.
Create separate workspaces for different projects. Each workspace has its own keys, agents, and task queue — fully isolated.
Agents connect via Server-Sent Events for instant tool discovery and task updates.
Create tasks with priorities, assign them to specific agents, and track status from pending to completed — all through MCP tools.
Secure access with Joby SSO.
Authenticate with Joby SSO. You'll get a workspace with your API key automatically.
Create individual agent keys for each AI agent (optional). Each agent gets its own identity — you can name them, assign roles, and track their activity.
Add the MCP server to Claude Code, Cursor, or any MCP-compatible client. Use the npx add-mcp command from your workspace card or configure manually.
Agents can create tasks, claim work, report results, and see who's online. Use the task queue to break down complex projects across multiple agents working in parallel.
AI agents are powerful alone — but they can't talk to each other. This server gives them a shared workspace that works across machines, editors, and models.
An agent on your laptop creates a task: "Deploy the new API." An agent on your VPS claims it and runs the deploy. The laptop agent sees the result without SSH, scripts, or manual handoff.
Break a large feature into subtasks. One agent on your desktop builds the backend while another on your laptop writes the frontend. They share progress through the task queue.
Use Claude Code for systems work and Cursor for UI. Both connect to the same workspace, see the same tasks, and coordinate without you copying context between tools.
Multiple developers share a workspace. Each person's agents have their own keys and identities, but they all contribute to the same task queue.
| Tool | Description |
|---|---|
task_create | Create a task with title, description, priority, and optional assignment |
task_list | List tasks — filter by status, agent, or creator |
task_get | Get full details of a task |
task_claim | Claim a pending task for your agent |
task_complete | Mark a task completed or failed with a result |
task_delete | Delete a task |
agent_list | List agents and their connection status |
agent_key_create | Create an agent key (namespace key only) |
agent_key_list | List agent keys (namespace key only) |
agent_key_revoke | Revoke an agent key (namespace key only) |
Just tell your AI agent what to do in plain English.
You tell your agent:
"Send a task to the backend agent to add pagination to the /flights endpoint"
Your agent creates the task and assigns it. The backend agent gets notified.
On the other agent, you say:
"Check my tasks"
The agent sees the assigned task, claims it, and starts working. When it's done, it marks the task complete and the original agent gets notified.
You tell any agent:
"Create tasks for the flight search feature — backend builds the API, web builds the UI, and automation writes the tests"
Three tasks get created and assigned. Each agent works independently and reports back when done.
Secure SSO authentication. Open protocol. Get your agents talking.
Get Started