/mcpso/loops/search

POST /api/mcpso/loops/search

Price: 5 credits

Walk mcp.so's catalogue of agent loops — repeat-until-done recipes such as 'run the build and fix errors until it succeeds' — with name, summary, category, trigger type and the coding agents each loop is known to run on

How to use it

A small curated set of repeatable agent workflows, useful when a caller asks how to automate a recurring engineering chore. `kind` separates loops a human triggers from ones wired to a schedule or event. `category` values are capitalised exactly as shown and a lower-case spelling returns 422. There is no keyword here: a query string is silently ignored by this route.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Number of loops to return (examples: 30; min: 1)
• category string nullable — Restrict to one loop category (one of: "Testing", "Maintenance", "CI", "Debugging", "API", "Automation", "DevOps", "Review", "Database", "Quality", "Planning", "Performance", "Git", "Docs", "Security"; examples: "Testing")

Response

• @type string (default: "McpsoLoop")
• id string required
• alias string required
• url string required
• name string nullable
• summary string nullable
• category string nullable
• kind string nullable
• agents array (default: [])
  • @type string (default: "McpsoLoopAgent")
  • name string required
  • is_active boolean nullable
• is_featured boolean nullable
• is_verified boolean nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.