Post

I'm testing the @debugbear.com MCP with Claude Code, and my first impression is that combining DebugBear's great tools with the power of AI Agents is awesome for creating executive and detailed technical reports... #WebPerf #PerfTools #AI #WebPerfAI

17/7/26, 6:18 pm0 reposts1 like

Joan León

@nucliweb.net

17 July

And if you have the opportunity to run it on the source code, the potential is impressive. I'll write a post with my experience and thoughts.

Joan León

@nucliweb.net

17 July

www.debugbear.com/docs/mcp

debugbear.comAccess Web Performance Data With The DebugBear MCP Server | DebugBearConnect AI assistants like Claude and ChatGPT to DebugBear using the Model Context Protocol (MCP) to run tests, query metrics, and manage projects.

Reid Marlow

@reidmarlow.com

17 July

The report angle is where MCP makes the most sense to me: let the agent gather evidence, but keep the final call tied to traces, budgets, and URLs. What would you use as the acceptance test?

Joan León

@nucliweb.net

17 July

Simple test: every conclusion needs an `evidence` field pointing to real data (Lighthouse, RUM, waterfall), not generated text. If the agent can't cite it, it doesn't make the report. Testing it with any specific workflow?

Reid Marlow

@reidmarlow.com

17 July

That's the right constraint. I'd make the evidence field a URL + timestamp + raw metric, not a summary. Otherwise the agent just moves the hallucination into the citation box. What are you testing first?