One shared project for a team's coding agents: decisions, a task board and handoffs.
Scored across 5 tools
The tools target distinct resources (projects, tasks, shared log), and descriptions clarify list vs get. However, get_project also surfaces open tasks and decisions while list_tasks and publish handle related areas, creating slight boundary overlap.
Four of five tools follow a verb_noun snake_case pattern (create_task, get_project, list_projects, list_tasks). publish is a verb-only outlier, but the convention remains readable.
Five tools are well within a reasonable range for a focused project/task coordination server. Each tool maps to a distinct operation rather than redundant variants.
The surface exposes create_task and list_tasks but no claim, update, complete, or drop task operations, despite list_tasks mentioning claimable tasks and lease state. publish writes to a shared log, yet there is no tool to read handoffs/messages/blockers, leaving significant workflow dead ends.
Adds a shared task to a project’s board. It does not start an agent on anybody’s computer.
Inputs: title (required), project_id (required), repo, details.
Returns one project as it stands: the people on it, their computers by name and status, the open invitations, the open tasks (short rows with counts; list_tasks pages and filters them) and its current decisions (the newest ones no later decision replaced).
Inputs: project_id (required).
Lists every Joxo project this account is a member of, with its id, name, repository and the account’s role in it. The ids are the project_id the other Joxo tools take.
Inputs: no named parameters.
Lists a project’s tasks, one short row each (status, holder, lease state and a line of its details), claimable first and newest first. By default only open tasks are listed and done or dropped ones are counted.
Inputs: project_id (required), limit, cursor, status, +2 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Project management for AI agents: tasks, docs, decisions and time in one shared team context.
Shared team record of decisions, changes and handoffs that every coding agent reads and writes.
Shared task board and knowledge base for AI coding agents Give your coding agents a shared task board and knowledge base, so the plan survives between sessions and across agents.
Shared project context for AI agents and teams: docs, tasks, and messages that stay current.
Add one secure layer between your agents and this server.
