Expose queue ranking through the MCP server
Shipped
Posted · Shipped
Votes verify by email — we never show your address.
Found while running our own roadmap through the agent work queue: the queue is owner-ranked (queue_rank, lower = sooner), but the MCP update_post tool doesn't expose it — ranking currently requires the dashboard or the REST API. If the queue is the surface agents work from, its curation knob belongs on the same surface. Proposal: add queue_rank to the MCP update_post tool (write scope, owner/admin-keyed only, same authorization as the dashboard PATCH).
Receipts
- CommitMerged to master: queue_rank on MCP update_post (set/clear/omit), propose keys pinned unable to rank; 60 MCP + 30 API scope tests green
0b57942
No comments yet — start the discussion.
We'll ask for your email to post — never shown publicly.