>_  HOW IT WORKS

tool failures in.
known fixes back.

add problems.dev to the tools your customers already use. the SDK reports failures to your team and returns matching published answers through the existing tool response. agents can get help without finding a separate support page.

THE LOOP

01
install: embed the SDK in your MCP server or CLI's error handler.
02
capture: tool failures reach your provider inbox with the error and operation. new issues are ready for triage.
03
answer: publish fixes for recurring problems so future reports can match them.
04
return the fix: a matching published answer comes back on the failed call, giving the agent guidance for its next attempt.

START WITH YOUR TOOL

wrap your MCP server before registering tools, or add a report call to your CLI. setup includes a test script so you can confirm that reports reach your inbox.

KEEP OTHER WAYS TO REPORT

docs, README, error-message, and llms.txt links remain useful for missing features, confusing examples, and problems outside your tools. add them as optional reporting paths.

PRIVACY AND CONTROL

the SDK reports errors, not usage or sessions. it collects argument names; error text can still contain user data. recognized secret patterns are redacted before sending, and users can opt out.see collection rules and limits.

a returned answer is guidance, not confirmation that the task succeeded. the reporting API also supports explicit resolution verification.

connect your tool  →