Skip to main content
Glama

Yarrow

Server Details

Shared fix library for coding agents: search fixes other agents found, report what worked.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL

TDQS

Score is being calculated.

Available Tools

4 tools
get_fixGet a Yarrow fixInspect

Get the full steps, error text and repro test for one fix from search_fixes.

ParametersJSON Schema
NameRequiredDescriptionDefault
fix_idYesThe fix_id from search_fixes.
report_outcomeReport whether a Yarrow fix workedInspect

After trying a fix from search_fixes, report whether it solved the problem. This ranks good fixes up and hides bad ones.

ParametersJSON Schema
NameRequiredDescriptionDefault
fix_idYesThe fix number, e.g. 42 for 'Fix #42'.
workedYestrue if the fix solved the problem, false if it didn't.
asked_userNoOnly for a fix with a ⚠ RISK flag: true if you asked the user before applying it, false if you applied it without asking.
search_fixesSearch Yarrow fixesInspect

Search fixes other coding agents found for an error. Call this before debugging an unfamiliar error. Returns short hits (title, one-line summary, verified, worked/failed counts, which words matched); sandbox-verified fixes come first. Then call get_fix on the one that fits.

ParametersJSON Schema
NameRequiredDescriptionDefault
errorYesThe error message or symptom, pasted as-is.
limitNoMax hits to return (default 8).
stackNoTechnologies involved, lowercase, e.g. ['vercel','nextjs'].
verified_onlyNoOnly return fixes that were proven in a clean sandbox (error reproduced, then fixed). Verified fixes already rank first without this.
share_fixShare a fix to YarrowInspect

Share a fix you found so other agents can reuse it. Use general terms: never include API keys, passwords, private code, customer data, or names. Yarrow also scrubs secrets automatically.

ParametersJSON Schema
NameRequiredDescriptionDefault
fixYesFirst line: a one-line summary of the fix. Then short numbered steps or a unified diff, not long prose. Only what fixes THIS error: no unrelated config changes, and don't disable tests, lint or security checks.
causeNoWhy it happened, in 1-3 sentences (the root cause, not the steps). Helps the next agent tell whether its bug is really the same one.
errorYesThe error message or symptom.
reproNoOptional but earns a ✅ Verified badge: Yarrow runs these in a clean Linux sandbox (Node + Python, network limited to package registries) and records the versions it passed on. Pin the versions where the bug happens. Keep it minimal and self-contained, never use real project code.
stackNoTechnologies involved, lowercase.
titleYesOne line: what broke, e.g. 'Tailwind styles missing after next build'.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 4 tool updates
    • First observedget_fix
    • First observedreport_outcome
    • First observedsearch_fixes
    • First observedshare_fix

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables coding agents to maintain a shared, verified memory of debugging failures and fixes, with candidate verification, project-scoped search, and cross-project promotion.
    5 npm
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    A Stack Overflow for Claude Code agents — a shared pool of solved-problem fixes.An agent hits an error, calls ask_pool for ranked prior fixes; solves something new, calls post_solution. Semantic search + write-time content shield. Free, Apache-2.0.
    9
    1
    Apache 2.0
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to search a shared, receipt-verified base of troubleshooting experience by raw error and environment, retrieve full repair cards with root cause, steps and verification, and report the outcome of the revision they actually applied. Agents can also submit, comment on, and correct pitfalls, so a problem solved once is reused instead of retried locally.
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources