Loops - Turn User Feedback Into Production Code Automatically
Don't just collect requests—ship them.
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeCan modify data
What it can do
- List Loops: List all feedback loops in this workspace. START HERE to discover available work. Returns loop names, statuses, and feedback counts. Look for loops with approved_count > 0 to find items re
- Get Loop: Get a specific loop with all its feedback items, comments, and vote counts. Use this to see the full details of a loop including all feedback regardless of status.
- Get Task List: Get a simplified task list for a loop showing all feedback items and their current status. Perfect for tracking work progress. Returns: { loop, status, items: [{ id, name, status, votes
What data it sees
Do you need an account
No: the server works without sign-in
Don't just collect requests—ship them. Loops integrates with AI Agents like Claude, Codex, and Cursor to write the code for top-voted features and notifies users the moment it’s live.
Server tool list (11)
Raw names from tools/list. Only developers need these.
| list_loops | List all feedback loops in this workspace. START HERE to discover available work. Returns loop names, statuses, and feedback counts. Look for loops with approved_count > 0 to find items ready to implement. |
| get_loop | Get a specific loop with all its feedback items, comments, and vote counts. Use this to see the full details of a loop including all feedback regardless of status. |
| get_task_list | Get a simplified task list for a loop showing all feedback items and their current status. Perfect for tracking work progress. Returns: { loop, status, items: [{ id, name, status, votes }] }. Statuses: open (new), accepted (approved), in_progress (being worked on), shipped (done), rejected (declined). |
| get_approved_feedback | Get feedback items with "accepted" status that are ready for implementation. Use this to find work to do. Before starting work on an item, call update_feedback_status to mark it "in_progress". |
| get_pending_feedback | Get feedback items with "open" status that need review. Use this to find items awaiting approval. Present these to the user and let them decide to accept or reject each one using update_feedback_status. |
| update_feedback_status | Update the status of a feedback item. Workflow: open → accepted (approve for work) → in_progress (started) → shipped (done). Or: open → rejected (decline). Always mark "in_progress" before starting work, and "shipped" when complete. |
| create_loop | Create a new feedback loop in the workspace. Loops collect user feedback that can be triaged and implemented. Use "public" visibility for open feedback, "private" for team-only. |
| close_loop | Close a loop for new feedback submissions. Use this when you want to stop accepting new feedback but continue working on existing items. Can be reopened later with reopen_loop. |
| reopen_loop | Reopen a closed loop to accept new feedback again. Cannot reopen shipped loops. |
| ship_loop | Ship a loop, marking it complete and notifying all members via email. The loop must be "closed" first. This is final — shipped loops cannot be reopened. Use this when all feedback has been addressed. |
| get_workflow | Get step-by-step instructions for common Loops workflows. Use this if you need guidance on how to work with Loops. Available workflows: discover (find loops), implement (build approved items), review (triage pending feedback), create (set up new loop). |