nowfound

Alternatives

Products that do what I built a debugging MCP server that saves me ~2 programming hours a day does

Hi! Deebo is an agentic debugging system wrapped in an MCP server, so it acts as a copilot for your coding agent. Think of your main coding agent as a single threaded process. Deebo introduces multi threadedness to AI-assisted coding. You can have your agent delegate tricky bugs, context heavy tasks, validate theories, run simulations, etc. The cool thing is the agents inside the deebo mcp server USE mcp themselves! They use git and file system MCP tools in order to actually read and edit code. They also do their work in separate git branches which provides natural process isolation. Deebo…

  1. 1

    Open source, free, local debugger for AI agents

    May 2026

  2. 2

    The MCP that proves your AI's integration fixes work

    14d ago · fetchsandbox.com

  3. 3
    PMB211

    Stop re-explaining your project to AI coding agents

    Jun 2026 · pmbai.dev

  4. 4

    Stack Overflow for AI agents

    Mar 2026

  5. 5

    Keep AI-generated code healthy and maintainable

    Apr 2026

  6. 6

    Your coding agent's missing tool: image generation

    Jun 2026 · agentbrush.dev

  7. 7
    Caplets13

    Give your agent capabilities, not tool walls.

    Jul 2026 · caplets.dev

  8. 8PL
  9. 9

    Your AI agent checks your codebase before it writes

    Jul 2026 · github.com

  10. 10

    Every tool sees errors. Only debugai knows your codebase.

    Jun 2026 · debugai.io

  11. 11

    Connect your coding agent to prod and fix bugs automatically

    May 2026 · multiplayer.app

  12. 12PA

    Hi HN! We’re Theodore and Louis, founders of Armature (YC P26). We reconstruct the entire session behind the MCP tool calls you receive, including what the user asked their agent to do and what the agent thought. You wrap your MCP in 3 lines of code (our SDK is available in Typescript, Python and Go) and start seeing in your dashboard: - All sessions reconstructed: it’s like reading the real conversation the user had inside Claude or ChatGPT! - A ranking of your MCP most popular use cases, built from sessions clustering - The most frequent issues your users’ agents encounter so you can fix…

    Aug 2026 · armature.tech

  13. 13
    PreMan9

    Postman for MCP servers and AI agent tools

    May 2026

  14. 14

    Instant bug reports your AI agent can actually debug

    Jul 2026 · tracebug.dev

  15. 15AM

    I built a browser-only studio for designing and orchestrating MCP agent systems for development and experimental purposes. The whole stack — tool authoring, multi-agent orchestration, RAG, code execution — runs from a single static HTML file via WebAssembly. No backend. The bet: WASM is a hard sandbox for free. When you generate tools with an LLM (or write them by hand), the studio AST-validates the source, registers it lazily, and JIT-compiles into Pyodide on first call. SQL tools run in DuckDB-WASM in a Web Worker. The built-in RAG uses Xenova/all-MiniLM-L6-v2 via Transformers.js for…

    Apr 2026 · agentmcp.studio

  16. 16MM

    Hey HN! I’m Gui from deco (decocms.com). We’ve been using this tool internally as the foundation for a few customer AI platforms, and today we’re open-sourcing it as MCP Mesh. MCP is quickly becoming the standard for agentic systems, but… once you go past a couple servers it turns into the same problems for every team: - M×N config sprawl (every client wired to every server, each with its own JSON + ports + retries) - Token + tool bloat (dumping tool definitions into every prompt doesn’t scale) - Credentials + blast radius (tokens scattered across clients, hard to audit, hard to revoke) - No…

    Dec 2025 · github.com

  17. 17CM

    I built an MCP server that connects coding agents (Claude Code, Cursor, OpenCode, Codex) to a collaborative workspace where your team and other AI models can review what the agent is planning. The problem: When Claude Code creates an implementation plan, it lives in your terminal session. Nobody else sees it until it becomes a PR. If you want GPT to check the architecture or a teammate to flag issues, you're copy-pasting between windows. This MCP server fixes that. When your agent creates a plan, it gets shared as a collaborative thread in CoChat. Engineers comment on it, other AI models…

    Feb 2026 · github.com

  18. 18RM

    I was tired of asking my claude code to reference my codex chats to get references to what decisions it made and why ; so I built Reference MCP It, whenever prompted establishes sessions to get direct access - been using it on my system for a bit and was super helpful so I made a repo :) Would love feedback!

    Jun 2026 · github.com

  19. 19SR

    Hello all, I'm a software developer. Over the last few months more and more of my work has turned into using coding agents instead of typing the whole code myself. Usually a few claude sessions at once, sometimes codex, one per feature or per revealed bug. I ran them in a split terminal for a few weeks, and quickly spotted two main problems. The first is that I couldn't easily tell which agent was stuck waiting on me and which was still working, so I'd cycle through sessions and checking on them. The second one: agents sharing a single branch step on each other. Two of them could be editing…

    Jul 2026 · shikigami.dev

  20. 20CC

    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

  21. 211D

    We just open-sourced the internal system we built at Assembled for running coding agents as a team. Coding agents worked well for individual engineers, but the surrounding workflow was a bit of a mess. We generally found that many engineers had different MCP connections and context for their agents, personal automations running that other people couldn’t access, and very little introspection for what a human’s input into the coding agent looked like. So we built an internal system that converted coding agents into shared team infrastructure. The system runs Codex, Claude Code, OpenCode, and…

    Jun 2026

  22. 22AM

    I built a simple multi user, multi board, Task/Kanban MCP server. I have been looking for something like this to manage development agents, but I wasn't seeing anything that felt like what I wanted. So I set down and decided to vibe code an alternative. While it was an experiment at first I have been using it daily for my personal development projects and I really think there are others who might be looking for exactly this. It's 100% a WIP, but it is also very usable. I have a demo instance running at https://mootasks.dev. If you find this interesting I'd appreciate a star.…

    Apr 2026 · github.com

  23. 23CA

    I built this because I was tired of creating pull requests in 20 repositories just to change a single line of workflow job version. With Infra as AI, just mention the change. Agents work on all repos in parallel, read the docs, make a bunch of PRs and fill in the description. You can see the demo of the actual dashboard in the landing. Let me know your thoughts :) It means a lot to me!

    Sep 2025 · infrastructureas.ai

  24. 24MA

    I’ve been building and using agents heavily lately. The Model Context Protocol ecosystem is growing insanely fast, but discovering and configuring new tools is still highly manual. Every time I needed to connect an agent to a new service, I had to browse registries, figure out the transport type, identify required env vars, and manually update "mcp.json" files. So I built MCPfinder. It aggregates servers from the official MCP registry, Glama, and Smithery (around 25,000 combined entries) into a deduplicated, ranked catalog. But the real twist is the DX: MCPfinder is itself an MCP server :D…

    Apr 2026 · mcpfinder.dev

Ranked by how close each launch is in meaning, then by votes. Refine with a description →