Nicheloom visits: 59,847 all-time · 7,913 in the last 7 days

The opportunity tracker for new startups.

Today: 895 launches · Niche of the day: browser-based video games · See what launched today →

Agent MCP Studio

build multi-agent MCP systems in a browser tab

Get picks like this daily. Today's launch numbers, the top launches, AI and tech news, and a daily opportunity pick, straight to your inbox.

Want to reach these readers? Sponsor an issue.

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 on-device embeddings. Nothing leaves the browser; close the tab and the stack is gone. The WASM boundary is what makes it safe to execute LLM-generated code locally — no Docker, no per-tenant container, no server.Above the tool layer sits an agentic system with 10 orchestration strategies:- Supervisor (router → 1 expert) - Mixture of Experts (parallel + synthesizer) - Sequential Pipeline - Plan & Execute (planner decomposes, workers execute) - Swarm (peer handoffs) - Debate (contestants + judge) - Reflection (actor + critic loop) - Hierarchical (manager delegates via ask_<persona> tools) - Round-Robin (panel + moderator) - Map-Reduce (splitter → parallel → aggregator)You build a team visually: drag tool chips onto persona nodes on a service graph, pick a strategy, and the topology reshapes to match. Each persona auto-registers as an MCP tool (ask_<name>), plus an agent_chat(query, strategy?) meta tool. A bundled Node bridge speaks stdio to Claude Desktop and WebSocket to your tab — your browser becomes an MCP server.When you're done, Export gives you a real Python MCP server: server.py, agentic.py, tools/*.py, Dockerfile, requirements.txt, .env.example. The exported agentic.py is a faithful Python port of the same orchestration logic running in the browser, so the deployable artifact behaves identically to the prototype.Also shipped: Project Packs. Export the whole project as a single .agentpack.json. Auto-detects required external services (OpenAI, GitHub, Stripe, Anthropic, Slack, Notion, Linear, etc.) by scanning tool source for os.environ.get(...) and cross-referencing against the network allowlist. Recipients get an import wizard that prompts for credentials. Manifests are reviewable, sharable, and never carry secrets.Some things I'm honestly uncertain about:- 10 strategies might be too many. My guess is most users only need Supervisor, Mixture of Experts, and Debate. Open to data on which ones actually pull weight. - Browser cold-starts (Pyodide warm-up on first load) are a real UX hit despite aggressive caching. - bridge.js is the only non-browser piece. A hosted variant is the obvious next step.Built with Pyodide, DuckDB-WASM, Transformers.js, OpenAI Chat Completions (or a local Qwen 1.5 0.5B running in-browser via Transformers for fully offline mode). ~5K lines of HTML/CSS/JS in one file.https://www.agentmcp.studioGenuinely curious whether running this much LLM-generated code in a browser tab feels reasonable to you, or quietly terrifying.

HN · launched Apr 25, 2026 · 11 upvotes (top 38%) · 0 views

Niche: mcp server developer tools · 110 launches, 14 in the last 7 days ▲ +75% · Explore this niche →

Category and tags

  • Horizontal
  • Dev tools
  • Developer
  • AI-native
  • Commercial product

Visit website ↗ Source listing ↗

Could you build this?

Partial The UI and orchestration can be vibe-coded, but running full Python MCP tools and SQL processing client-side in a single static file relies on complex WebAssembly integration with Pyodide and DuckDB-WASM.

What it would actually take: The architecture requires bundling Pyodide and DuckDB-WASM inside web workers, handling virtual filesystem synchronization (Emscripten FS) in browser storage, and establishing a client-side JSON-RPC/MCP transport bridge. The difficult part is debugging Pyodide package dependencies, browser sandbox constraints, and cross-thread memory management without any server-side fallback.

Discussion

6 comments analyzed.

Concerns raised: Export to Python feature may have unhandled edge cases, Bug with MCP tool code visibility in editor

Feature requests: Explicit agent topology serialization for version control and diffing, Support testing workflows against multiple models, Rollback capability for production changes

Competitors

Other products that read as similar to this one : 853 launches clear the similarity bar, closest 8 shown.

Attention rank: #389 of 854 (itself plus its competitors, highest first, normalized so YC and Product Hunt are compared fairly).

Launched 172 days after the earliest competitor.

The niche, labels, vibe code rating and competitor comparison on this page are analysis by Nicheloom. If you use them, please credit nicheloom.com. How you may use our data.