Alternatives
Products that do what FlowLens – MCP server for debugging with Claude Code does
Hi HN, We often run into this with coding agents like Claude Code: debugging turns into copy-pasting logs, writing long explanations, and sharing screenshots. FlowLens is an MCP server plus a Chrome extension that captures browser context (video, console, network, user actions, storage) and makes it available to MCP-compatible agents like Claude Code. You can try it here: https://magentic.ai/flowlens Any feedback—good, bad, or brutal—is welcome.
- 1
- 2
- 3
- 4
- 5AB
Hi HN, Zidan here. I’ve been experimenting with AI-assisted debugging and noticed a recurring gap: most tools optimize for agent-led exploration (ex: giving claude code a browser to click around and try to reproduce an issue). But in many cases, I've already found the bug myself. What I actually want is a way to hand the agent the exact context I just saw - without retyping steps, copying logs, or hoping it can reproduce the behavior. So we built FlowLens, an open-source MCP server + Chrome extension that captures browser context and lets coding agents inspect it as structured, queryable…
Nov 2025 · github.com
- 6
- 7
- 8
- 9
- 10
- 11
- 12CC
Codex runs as an MCP server, Claude orchestrates a five-perspective review (security, correctness, compliance, performance, maintainability). Drop the SKILL.md into your repo's .claude/skills/ folder. MIT licensed.
Feb 2026 · github.com
- 13LC
Debugging is hard for LLMs, because they primarily depend on source code, and they don't have access to runtime state. I spent countless hours debugging code, and the only way I found LLMs useful for that, is to ask them to add log lines. That's annoying, because it pollutes my code and adds unnecessary diffs. So we made an MCP server that solve this problem. It gives MCP clients (like Claude Code) access to a NodeJS inspector, so they can: 1. set breakpoints 2. step in, step out, continue 3. fetch the current execution location 4. read console output 5. run JS using eval To try: 1. run a…
2025 · github.com
- 14
Hi y'all. Been working on something that should've been made a long time ago imo. It compiles codebases into O(1) hashmaps that the agent queries to discover the structure of your code/answer questions/write code. It also does complete static analysis checks on any writes the agent makes. Don't take my word for it though. Here are the benchmarks: https://benzi.fly.dev/benchmark. on 2/20 tests, Claude Code (mostly Sonnet on one task) regressed or timed out. Benzi didn't because of course, it has a map it can query and not get lost in the sauce. On the other 18 it…
28d ago · benzi.fly.dev
- 15EC
I participated in the Nvidia + Vercel 2 hour hackathon in SF tonight, and built something I've wanted, but hadn't tried building. I implemented an MCP Server and VS Code extension to allow Claude Desktop to place breakpoints, step through code, and execute expressions (assuming language support). So you can ask it a question that requires actually stepping through the code and now it can actually do that - check values for you, etc. It's _definitely_ not perfect. Have improvements? Please make a PR!
2025 · github.com
- 16
- 17
- 18DD
2025 · blog.kuzudb.com
- 19
- 20
- 21SI
Claude Code is amazing for individuals but terrible for teams. I spent the last six months building my perfect mix of MCP servers, subagents, commands and skills. Claude Code writes 100% of the code now, but sharing this with my team? Painful. 1. Blog posts and workshops don't work (and don't scale) 2. Committing tools to N repos means N PRs. A tool changes? N more PRs. 3. Same tools, different files or folders for each AI assistant; not everyone uses Claude Code It is like 1999 all over again; FTPing files up to prod and versioning with ".bak" suffixes. So I built sx. It is your team's…
Jan 2026 · github.com
- 22
- 23SM
I built this because I got tired of watching Claude Code read through massive files just to find a few functions. Sourcerer lets AI agents search code semantically and grab exactly the code chunks they need instead of burning tokens on whole files. It uses tree-sitter to parse your codebase and creates a searchable index. So instead of "read auth.py (538 lines)", an agent can search for "user authentication logic" and get back just the relevant functions. Demo: https://asciinema.org/a/736638 GitHub: https://github.com/st3v3nmw/sourcerer-mcp
2025 · github.com
- 24
Stop your coding agent from guessing at datasheets
Jun 2026 · docs.byteask.ai
Ranked by how close each launch is in meaning, then by votes. Refine with a description →