NocoBase
NocoBase's Runner Agent gets conversation management, task links and agent switching mid-thread.
A side-by-side editorial comparison of Avaza and Tracecat — release velocity, themes, recent moves, and the top alternatives to consider.
Avaza ships an MCP server, opening its professional-services suite to AI clients
Avaza is moving on two fronts: a notable strategic push — an MCP server that exposes projects, time-tracking, and billing data to AI clients — and steady product improvements (custom project statuses, a rebuilt subtask model with assignees and time tracking). Educational content reinforces the professional-services positioning around capacity, risk, and resource planning.
Tracecat's 1.3 alphas keep reworking agent plumbing: tunnels, multi-org MCP, pluggable runners.
Tracecat is mid-cycle on 1.3, and nearly every change is agent infrastructure. The alphas route agent MCP and tool calls through tunnels, let one MCP OAuth login cover multiple organizations, trace LLM proxy requests, and raise agent timeouts to two hours. The nightly builds add a session command store, chat steering, and now a pluggable runner for stdio MCP servers.
Avaza is moving on two fronts: a notable strategic push — an MCP server that exposes projects, time-tracking, and billing data to AI clients — and steady product improvements (custom project statuses, a rebuilt subtask model with assignees and time tracking). Educational content reinforces the professional-services positioning around capacity, risk, and resource planning.
Avaza is positioning itself to become the system AI agents read from and write to when a professional-services workflow needs context — quotes, billable hours, project status. The MCP server is the infrastructure for that bet; the subtask rebuild and status customization narrow the gap with heavier-weight project management tools. Cadence is moderate, but the MCP move is unusual for an SMB-focused vendor.
Expect use-case content showing the MCP server driving Claude or ChatGPT workflows around timesheet entry, invoice drafting, and project status updates. Further automation surfaces (webhooks, agentic billing) are likely follow-ons given the MCP foundation.
Tracecat is mid-cycle on 1.3, and nearly every change is agent infrastructure. The alphas route agent MCP and tool calls through tunnels, let one MCP OAuth login cover multiple organizations, trace LLM proxy requests, and raise agent timeouts to two hours. The nightly builds add a session command store, chat steering, and now a pluggable runner for stdio MCP servers.
The 1.3 line is making agents long-running, observable, and able to reach private infrastructure. Maintenance releases on 1.1 and 1.2 carried the same breaking org-scoping fix, so older lines are being patched in parallel.
Session commands and chat steering in the nightlies look set to land in the next 1.3 alpha as user-facing controls for steering running agent sessions.
Other PM products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Avaza or Tracecat.
NocoBase's Runner Agent gets conversation management, task links and agent switching mid-thread.
Camunda opens the 8.11 cycle with job-worker fixes and variable metadata across gRPC, REST and MCP.
Todoist's 2026 bets are on capture: voice via Ramble, photos and files via Task Capture.
Atarim's AI experts now propose changes to live pages as drafts, and the app runs on phones.
Fibery's MCP server can now upload local files, so AI assistants can attach screenshots and images.
SmartSuite adds a scheduled JavaScript runtime with secrets and run history.
See all Avaza alternatives → · See all Tracecat alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — mcp — within PM. Avaza and Tracecat are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Avaza and Tracecat are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other PM products to evaluate alongside.
Top Avaza alternatives in PM are ranked by recent ship velocity. Browse the "Avaza alternatives" section above for the current picks, or visit /alternatives/avaza for the full list with editorial commentary on each.
Top Tracecat alternatives in PM are ranked by recent ship velocity. Browse the "Tracecat alternatives" section above for the current picks, or visit /alternatives/tracecat for the full list with editorial commentary on each.