December 19, 2025
Shark Week hits your editor
Show HN: MCPShark Viewer (VS Code/Cursor extension)- view MCP traffic in-editor
Peek inside your AI’s secret chats—devs cheer, skeptics clutch pearls
TLDR: A new VS Code/Cursor add‑on shows AI tool traffic inside your editor, making debugging clearer. Commenters are split between praise for transparency and concerns about privacy, compliance, and whether we’re papering over bad agent design; feature requests for timeline views and redaction are already piling up.
The maker of MCPShark just dropped a VS Code/Cursor add‑on that lets you watch the “conversation” between your AI helper and the tools it uses—right in your editor. MCP stands for Model Context Protocol, basically the way AI agents talk to external tools and share info. Fans are calling it “Wireshark for AI” and racing to install it from the Marketplace and the repo, gushing that they can finally stop guessing what got sent where.
But the comment section quickly turned into a soap opera. Minimalists rolled in with “do we really need another VS Code extension?” while architecture purists insisted this is treating symptoms, not causes: fix flaky agents, not just spy on them. Security folks grabbed the mic to warn that traces can contain prompts, API keys, and user data—demanding redaction, opt‑in logging, and export controls before this sees enterprise daylight. Meanwhile, power users are piling on feature requests: timeline view, session grouping, diff tool args, exporting traces via the issues board.
And yes, the memes flowed: “Baby Shark (do-do-do) for prompts,” shark fins in dark mode, and jokes about “Shark Week in VS Code.” The vibe: half tool‑nerd excitement, half pearl‑clutching paranoia, with a side of fish puns. More details live at mcpshark.sh.
Key Points
- •MCPShark Viewer is a new extension for VS Code and Cursor that displays MCP traffic within the editor.
- •The extension aims to streamline MCP debugging by reducing switching between terminals and logs.
- •Links are provided to the VS Code Marketplace, the GitHub repo (mcp-shark/mcp-shark), the issues tracker, and the project website.
- •The release follows the recent introduction of MCPShark, a traffic inspector for the Model Context Protocol.
- •The author invites feature requests for improvements like timeline view, session grouping, diffing tool args, and exporting traces.