Summary
It closes the loop that usually gets dropped: telling the people who asked.
Reading the backlog is the easy half — top requests by votes or revenue, semantic search across feedback, and a prioritisation pass. Notifying requesters is the call that does the thing nobody has time for once the feature actually ships.
What it is
A server over a Featuriq workspace, the product feedback and roadmap tool. It reads feature requests and customer feedback, and writes status changes back.
What you get
- get_top_requests — the top feature requests, sorted by vote count or by revenue impact
- search_feedback — semantic search across feedback posts, which finds relevant results even when the exact words do not match
- get_feature_feedback — the feedback attached to one feature
- get_prioritization — an AI prioritisation pass over the backlog
- update_feature_status — a feature's status changed
- notify_requesters — the people who asked for a feature told about it
Requirements
A Featuriq account and its API key, from Settings → API, set in your client config. It runs from npx, and the API base URL can be overridden if you need to point it elsewhere.