Backloop catches where agents get stuck on your API or MCP server, ranks each problem by impact and drafts the fix as a pull request.
You approve. Nothing ships without you.
~/acme $ claude -p "Find companies hiring GTM engineers" ⏺ GET /companies/search?hiring_role=gtm_engineer 200 └ unknown parameter ignored · 20 results ⏺ GET /companies/cmp_001/jobs 200 ⏺ GET /companies/cmp_002/jobs 200 └ … 497 more calls, all 200 ⏺ submit_feedback missing_capability 202 └ known_issue: "Add a hiring_role filter" · acknowledged ── backloop ────────────────────────────────────────── cluster hiring-role-filter · 24 reports · 13 accounts priority ████████░░ 78 build claude-code · 2 files · tests pass ? Approve and open a draft PR? [y/N]
Free audit
Paste the address of your MCP server or API. You get a score out of 100, each gap an agent would hit, and the fix. A few seconds, no signup.
About 20 public requests. No tool is called and nothing is stored.
State of MCP servers · Nov 2026
01The problem
AI agents use your API for your customers. When something is missing, they give up or take a slow way around it. Your logs never tell you.
What your logs see
access.log10:04:11Z 200 GET /companies/search?hiring_role=gtm_engineer total=20 unknown parameter ignored 10:04:12Z 200 GET /companies/cmp_001/jobs 10:04:12Z 200 GET /companies/cmp_002/jobs 10:04:12Z 200 GET /companies/cmp_003/jobs … 496 more, all 200
What the agent tells you
POST /feedback{
"type": "missing_capability",
"goal": "Find companies currently hiring GTM engineers",
"endpoint": "/companies/search",
"message": "No hiring-role filter is available",
"workaround": true,
"workaround_description": "500 calls to /companies/{id}/jobs"
}
02How it works
Add one SDK to your API or MCP server. Backloop does the rest.
03What you get
Demo data: 67 reports from 17 customers, grouped into 8 problems
What agents were trying to do
04You approve
Every fix waits for you, with the code, the test results and the reports behind it.
claude-code · backloop/hiring-role-filter
Add a hiring_role filter to /companies/search
src/companies.js@@ -32,6 +32,9 @@ export function searchCompanies(params) if (params.country) results = results.filter(…);+ if (params.hiring_role) {+ results = results.filter((c) =>+ c.jobs.some((job) => job.role === params.hiring_role));+ }test/companies.test.js+test("search filters by hiring role", () => { … });
05Pricing
You pay for events: one agent call to your API or MCP server, or one report. Fixes are counted on their own.
Free
See where agents get stuck.
$0forever
No card.
Starter
One service, with fixes written for you.
$49/ month
Billed monthly.
Growth
For teams with several APIs or MCP servers.
$399/ month
Billed monthly.
Custom
More volume, in your own cloud.
Talkto us
Billed annually.
More events$40 per 100k on Starter, $20 per 100k on Growth. On Free, sessions stop recording until next month.
More fixes$6 per fix beyond your plan.
Reports never dropAgent reports always go through, even over your limit.
Open sourceThe protocol and SDKs are free to use (Apache-2.0). Run it yourself ↗
06Questions
Because you ask it to. Backloop gives agents a feedback tool and short instructions. On an MCP server they see it like any other tool, and your error messages point to it.
Most don’t. On an MCP server, Backloop records each session and flags the ones that failed on its own. They land in the same list as the reports.
Reports are checked, rate limited and de-duplicated. They’re treated as data, never as instructions. The coding agent can’t browse the web or push code, and nothing ships without your approval.
No. The protocol is open source, so you can build it yourself. The platform does the grouping, ranking and fixes for you.
One attempt: Backloop writes a change and runs your tests. It only starts when someone on your team clicks. Fixes start on Starter.