Labsco
MCP SERVER

Loop MCP Server

by smogili1

Walk an array item by item — or in batches — with results collected and released only at the end.

Reasoning Scaffolds & Agent Workflow Engines
Summary
The list gets finished, not abandoned halfway.

Asked to process fifty items, a model will do eight and summarise. Handing them out one at a time with the remaining count attached — and refusing to release the results until the array is empty — turns that into a loop that actually terminates.

What it is

A processing harness for a list: load an array with a task description, pull items one at a time or in batches, store each result as it comes, and take the whole set once every item is done.

What you get
  • An array loaded with a task description and an optional batch size, defaulting to 1
  • The next item returned with its index, the task, and how many remain
  • The next batch, when a batch size is set, with indices and remaining count
  • A result stored per item or per batch
  • All results retrieved at the end with an optional summary — the call errors while items remain
  • A reset that clears the current processing state
Requirements

Node, with npm install and npm start. No account and no key, and nothing leaves the machine.